Resource headers

[Murphy, Ged (Bolton)]

Daniel Reimer wrote:

>   I did not want to cause problems with that... 
I know, which is why I didn't want to drag this through the mud.

Anyway, now as we're on the topic, we might as well try and resolve it.

So, should we be adding headers to resource file?
If yes, what info should be in there. It's clear that the translator and
programmer should be separate headings.

My personal view is that we should leave headers out of resource files.
If translators wanted to add their mark, then a line should be added at the
top of the file saying /* translated by FOO */

Ged.

[Brandon Turner]

Murphy, Ged (Bolton) wrote:

>  Daniel Reimer wrote:
>
>   
>
> >  I did not want to cause problems with that...
> >     
> >  
> I know, which is why I didn't want to drag this through the mud.
>
> Anyway, now as we're on the topic, we might as well try and resolve it.
>
> So, should we be adding headers to resource file?
> If yes, what info should be in there. It's clear that the translator and
> programmer should be separate headings.
>
> My personal view is that we should leave headers out of resource files.
> If translators wanted to add their mark, then a line should be added at the
> top of the file saying /* translated by FOO */
>
> Ged.
>
>
>
>
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
>   
>  
+1 one to that. 

Perhaps if the original coder didn't have a rc file and hardcoded 
everything to english and the translator fixed that then they could 
claim copyright over it.  But not if they just translate what someone 
else did in another language already.

Brandon