[TC 10.51 and later] Illegal dot in string 2107 in wcmd_ita.lng

[Hurdet]

I continuously receive warning box in TC 11.02:

Note to plugin translator of plugin tc.wdx
Invalid character . in Plugin field "IN. traccia"
Please change!

How to stop it?

[petermad]

2Hurdet

How to stop it?

Open your wcmd_ita.lng file in a text editor, go to string number 2107 and remove the dot after N

Before TC 10.50 the translation was "Numero traccia", but for some reson the translater changed that to "N. traccia" in TC 10.51 - peculiar, that the translator hasn't noticed the error message.

[white]

Confirmed.

Moderator message from: white » 2023-11-10, 19:59 UTC

Moved to Bugs forum.

[petermad]

There is an illegal dot in string 2107 in wcmd_ita.lng:

Code: Select all

2107="Etichetta presente|Titolo|Artista|Album|Anno di uscita|Descrizione|N. traccia|Genere|"

It causes this error message when starting TC:

---------------------------
tc.wdx
---------------------------
Note to plugin translator of plugin tc.wdx

Invalid character "." in Plugin field "!N. traccia"

Please change!
---------------------------
OK
---------------------------

See also: https://ghisler.ch/board/viewtopic.php?p=444813#p444813

[white]

Moderator message from: white » 2023-11-10, 20:04 UTC

There is an illegal dot in string 2107 in wcmd_ita.lng:

Topic merged with existing topic

[petermad]

Moderator message from: petermad » 2023-11-11, 03:32 UTC

Changed the topic title to something more meaningful for a bug report

[white]

Moderator message from: white » 2023-11-11, 09:57 UTC

Fixed the TC version number (11.51) in the topic title to something more meaningful (10.51)

[white]

Before TC 10.50 the translation was "Numero traccia", but for some reson the translater changed that to "N. traccia" in TC 10.51 - peculiar, that the translator hasn't noticed the error message.

Mr. Ghisler changed it in TC 10.50rc2:

Thanks, it's a problem with the included Italian translation. I will change it to "Numero traccia". You can do that yourself in wcmd_ita.lng string 2107 to get rid of the error.

Spanish, French, Norwegian and Slovenian have the same problem.

Then it was changed back again to the faulty value in TC 10.51rc1.
It seems the Norwegian file is still wrong:

2107="Gjeldende merking|Tittel|Artist|Album|Utgitt år|Beskrivelse|Spornr.|Sjanger|"

[ghisler(Author)]

Unfortunately I didn't detect that the Italian translator added the new strings to an uncorrected version of WCM_ITA.LNG, so the bug returned. It's also my fault because I didn't update difres.exe to check also strings 1732,1742,2061,2101,2107 in addition to 1579 and 1580 for errors (they are all used for translating the internal content plugin).

Here is an updated version of the tool (there were no new strings in 11.02):
https://www.ghisler.com/b/difres1101.zip

[white]

Here is an updated version of the tool (there were no new strings in 11.02):
https://www.ghisler.com/b/difres1101.zip

Can you update it a bit more so that it doesn't try to write an ini file into the Windows folder (which puts the ini file into the VirtualStore folder)?

[petermad]

It's also my fault because I didn't update difres.exe

Not entirely your fault - just testing the languages in question by restarting TC should have made the translator react.

[petermad]

Can you update it a bit more so that it doesn't try to write an ini file into the Windows folder

It would be better if the difres.ini file was first tried to be written in the same dir as Difres.exe.

Also - why can't those string numbers: 1579,1580,1732,1742,2061,2101,2107 not be placed in a special section of Dglrange.txt instead of being hardcoded into Difres.exe?

[ghisler(Author)]

Also - why can't those string numbers: 1579,1580,1732,1742,2061,2101,2107 not be placed in a special section of Dglrange.txt instead of being hardcoded into Difres.exe?

It would make dlgrange.txt incompatible with older versions of difres.exe. Some people (for example you!) have distributed updated dlgrange.txt files which would break older versions of difres.exe when users download them.

Can you update it a bit more so that it doesn't try to write an ini file into the Windows folder (which puts the ini file into the VirtualStore folder)?

Who cares as long as the data can be written?

[petermad]

2ghisler(Author)

Who cares as long as the data can be written?

Well, I have a difres.exe both in my language folder for 64bit TC and 32bit TC, but currently it is always the last used file in either of the two directories that is preloaded, so I have to change the "Foreign language resource" file name before running the tool in the other language folder. If Difres.exe first looked for it's ini file in the local directory, I would not have to do that.

[white]

Can you update it a bit more so that it doesn't try to write an ini file into the Windows folder (which puts the ini file into the VirtualStore folder)?

Who cares as long as the data can be written?

The VirtualStore solution by Microsoft was introduced to address compatibility issues with programs that still write files into system directories. However, it has become a best practice to avoid using the Windows directory for storing ini files for quite some time now. I think the reasons for that are quite obvious and well known by you: ensure better compatibility, minimize potential conflicts, and provide a clearer understanding to users about where their settings are stored.