Translator Q&A

[Steven]

where are you refering to? eg. player control panel, now playing panel, artist info tab
i cant think of anything that has changed for any of those

[silasje1]

the tab with last.fm wikipedia.nl wikipedia.com and youube.com. This doesnt update itself after putting the latest exe in musibee folder. it just keeps the first played song info there.

[Steven]

its working ok for me. I really cant think of anything that would have changed to affect it.
Could you try again and if it still doesnt work can you send me a screenshot so i can see your layout

[carloscs]

With all the due respect, but such an editor doesn't deserve to be used in my opinion...
I highly recommend Notepad++

With all due respect you don't know what you're talking about

The editor I used to add the missing space at the end of that line is Notepad++. The editor I work with has a few functionalities a lot better than Notepad++. Apart from that personal opinion, I've been using it for 10 years a lot (for a few years 8+ hours a day every day) and work a lot faster with it than with Notepad++.

(or at least it should allow to disable such an option).

I can disable that option, but not on a per file basis and on a per project basis there are some troubles with the configuration (I've already submitted a bug report on this). Hmm, now that you mention it, there IS a way to do it, by putting the configuration inside the project. Thanks for reminding me of it

None of this matters much IMHO. I posted mainly because it's bad requiring spaces at the end of lines. It's too easy for the spaces to disappear/go missing/... and it's very hard for the programmer/translator to notice that those same spaces are missing.

Edit: I see that Steven added the missing space if it's missing. Thank you very much.

[Steven]

updated .exe with minor layout fixes for german localisation and a couple of missing localisations (no action required by translators)
http://www.mediafire.com/?di9whk2u5tkltj9

incremental file with new additions to the english base file in date order (not changed since yesterday)
http://www.mediafire.com/?0jewibmm0y27715

[silasje1]

could you maybe make the credits/copyright box wider? my dutch translation doenst fit

[Steven]

done for the next update

[silasje1]

The latest exe does give me problems with the artist tab not being updated. (i did clean install) and the problem is still here
http://i350.photobucket.com/albums/q429/Silasje1/lulz.jpg

[Steven]

The latest exe does give me problems with the artist tab not being updated. (i did clean install) and the problem is still here
http://i350.photobucket.com/albums/q429/Silasje1/lulz.jpg

the screenshot you have, the artist field is blank for the playing track. In that case it doesnt update the artist tab. That behavior has been the same from the start

[silasje1]

my bad

[Steven]

i've hit a snag with the windows installer software i use (WIX) which wont allow unicode filename characters in the installation scripts (i am aware of using codepage 65001 but utf-8 is not officially supported by the windows installer and WIX doesnt seem to work with it)

So that means i cant name the language files as their native language name.
There are a few ways i could tackle this and looking for opinions:
1 - name the files the english name so they contain no non-ascii chars eg. Russian, Simplified Chinese etc
    thats how the user would see the language name in the language listbox
2 - name the files the english name but have a hard-coded mapping built into MB so it gets turned into the native language name
  obviously not a great solution as it means i have to update MB for each new language supported
3 - encode the filenames eg. the russian one would be: %d0%a0%d1%83%d1%81%d1%81%d0%ba%d0%b8%d0%b9.lngc
  when loaded in the language list box it would be decoded and displayed as a user would expect
  the down side is the filename in the Localisation folder would be very obscure and so make doing manual updates difficult

i'm inclined to go with option 3 but how bad is the first option?

[Roadrunner]

What about using English filenames at least for the languages concerned, but include a new (optional) tag showing the translated text for the language?

I suggest even more new tags for:
- Translaters's name(s) in respect to their work
- Version number and state, so that one could see, if the file should be complete and current

All or some of these tags could be showed in the selection box
"Deutsch (1.2.4157 test; OrB, ...)"
"English (1.2.4159)"

[carloscs]

What about using English filenames at least for the languages concerned, but include a new (optional) tag showing the translated text for the language?

Should work, but has a downside: for showing the list MusicBee has to open every file to know how to display the title. +1 from me if it's not too slow.

[boroda]

Should work, but has a downside: for showing the list MusicBee has to open every file to know how to display the title. +1 from me if it's not too slow.

+1. I think tag with translated name of language MUST be the FIRST tag in .lng file, so it may speed up reading language names from all .lng files (i.e. MB shouldn't read every .lng completely, but only first string from each file to display localization file name/comments in native language).

[Steven]

roadrunner, thats a good suggestion but i dont want MB having to open X (30-40 eventually?) number of files when loading the language box.
the language files i will distribute with MB are compiled to a binary format - for those i will use option 2 and have the mapping in MB.
any uncompiled .lng files that are downloaded from the forum can be named as you want.