Hi
It is still under devloping and havy it will problare be ready next year,
it is very complex system, we do not want anything goes wrong.
it will not letting translator tuch the rc syntax, and best of part
it allown any dev only change the english rc file and thuse change
will automatic merges to other langues as well,
----- Original Message -----
From: Colin Finck
To: 'ReactOS Development List'
Sent: Monday, November 05, 2007 3:43 PM
Subject: Re: [ros-dev] Ros-dev Digest, Vol 39, Issue 1
The open question would be: What happens with the already planned/prepared online
translation service?
It also had a plan to improve the whole translation process, but as far as I know it
differs much from your solution.
Klemens, Magnus, any comments on this?
Regards,
Colin
----------------------------------------------------------------------------
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of
Marc Piulachs
Sent: Monday, November 05, 2007 2:26 PM
To: 'ReactOS Development List'
Subject: Re: [ros-dev] Ros-dev Digest, Vol 39, Issue 1
Hi Olaf,
You understood it correctly; the idea is graphically show an up-to-date localization
status report. Not only which modules are translated to each language, but also if any of
the localizations is "dirty" (meaning that exists but contains new unlocalized
strings). It will make the task of maintaining updated translations easier.
/marc
----------------------------------------------------------------------------
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of
Olaf Siejka
Sent: Sunday, November 04, 2007 11:11 PM
To: ros-dev(a)reactos.org
Subject: Re: [ros-dev] Ros-dev Digest, Vol 39, Issue 1
- Declarative module localizations : Now module localizations are created in
a declarative way which makes trivial tasks like listing non existent or
outdated language localizations in real time for example :
http://www.codexchange.net/rosdoc/localizations.htm
Let me know your opinions and suggestions as I would like to start finishing
some of this features and merge all/part of my changes back to trunk
I find this part extremely important. It would allow real-time tracking of translation
progress/status (if i understood it correctly) which would greatly help maintain all the
growing ROS localizations and help all ROS translating teams. Such webpage, as you
presented here, should be created on ROS website as soon as it would be possible.
------------------------------------------------------------------------------
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev