Translator Q&A

[klint]

Hi
I got a question from a French user who was looking for a support section in French, on this site. Do we already have such localized sections in the forum ? I couldn't find any. But I think it is a good idea, and the right place for it.
We could even mention it next to the Localization thread in the Support menu within MB.
What do you think?

[Steven]

Hi
I got a question from a French user who was looking for a support section in French, on this site. Do we already have such localized sections in the forum ? I couldn't find any. But I think it is a good idea, and the right place for it.
We could even mention it next to the Localization thread in the Support menu within MB.
What do you think?

This has come up a few times but never gained traction. The concern i have is that this is a small forum and there wont be enough active french, german, dutch forum members who could help. Maybe key parts of the wiki (such as the FAQ and Anatomy of MB sections) could be translated and linked to?

[klint]

I agree with your concern actually. And, yes, translating the FAQ and few key wiki entries like "Anatomy of MusicBee" would be a good start. But do the new FAQ page and the wiki pages support localization already?

About the menu, we have the following menu structure in the Help section:



I suppose that Online Help would lead to the localized FAQ
By the way, for consistency's sake, maybe the Forum URL could be replaced by a plain localized text ('MusicBee Forum')?

[hiccup]

i will add support for plural by adding a variation on the id by appending ".n" eg:
#Main.msg.Rtsffp# translation for singular
#Main.msg.Rtsffp.n# translation for plural

Your solution worked very well. I was able to correct all the grammatical singular/plural errors in the Dutch language file that I could find.

[hiccup]

I never used this synchronise function, and in trying to improve the translation for it, this text slightly confuses me:



Here it is saying "rewrite the files", but it will only rewrite the one selected file from this example, correct?
It will not write to other resembling files, or change anything in the database, correct?

I am then guessing that the data from the database is leading here, and that:
 - tags present in the database, but missing from the music file(s) will be added to the files
 - tags present in the music file(s) but not in the database will be deleted from the music file(s)
 - tags that exist in both, but differ in content will be copied from the database and be overwritten in the music file(s)

If this is all correct I can attempt to make this a bit clearer in this confirmation dialogue.

ps
And a minor spelling issue, shouldn't it say "differ from" instead of "differ to"?

[Steven]

i have reworded it:
CONFIRMATION: Scan {0} and re-save the files that have tag values that differ to the MusicBee database?

[hiccup]

i have reworded it:
CONFIRMATION: Scan {0} and re-save the files that have tag values that differ to the MusicBee database?

Ok.
I did some testing, and I believe my assumptions on how this syncing works in regards to 'who's boss' and what will tags will be written or deleted are correct.
Don't you agree this could be explained a bit better?
Either in this confirmation pop-up, or possibly elsewhere?

[klint]

I have applied the new .n plural management in the French translation, but I end up with truncated values, like in the examples below:



or



The SelFiles9 tag seems to be set correctly though:
#Main.msg.SelFiles9# {0} fichiers sélectionnés

And the other tags for the first example are:
#Main.msg.Rfpadt# Retirer de la liste de lecture et supprimer le fichier sélectionné
#Main.msg.Rfpadt.n# Retirer de la liste de lecture et supprimer les {0}

The whole translation file is here.

The part "fichiers sélectionnés" is missing in the resulting text.

[hiccup]

I have applied the new .n plural management in the French translation, but I end up with truncated values, like in the examples below:

The trick here is that for the 'singular' entry (no .n) you don't need to add the translated word for 'file'.
('fichier' will automatically be sourced from another element)

But for the plural one ( with .n) you will need to add the translated version of the plural word 'files' (in your case 'fichiers'), since for the .n elements, file/fichier will not be automatically retrieved and filled.

I am pretty sure this should work for French too.
I notice that you have removed {0} from the singular element #aNum.msg.Atntt#
You should leave that in for all singular elements, so 'fichier' will be auto-filled there.

[klint]

Hi
Ok thanks, I get it for the plural, "fichiers" will be hardcoded. But then, I don't understand why we couldn't hardcode "fichier" in the singular entry, similarly. Have I missed anything?

[hiccup]

I'm guessing it's for backwards compatibility.

For singular elements, you could try if replacing {0} with something like ce fichier would work for you.

[klint]

Yes, hardcoding works well for both singular and plural. I'll apply that actually.
Cheers

[sheppaul]

Steven, please don't forget to include my translation in next beta release.. :p

[Steven]

Steven, please don't forget to include my translation in next beta release.. :p

there will be one more small set of translations before that

[Roadrunner]

The button for "#Sys.btn.5BA89F9B# Add Plugin" is too small for the translated text.

I don't find the option "#PLE.ctl.D659848# show tracks when an album picture is double clicked" in the "Artwork layout preferences" dialog in MB 3.1.6420. Any hint...?