RE: Ros-dev Digest, Vol 14, Issue 25

[Lucio Diaz]

David Hinz wrote:

Hey guys,
when I just translated format, I stunbled over one
thing:
What if somebody changed the content of a string after
I translated it?
After some minutes, I had a easy solution for that
problem:
The En.rc gets a little line in it's head-comment with
a revision
number. Each time somebody changes or adds a string in
the En.rc, he
sets the revision number +1 and so all translators
have an easy to
control indicator, if they need to translate something
or not.
But I think one thing should be clear, if there just
has been corrected
a spelling mistake and not something important, the
revision number
won't be touched.
Now some example headers:
in the EN.rc:
/*
  * Moved all hardcoded strings to En.rc.
  * By Magnus Olsen  2005
  *
  * Revision: 1
  */
in my De.rc:
/*
  * Moved all hardcoded strings to En.rc.
  * By Magnus Olsen  2005
  * First German Translation by David Hinz 20051010
  *
  * Translated Revision 1 of En.rc
  */
This is just an idea, but I think this could save a
lot of work on
bigger applications than format...
Greets,
David Hinz

---------------------------------------

I agree, in fact i am working in a program to manage
translation in reactos, i am using Delphi 2.0 but as i
am not much skilled (long time since i used pascal)
and my time is on the limit it is going slowly but it
should work as follow:

Part 1:
- You select your language
- You select the working directory of reactos source.
- The program scans all files for en.rc files and list
their directories (as their names are all the same).
- With each file the program check a text file with a
list of en.rc files, and if it is not there it adds
it, and it is shown in the GUI as highlighted (pending
translation).
- If the file is found in the list, it check if
translating language file is current--> if it is not
current then the file is highlighted (pending
translation).
- If the file is found in the list, and found a
translation file current--> the file is listed but not
highlighted.
- It does with all rc files till no more rc files in
the directory.

Part 2:

- On clicking in a file in the listbox (highlighted or
not) it will be shown in an Richtext edit panel and
besides another panel with the material already
translated (if there is any language related file
already done), if not, the english text will be shown
with the "probable translatable" areas highligthed
(those between "").
-A save button, that will save the changes in the
second panel automatically into the right directory in
a language working copy.

What do you think?


		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es

[Thomas Weidenmueller]

Lucio Diaz wrote:
>   David Hinz wrote:
>  
>  Hey guys,
>  when I just translated format, I stunbled over one
>  thing:
>  What if somebody changed the content of a string after
>  I translated it?
>  After some minutes, I had a easy solution for that
>  problem:
>  The En.rc gets a little line in it's head-comment with
>  a revision
>  number. Each time somebody changes or adds a string in
>  the En.rc, he
>  sets the revision number +1 and so all translators
>  have an easy to
>  control indicator, if they need to translate something
>  or not.
>  But I think one thing should be clear, if there just
>  has been corrected
>  a spelling mistake and not something important, the
>  revision number
>  won't be touched.
>  Now some example headers:
>  in the EN.rc:
>  /*
>    * Moved all hardcoded strings to En.rc.
>    * By Magnus Olsen  2005
>    *
>    * Revision: 1
>    */
>  in my De.rc:
>  /*
>    * Moved all hardcoded strings to En.rc.
>    * By Magnus Olsen  2005
>    * First German Translation by David Hinz 20051010
>    *
>    * Translated Revision 1 of En.rc
>    */
>  This is just an idea, but I think this could save a
>  lot of work on
>  bigger applications than format... 
Uhm...why not simply watch SVN or take a look at the svn logs?

- Thomas

[Royce Mitchell III]

David Hinz wrote:

>   Thomas Weidenmueller schrieb:
>
> >  Lucio Diaz wrote:
> >   
> >
> > >  David Hinz wrote:
> > >
> > > Hey guys,
> > > when I just translated format, I stunbled over one
> > > thing:
> > > What if somebody changed the content of a string after
> > > I translated it?
> > > After some minutes, I had a easy solution for that
> > > problem:
> > > The En.rc gets a little line in it's head-comment with
> > > a revision
> > > number. Each time somebody changes or adds a string in
> > > the En.rc, he
> > > sets the revision number +1 and so all translators
> > > have an easy to
> > > control indicator, if they need to translate something
> > > or not.
> > > But I think one thing should be clear, if there just
> > > has been corrected
> > > a spelling mistake and not something important, the
> > > revision number
> > > won't be touched.
> > > Now some example headers:
> > > in the EN.rc:
> > > /*
> > >   * Moved all hardcoded strings to En.rc.
> > >   * By Magnus Olsen  2005
> > >   *
> > >   * Revision: 1
> > >   */
> > > in my De.rc:
> > > /*
> > >   * Moved all hardcoded strings to En.rc.
> > >   * By Magnus Olsen  2005
> > >   * First German Translation by David Hinz 20051010
> > >   *
> > >   * Translated Revision 1 of En.rc
> > >   */
> > > This is just an idea, but I think this could save a
> > > lot of work on
> > > bigger applications than format...
> > >     
> > >  
> > Uhm...why not simply watch SVN or take a look at the svn logs?
> >
> > - Thomas
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >   
> >  
>  The thing is, I want to see, if somebody changed the conteent of a 
>  string, so that a retranslation is necessary.
>  Maybe a changelog for the .rc-files would be a good idea.
>  But that tool sounds good, maybe we should create a translation tool 
>  for all the translators, with a database on the reactos.org server, 
>  where we can save all strings and mark them as "needs to be 
>  retranslated". Just an idea... 
The best way to accomplish this, IMHO, is to feed the results of "svn 
blame" into a utility that can do those comparisons for you, and give 
you a list of what non-english strings are missing or older than the 
english strings.

[Maarten Bosma]

>  
>
> If someone would want to create a script that checks the last-changed svn
> revision of .rc files against the corresponding English resource file, I
> could put that on reactos.org and have it run once or twice a day and put
> the results on the website.
>  
If no one else wants to I would do it, when I have a bit more time.

Royce Mitchell III schrieb:

>   The best way to accomplish this, IMHO, is to feed the
> results of "svn 
>  blame" into a utility that can do those comparisons for you, and give 
>  you a list of what non-english strings are missing or older than the 
>  english strings.
>  
Don't see how svn blame could be usefull here. You just need a paser 
that generates mysql database entries from rc files and run him 
everytime one of the files changes.


Maarten Bosma

[David Hinz]

Maarten Bosma schrieb:

> >  
> >
> >  If someone would want to create a script that checks the last-changed 
> >  svn
> >  revision of .rc files against the corresponding English resource file, I
> >  could put that on reactos.org and have it run once or twice a day and 
> >  put
> >  the results on the website.
> >  
>  If no one else wants to I would do it, when I have a bit more time.
>
>  Royce Mitchell III schrieb:
>
> >   The best way to accomplish this, IMHO, is to feed
> > the results of "svn 
> >  blame" into a utility that can do those comparisons for you, and give 
> >  you a list of what non-english strings are missing or older than the 
> >  english strings.
> >  
>  Don't see how svn blame could be usefull here. You just need a paser 
>  that generates mysql database entries from rc files and run him 
>  everytime one of the files changes.
>
>
>  Maarten Bosma
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  
Well, my idea with the database would also allow us to share strings 
between different applications.
We _could_ create a MySQL database on the reactos.org server and update 
our local database from it, just like svn.
The .rc files don't contain the full strings any more, the just tell a 
little application which strings it has to load from the db and put them 
into the .rc file.
This would allow easier translation, because a string only needs to be 
translated one time and not in every single application. And I think 
there are a lot of strings that can be used in more than one application.

This is of course just an idea, but there are a lot of applications we 
will create, and they all need to be translated in let's say 50 
different languages.
I think, we can save a lot of work here.
Just think about it.

Greets,

David Hinz

[Royce Mitchell III]

Maarten Bosma wrote:

>   Don't see how svn blame could be usefull here. You
> just need a paser 
>  that generates mysql database entries from rc files and run him 
>  everytime one of the files changes.
>
>
>  Maarten Bosma 
Allow me to illustrate...

Here is a line from the svn blame from 
reactos/subsys/system/explorer/explorer-en.rc:

   328  18263           10/4/2005 8:47:22 AM 
mf                                 IDS_TITLE               "Reactos 
Explorer"

Notice that for the string IDS_TITLE, I know that it was last edited at 
revision 18263.

Now here's the svn blame for the same resource from 
reactos/subsys/system/explorer/explorer-es.rc:

   313  18263           10/4/2005 8:47:22 AM 
mf                                 IDS_TITLE               "ReactOS 
Explorer"

I can see that IDS_TITLE for the spanish resource was edited at the same 
revision, so it is up to date. These are comparisons that can be automated.

You can also check and see if the string is missing or identical to 
English ( i.e. still needing to be edited ).

[Brandon Turner]

Yeah, in general if i change anything in the .rc file i make it known 
pretty clearly in my svn log.

Brandon

Thomas Weidenmueller wrote:

>  Lucio Diaz wrote:
>   
>
> >  David Hinz wrote:
> >
> > Hey guys,
> > when I just translated format, I stunbled over one
> > thing:
> > What if somebody changed the content of a string after
> > I translated it?
> > After some minutes, I had a easy solution for that
> > problem:
> > The En.rc gets a little line in it's head-comment with
> > a revision
> > number. Each time somebody changes or adds a string in
> > the En.rc, he
> > sets the revision number +1 and so all translators
> > have an easy to
> > control indicator, if they need to translate something
> > or not.
> > But I think one thing should be clear, if there just
> > has been corrected
> > a spelling mistake and not something important, the
> > revision number
> > won't be touched.
> > Now some example headers:
> > in the EN.rc:
> > /*
> >   * Moved all hardcoded strings to En.rc.
> >   * By Magnus Olsen  2005
> >   *
> >   * Revision: 1
> >   */
> > in my De.rc:
> > /*
> >   * Moved all hardcoded strings to En.rc.
> >   * By Magnus Olsen  2005
> >   * First German Translation by David Hinz 20051010
> >   *
> >   * Translated Revision 1 of En.rc
> >   */
> > This is just an idea, but I think this could save a
> > lot of work on
> > bigger applications than format...
> >     
> >  
> Uhm...why not simply watch SVN or take a look at the svn logs?
>
> - Thomas
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>   
>

[David Hinz]

Brandon Turner schrieb:

>   Yeah, in general if i change anything in the .rc file
> i make it known 
>  pretty clearly in my svn log.
>
>  Brandon
>
>  Thomas Weidenmueller wrote:
>
> >   Lucio Diaz wrote:
> >   
> >
> > >   David Hinz wrote:
> > >
> > >  Hey guys,
> > >  when I just translated format, I stunbled over one
> > >  thing:
> > >  What if somebody changed the content of a string after
> > >  I translated it?
> > >  After some minutes, I had a easy solution for that
> > >  problem:
> > >  The En.rc gets a little line in it's head-comment with
> > >  a revision
> > >  number. Each time somebody changes or adds a string in
> > >  the En.rc, he
> > >  sets the revision number +1 and so all translators
> > >  have an easy to
> > >  control indicator, if they need to translate something
> > >  or not.
> > >  But I think one thing should be clear, if there just
> > >  has been corrected
> > >  a spelling mistake and not something important, the
> > >  revision number
> > >  won't be touched.
> > >  Now some example headers:
> > >  in the EN.rc:
> > >  /*
> > >   * Moved all hardcoded strings to En.rc.
> > >   * By Magnus Olsen  2005
> > >   *
> > >   * Revision: 1
> > >   */
> > >  in my De.rc:
> > >  /*
> > >   * Moved all hardcoded strings to En.rc.
> > >   * By Magnus Olsen  2005
> > >   * First German Translation by David Hinz 20051010
> > >   *
> > >   * Translated Revision 1 of En.rc
> > >   */
> > >  This is just an idea, but I think this could save a
> > >  lot of work on
> > >  bigger applications than format...
> > >     
> >
> >  Uhm...why not simply watch SVN or take a look at the svn logs?
> >
> >  - Thomas
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >   
> >  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  
Well, the thing is I wanted to have something that makes it very easy to 
see, if something has changed since the last time I translated that file.
Watching the svn all the time is not that easy than just looking at a 
number.
There could also be a little helper app that scans all .rc files in my 
language and all en.rcs for revision differences and shows me, where I 
have to translate something.
Then I can look in the svn what actually has been changed.
It just makes things easier for translators.

Greets,

David Hinz

[Ge van Geldorp]

>   Well, the thing is I wanted to have something that
> makes it 
>  very easy to see, if something has changed since the last 
>  time I translated that file.
>  Watching the svn all the time is not that easy than just 
>  looking at a number.
>  There could also be a little helper app that scans all .rc 
>  files in my language and all en.rcs for revision differences 
>  and shows me, where I have to translate something.
>  Then I can look in the svn what actually has been changed.
>  It just makes things easier for translators. 
If someone would want to create a script that checks the last-changed svn
revision of .rc files against the corresponding English resource file, I
could put that on reactos.org and have it run once or twice a day and put
the results on the website.

Gé van Geldorp.

[Magnus Olsen]

Hi
GvG that is good idea I know harteex and other translator should love it.
They want more easy way to keep track on the en.rc

----- Original Message ----- 
From: "Ge van Geldorp" <gvg(a)reactos.org>
To: "'ReactOS Development List'" <ros-dev(a)reactos.org>
Sent: den 12 October 2005 14:31
Subject: [ros-dev] Resource updates


>   Well, the thing is I wanted to have something that
> makes it
>  very easy to see, if something has changed since the last
>  time I translated that file.
>  Watching the svn all the time is not that easy than just
>  looking at a number.
>  There could also be a little helper app that scans all .rc
>  files in my language and all en.rcs for revision differences
>  and shows me, where I have to translate something.
>  Then I can look in the svn what actually has been changed.
>  It just makes things easier for translators. 
If someone would want to create a script that checks the last-changed svn
revision of .rc files against the corresponding English resource file, I
could put that on reactos.org and have it run once or twice a day and put
the results on the website.

Gé van Geldorp.


_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.14/129 - Release Date: 2005-10-11

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.org [mailto:[e-mail]] On Behalf Of Ge
> van Geldorp
>  Sent: 12. oktober 2005 14:31
>  To: 'ReactOS Development List'
>  Subject: [ros-dev] Resource updates
>  
> >   Well, the thing is I wanted to have something
> > that makes it
> >  very easy to see, if something has changed since the last
> >  time I translated that file.
> >  Watching the svn all the time is not that easy than just
> >  looking at a number.
> >  There could also be a little helper app that scans all .rc
> >  files in my language and all en.rcs for revision differences
> >  and shows me, where I have to translate something.
> >  Then I can look in the svn what actually has been changed.
> >  It just makes things easier for translators. 
>  
>  If someone would want to create a script that checks the last-changed svn
>  revision of .rc files against the corresponding English resource file, I
>  could put that on reactos.org and have it run once or twice a day and put
>  the results on the website.
>  
>  Gé van Geldorp. 
You could track it using properties on the translated resource files.
Tracking it using revision numbers can give false positives (e.g. if
you commit a change to the translated resource file that doesn't actually
sync it to the latest English resource file). This will also work well
with branches (giving merge conflicts in case of conflicting changes).
Example:

# svn ci -m "Some change" en.rc
Committed revision 123.

(translate r123)
# svn propset ros:translate "123" da.rc
# svn ci -m "Sync to r123" da.rc
Committed revision 124.

Casper

[Ge van Geldorp]

>   From: Ge van Geldorp
>  
>  If someone would want to create a script that checks the 
>  last-changed svn revision of .rc files against the 
>  corresponding English resource file, I could put that on 
>  reactos.org and have it run once or twice a day and put the 
>  results on the website. 
Nathan Woods created such a script, I've set it up to run daily. You can
find the output in http://www.reactos.org/generated/transstatus.html (or in
the Developer menu choose "Translation status").
The script is available in svn at svn://svn.reactos.org/trunk/web/scripts,
feel free to improve if needed. Just drop me a note when you change
something, I need to check-out the script manually.

Gé van Geldorp.

[Bernd Blaauw]

Ge van Geldorp schreef:
>   Nathan Woods created such a script, I've set it up
> to run daily. You can
>  find the output in http://www.reactos.org/generated/transstatus.html (or in
>  the Developer menu choose "Translation status").
>     
Not that I can code even "Hello World", but:
The webpage shows for which programs/modules at least 1 translation exists.
English files themselves are missing, as an example based on which to 
translate

This would also show additional programs for which only English exists 
as current translation.
Otherwise people would think only Regedit and Notepad can be translated.
(as no translations exist for other programs currently)

I sometimes translate (into Dutch) small items when I'm bored, but never 
using any revision control system, just using NOTEPAD/EDIT

Bernd

[Magnus Olsen]

GvG great
Can it be include all En.rc vs all langues.rc ?
if u do alot of translator will love that url more


----- Original Message ----- 
From: "Ge van Geldorp" <gvg(a)reactos.org>
To: "'ReactOS Development List'" <ros-dev(a)reactos.org>
Sent: den 13 October 2005 17:51
Subject: RE: [ros-dev] Resource updates


>   From: Ge van Geldorp
>
>  If someone would want to create a script that checks the
>  last-changed svn revision of .rc files against the
>  corresponding English resource file, I could put that on
>  reactos.org and have it run once or twice a day and put the
>  results on the website. 
Nathan Woods created such a script, I've set it up to run daily. You can
find the output in http://www.reactos.org/generated/transstatus.html (or in
the Developer menu choose "Translation status").
The script is available in svn at svn://svn.reactos.org/trunk/web/scripts,
feel free to improve if needed. Just drop me a note when you change
something, I need to check-out the script manually.

Gé van Geldorp.


_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.14/131 - Release Date: 2005-10-12

[Ge van Geldorp]

>   From: Magnus Olsen
>  
>  GvG great
>  Can it be include all En.rc vs all langues.rc ?
>  if u do alot of translator will love that url more 
Like I said, the code is in svn. Please feel free to improve.

Gé van Geldorp.

[Sylvain Petreolle]

--- Ge van Geldorp <gvg(a)reactos.org> a écrit :
>   Nathan Woods created such a script, I've set it up
> to run daily. You can
>  find the output in http://www.reactos.org/generated/transstatus.html (or in
>  the Developer menu choose "Translation status").
>  The script is available in svn at svn://svn.reactos.org/trunk/web/scripts,
>  feel free to improve if needed. Just drop me a note when you change
>  something, I need to check-out the script manually.
>  
>  Gé van Geldorp. 
Hi Gé,
The script works as expected,
but the url  pointing to the files on ViewVC still link to the old svn.reactos.org
repository.

The following line should read :
my $url = "http://svn.reactos.org/viewcvs/trunk/reactos/$path";
as
my $url = "http://svn.reactos.ru/svn/reactos/trunk/reactos/$path";


Kind regards,
Sylvain Petreolle (aka Usurp)
--- --- --- --- --- --- --- --- --- --- --- --- ---
Listen to free Music: http://www.jamendo.com
Windows is proprietary, use free ReactOS instead : http://www.reactos.org

[Ge van Geldorp]

>   From: Sylvain Petreolle
>
>  The script works as expected,
>  but the url  pointing to the files on ViewVC still link to 
>  the old svn.reactos.org repository.
>  
>  The following line should read :
>  my $url = "http://svn.reactos.org/viewcvs/trunk/reactos/$path";
>  as
>  my $url = "http://svn.reactos.ru/svn/reactos/trunk/reactos/$path"; 
Thanks, fixed in r21762. I used svn.reactos.org since I think that's still
the preferred hostname (svn.reactos.ru and svn.reactos.org point to the same
host).

GvG

[Sylvain Petreolle]

Hi,
--- Ge van Geldorp <gvg(a)reactos.org> a écrit :
>   
>  Thanks, fixed in r21762. I used svn.reactos.org since I think that's still
>  the preferred hostname (svn.reactos.ru and svn.reactos.org point to the same
>  host).
>  
>  GvG
>   
The script is case-sensitive, isnt it ?
It doesnt display latest changes done to ncpa.

base/shell/explorer/explorer-en.rc cant be detected like this,
we could add it as a special case.

Here are other apps that could appear after adding lowercase en.rc :

base/applications/reporterror/en.rc
base/applications/winefile/en.rc
dll/cpl/sysdm/en.rc
dll/cpl/ncpa/en.rc
dll/cpl/desk/en.rc
dll/cpl/intl/en.rc
modules/rosapps/packmgr/gui/en.rc
modules/rosapps/packmgr/lib/en.rc


Kind regards,
Sylvain Petreolle (aka Usurp)
--- --- --- --- --- --- --- --- --- --- --- --- ---
Listen to free Music: http://www.jamendo.com
Windows is proprietary, use free ReactOS instead : http://www.reactos.org