application

Hi!

I have else one idea :)
what I carry several time :)

but begin from afar.


[afar]

What is Wyona and other CMS? - programs.
What they solve? - CMS.

but CMS - is so big field, and must be fulcrum for application.
One of them - News, Magazine, Periodical, Journal...

This fulcrums - is user's tasks.
And that more fulcrums have program - that more program distribution.
This user's tasks - applications of program.
(And, usually, list of applications enumerate on first-page-site, so user
can see his task and go to next.)

For ordinary user - not interesting what program's application is
XML/XSLT, but if he see "News, Magazine ... CMS application" (him
tasks) - he interesting, and download. (although this is XML/XSLT but
in fine cover).

Important - sequence:
1. user _interesting_ by program that solving him tasks.
2. user _study_ required technologies for solving him task by this
   progam.


[application]

Idea - have application for translation.
Yes, simple translation of text.
But I think that there is many users that try to solve this task.
(at least one-user for each country)

And I dont know program that solve this task by full.
(more often there is one MS Word's file which are sequentially
editing by some translator...)

Task in reality is not simple.

But now's Wyona - _can_ solve this task.
This can be solved by technologies using in Wyona.

Requirements needed by translations-application:
- multy language (unicode)
- multi-user access, roles, there is
   * translator-master role (only correct translated texts)
   * translator-slave role (make first version on text)
   * ...
- client/server architecture (all stored on one place)
- Version controller
- Flow-manager
- content-flexible (XML/XSLT)
- publishing-house needes - xml-FO -> pdf ...

example work-sequence:
1. there is foreign-text,
2. convert to XML-like format (DocBook),
3. mark-up on translate-part (paragraph or statement),
4. each "translate-part" can translate one translator, i.e. possible
   working with document by many translator.
5. (correcting by main-translator, corrector)
6. publish

And for this application task "web-publish for internet" - not main
task, it is optional.

Main task - to give possibility to work many people on one document
(work with result of each-other's work), and have translated document
(qualitative) and have flexible output.

This may be for -
1. inter-net-server - which offer public translation service
2. intra-net-server - solve task for inner document-translation
   (there is firms with hired-translators in staff, or certainly
   publishing-house).


[ps]
repeat.
in program-industry there is balancing between
  1. universality (user may all customize by self) /open sources, free/
  2. black-box (which maded for narrow user's task, and user dont-know what
     is inside, and cant nothing change) /binary, cost/

1 - big scope, but needed skilled-user.
2 - easy for user - user "install and play".
    but there is many "user's specific task" and impossile to create
    so many programs, that covering all them. And solution - find points
    that have big demand.

Translation-task - is specific task of CMS.
And to try to make application like "black-box" for this demand.
But which can be "universality" on request.

And finally, building this application by Wyona - is excellent tutorial
illustrating all Wyona's features.


Ilya