Author Topic: Translator Q&A  (Read 529268 times)

Roadrunner

  • Sr. Member
  • ****
  • Posts: 377
But the issues I raise in my postings on translating issues are not necessarily factual errors or omissions, and will only possibly be implemented on Stevens discretion.
... which might be similar to some other languages as well...
So, unless I am mistaken, wouldn't it suffice for other translators such as you to just download the most recent language file Steven released, and look for implemented changes there? (notepad++'s compare plugin is great for that)
I just use the delta, so no need to compare. But that doesn't mather in this case: If I find something not or not correctly translated/translatable, I have to look where the problem is. If I see, that you or others had the same issue, I don't need to investigate more time into that. So your posts are really helpful for me! Therefore it's not a question of bothering or not (there're NOT), it's just a question of how easily helpful :)

Btw: In my version 3.1.6335 of MB there's no dropdown behind "do not crossfade"... ???

hiccup

  • Hero Member
  • *****
  • Posts: 9107
...., it's just a question of how easily helpful :)

Btw: In my version 3.1.6335 of MB there's no dropdown behind "do not crossfade"... ???

For a next time I will try to do it in a more easily helpful manner ;-)
For this run I believe I am pretty much done now.
I am going to switch back to English now and not look back for a while.

Thanks for reporting on the 'crossfade' issue.
It looks like a very ugly glitch my setup is experiencing.
It might be due to me accidentally running a 3.0 installer over my 3.1 installation yesterday.
This is what it now looks like in the English, and in my translated MB:


hiccup

  • Hero Member
  • *****
  • Posts: 9107
@Roadrunner,

Sometimes when in need of ideas on difficult translations, I take a look at other translations for inspiration, such as your German one.
In case you would like to do the same sometimes, here is the most recent version of mine:
https://1drv.ms/u/s!AkA0tSv_UzTAgwWQnKa0DAWncXUi


Roadrunner

  • Sr. Member
  • ****
  • Posts: 377
Hi Hiccup

Thx, sometimes I really use your or other up to date files to see, if something is translatable or if it's my own fault :-[ . Or if a button or something is to small for others as well. But Dutch is unfortunately not a language which I'm talking... So there couldn't be much inspiration for translation (or would be too much inspiration)... ::)

boroda

  • Hero Member
  • *****
  • Posts: 5171
I am not certain on the intention of:
#Main.msg.MBLLFoTo#   <Language> Forum Topic

That seems a good idea for languages that have a general discussion board in their own language.

But the option to provide a link in the translation file is described as: 'your forum topic for localisation'
That suggests it is intended for a link to the thread that only concerns translation issues?

In the first case, for most languages that entry has no purpose, since they don't have a localised general discussion or support board.
In the second case I think such a link is only interesting to 0.0001% of MB users?
suggest the 2nd case and i agree that its not very useful for users, but it might be very useful for translator(s) and thus very useful for all users again.

klint

  • Sr. Member
  • ****
  • Posts: 426
Hi

2 small things in the "Locate Missing Files" panel:


1) The button is not large enough to display "Appliquer les modifications" in French for instance

2) The column title reads "Differences" in the original version, while it actually show matches rather than differences. Or? :)

Thanks

klint

  • Sr. Member
  • ****
  • Posts: 426
One question about a past localization entry: what is the English version of the #aSplit.msg.diar# string? I have 2 versions in my archives, that do not match btw French and English

Thanks

PS: what is the original English version by the way? English or English US? Sorry to ask ;)!

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
1) The button is not large enough to display "Appliquer les modifications" in French for instance

2) The column title reads "Differences" in the original version, while it actually show matches rather than differences. Or? :)
1) i am going to change the wording to "Proceed" as "Apply Changes" wasnt a good choice in the first place
2) use "similarities" or "status" if you want - its really a mixture of both

hiccup

  • Hero Member
  • *****
  • Posts: 9107
One question about a past localization entry: what is the English version of the #aSplit.msg.diar# string? I have 2 versions in my archives, that do not match btw French and English

Originally it was:
display artist:

But it was changed to:
display {0}:

Quote
PS: what is the original English version by the way? English or English US? Sorry to ask ;)!

The creator of MusicBee is from the United Kingdom, so 'English' is the origin.
'English US', was added later on by a member, so to accommodate for some intercontinental differences such as 'equalizer' vs. 'equaliser', 'color' vs. 'colour', etc.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
'Album Artist' here has no translation entry:
it should do:
#Main.field.31# Album Artist

'Error' in the header has no translation entry:
thats added for the next translation file

'Collapse' here has no translation entry.
thats added for the next translation file
Last Edit: May 20, 2017, 07:42:02 PM by Steven

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
The messages for #Scan.msg.ScUpdCashFi# and #Scan.msg.CRefthitag# cannot be translated correctly to German because they have been combined with #Main.msg.SelFiles1# or #Main.msg.SelFiles9#:

#Main.msg.SelFiles1# is in German correctly "1 Datei ausgewählt" and #Main.msg.SelFiles9# "{0} Dateien ausgewählt".

But in the context of a sentence they should be changed to:

#Scan.msg.ScUpdCashFi#
1: "BESTÄTIGUNG: 1 ausgewählte Datei scannen und mit den Tag-Werten, die von der MusicBee-Datenbank abweichen, neu schreiben?"
more: "BESTÄTIGUNG: {0} ausgewählte Dateien scannen und mit den Tag-Werten, die von der MusicBee-Datenbank abweichen, neu schreiben?"
how about translating this instead?
CONFIRMATION: Scan the selected files and rewrite the files with tag values that differ to the MusicBee database?

hiccup

  • Hero Member
  • *****
  • Posts: 9107
'Album Artist' here has no translation entry:
it should do:
#Main.field.31# Album Artist

It doesn't, the same with other languages.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
'Album Artist' here has no translation entry:
it should do:
#Main.field.31# Album Artist

It doesn't, the same with other languages.
i just tried with the German and the French translations and both are fine for Album Artist. Which languages did you try with and also can you confirm your screenshot is refering to the Library Explorer?

hiccup

  • Hero Member
  • *****
  • Posts: 9107
i just tried with the German and the French translations and both are fine for Album Artist. Which languages did you try with and also can you confirm your screenshot is refering to the Library Explorer?

No, it's the thumbnail browser in the left main panel.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
the screenshot doesnt look like the thumbnail browser but in any case german and french are fine there as well
perhaps you are showing a custom tag that you have named "Album Artist"?