Idea for a new part in headers of .rc files

[David Hinz]

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

[Nathan Woods]

Is there a way in SVN to query which revision any given file was last 
modified?  If so, I could throw together a perl script that looked for 
xx.rc files that are in the same directory as en.rc files that were more 
recently modified.

[Mark de Wit]

Instead of making up another number, why not just reference the svn version 
the translation is based on?

Mark
----- Original Message ----- 
From: "David Hinz" [e-mail]
To: "ReactOS Development List" [e-mail]; "ReactOS Translate 
List" [e-mail]
Sent: Tuesday, October 11, 2005 10:16 PM
Subject: [ros-dev] Idea for a new part in headers of .rc files
> 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
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[David Hinz]

Mark de Wit schrieb:
> Instead of making up another number, why not just reference the svn 
> version the translation is based on?
>
> Mark
> ----- Original Message ----- From: "David Hinz" [e-mail]
> To: "ReactOS Development List" [e-mail]; "ReactOS 
> Translate List" [e-mail]
> Sent: Tuesday, October 11, 2005 10:16 PM
> Subject: [ros-dev] Idea for a new part in headers of .rc files
> > 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
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

The svn version changes, even if just a little spelling mistake was 
corrceted.

But if all the things I want to do are possible with svn please excuse 
me, I'm new to svn.