[BUG/REQ] Content plugin translation only works when...

[Lefteous]

2Sheepdog

What for?

You have two choices:
1) Use your current auto hotkey script to change the menu. Then rename the matching section in all your content language files (however you are going to do this).
2) Expand your auto hotkey script a bit...

It's your choice.

[Sheepdog]

2Sheepdog

What for?

You have two choices:
1) Use your current auto hotkey script to change the menu. Then rename the matching section in all your content language files (however you are going to do this).
2) Expand your auto hotkey script a bit...

It's your choice.

I think we have a good chance that @ghisler limits the check of the language filename to the first 7 chars what would suffice to fullfill this request.

What miltates against this proposal in your opinion?

sheepdog

[Lefteous]

2Sheepdog

I think we have a good chance that @ghisler limits the check of the language filename to the first 7 chars what would suffice to fullfill this request.

Probably not before TC 7, right? I thought Auto Hotkey is the way for you and others to get an immediate solution. 2) is really easier to make this happen.

What miltates against this proposal in your opinion?

You know my opinion as you have already quoted the Unified Command System proposal. In other words: I don't want anymore workarounds and changing the menu by changing the language is definitely a workaround.

[Sheepdog]

Okay, I see. You had a bad day and have no dog to kick at.

Of course I have already renamed the language files.

2) No, it is not - at least not for me.

BTW it has been icfu who mentioned your Unified Command System although I support this, too, as you know.

But I consider this not as much as a feature request but rather as a bugfix (like icfu stated quite nice in the thread title).

Anyway, I will not further argue this topic and ask you to consider a splitting of some off-topic posts.

Have a good night

friendly

sheepdog

[Lefteous]

2Sheepdog

Okay, I see. You had a bad day and have no dog to kick at.

Pardon

Of course I have already renamed the language files.

That means you have to adapt the content of each content plugin language file after each menu file change.

No, it is not - at least not for me.

Some reasons would be fine.

But I consider this not as much as a feature request but rather as a bugfix (like icfu stated quite nice in the thread title).

A bug is a behavior not expected by the author. I really don't know what Ghisler's opinion is.

Anyway, I will not further argue this topic and ask you to consider a splitting of some off-topic posts.

BTW: As you possbly know I don't moderate this forum anymore.

[Clo]

2Lefteous
Hello Christian !

Pardon

Is your French back ? Good news !

 VG
Claude
Clo

[ghisler(Author)]

Well, I could cut off the language name before a "_" character, so it would work with both 2 and 3 character language names, e.g. wcmd_cz_custom.lng and wcmd_deu_custom.lng, what do you think?

[Sheepdog]

Well, I could cut off the language name before a "_" character, so it would work with both 2 and 3 character language names, e.g. wcmd_cz_custom.lng and wcmd_deu_custom.lng, what do you think?

I think you should cut off the name after the 7 char.

As I mentioned above there would be no problem to distinguish all language files contained in the current Installer. And if you add other languages in future you could use the Top Level Domain Extensions used for the country domains (and add a third char if you like).

Most of the language filenames already fit this standard and only one collides with it. Exeptions:

WCMD_SVN.LNG - .si (this could collide with El Salvador - what should be no problem as they use spain as official language)
WCMD_POL.LNG - .pl
WCMD_DUT.LNG - .nl
WCMD_DAN.LNG - .dk

sheepdog

[ghisler(Author)]

The top level domains are NOT a good idea. They are country abbreviations, not language abbreviations. For example, here in Switzerland, we have 4 offocial languages: German, French, Italian and Rumantsch. I also don't want to change extensions now, it would cause a lot of confusion!

[sqa_wizard]

2sheepdog: Well, what about "Kölsch" and "Plattdütsch" official language packs ? Any top level domain for this I missed ?

[sqa_wizard]

... cut off the language name before a "_" character

Nice, user-feasable anyway ...