entries in configuration files should not be i18n'ed

[GoogleCodeExporter]

entries in configuration files should not be i18n'ed

[GoogleCodeExporter]

Original comment by [email protected] on 4 Nov 2006 at 4:49

• Changed title: entries in configuration files should not be i18n'ed

[GoogleCodeExporter]

it seems to be fixed now in *.pro files by some previous revisions.

Original comment by [email protected] on 14 Nov 2006 at 9:20

[GoogleCodeExporter]

so it is safe to close this report...?

Original comment by [email protected] on 18 Nov 2006 at 11:08

[GoogleCodeExporter]

well... for my part of i18N it works nice for a some number of weeks =). I 
think you 
(project developers) should make some rules about translations: what should and 
what 
should be not, bcs new visual features containing text are coming in and such 
issues 
may take place every time. Have a ruleset -> no troubles, and as I see you are 
already making such ruleset for src comments.

Original comment by [email protected] on 14 Dec 2006 at 9:48

[GoogleCodeExporter]

closing as the reporter claims "it's fixed for several weeks" a few months ago.

Original comment by [email protected] on 20 Jul 2007 at 10:24

• Changed state: Fixed