entries in configuration files should not be i18n'ed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Adding some qt module support into project (Project properties|
Advanced), for example "network" 

What is the expected output? What do you see instead?

expect "QT += network" in *.pro
have   "QT += <translation of word 'network'>"

then, build process is broken.

What version of the product are you using? On what operating system?

svn checkout 3.11.2006 (OS = FreeBSD Current, MS Windows XP sp2)

Please provide any additional information below.

Total I18N: 
1.IMHO, I18N should not touch some keywords =), build/src/lib/bin folder's 
names, class names and so on
2. it can touch GUI view features, but not matter of these features
3. sorry for my english

Original issue reported on code.google.com by har...@yandex.ru on 4 Nov 2006 at 1:03

[GoogleCodeExporter]

Original comment by cucoma...@gmail.com 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 har...@yandex.ru on 14 Nov 2006 at 9:20

[GoogleCodeExporter]

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

Original comment by cucoma...@gmail.com 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 har...@yandex.ru 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 cucoma...@gmail.com on 20 Jul 2007 at 10:24

• Changed state: Fixed