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

Lakrits

  • Jr. Member
  • **
  • Posts: 62
Hi,

There are two unlocalised strings in

Settings > Now Playing > section "Playback" > popup "Customise notification popup".

It's the two strings transparent and opaque (see screen-shot below, strings marked in red). Though appealing to an anglo- and francophiliac like myself (i.e. the UK and France, not the UK and El Generalissimo), they should probably be released to the translators for the usual linguistic hacking and slashing.



Lakrits
Spikar'u'nte inglish? Föredrar du helt enkelt svenska?

   Du hittar svenska språkfiler i den här tråden.
---
Non loqueris lingua Anglorum? Grammaticus fastuosus Oxbrigiae es?

  In hoc filum documenta linguae Latinae nancisceris.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
thats fixed for the next update with no further action required by yourself

Lakrits

  • Jr. Member
  • **
  • Posts: 62
thats fixed for the next update with no further action required by yourself
What can I say… You're too fast for me  :)
Spikar'u'nte inglish? Föredrar du helt enkelt svenska?

   Du hittar svenska språkfiler i den här tråden.
---
Non loqueris lingua Anglorum? Grammaticus fastuosus Oxbrigiae es?

  In hoc filum documenta linguae Latinae nancisceris.

Lakrits

  • Jr. Member
  • **
  • Posts: 62
[I couldn't find these questions (or anything like them) when searching the forums, so if I've missed answers to them already present, I apologise in advance.]

In the English (template) language file, I was from the very beginning struck by the use of lower-case characters as initials in strings. Since there also are a lot of strings with upper-case initials, with no apparent structural thought behind the mixed use of cases, I assume there is an basic idea of GUI design here. Unfortunately, I fail to see it, albeit I'm not known to be very responsive to aesthetic ideas (i.e. I'm pretty square). Therefore, I have kept the structure in my translation, as it is in the template file. Hence, my questions are two:

1. Is there a thought behind this seemingly irrational blend between lower- and upper-case initials in strings?

2. Is it okay for me, as the translator, to only use upper-case characters as initials where applicable, or would I in doing so destroy the look and feel of MusicBee?

The poorly hidden, mumbled question here is of course, "may I 'correct' the strings that are led by lower-case characters?"

Best regards,

Lakrits/Mikael
Last Edit: September 12, 2012, 09:41:02 PM by Lakrits
Spikar'u'nte inglish? Föredrar du helt enkelt svenska?

   Du hittar svenska språkfiler i den här tråden.
---
Non loqueris lingua Anglorum? Grammaticus fastuosus Oxbrigiae es?

  In hoc filum documenta linguae Latinae nancisceris.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
The lower casing is for prompts, and mixed casing for values - its just a personal preference i have. The german translation always uses Mixed case because i gather its important for that language. Also if you have a strong feeling about always using mixed case then thats fine with me as well

jistme

  • Guest
I understand the literal text of this pop-up message, but I don't quite understand it's meaning or use?
Is it ment as a warning, a confirmation, or maybe something that might better fit a 'balloon hoover over' message?



jistme

  • Guest
I can find no entry for this pop-up in the translation file:



Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973
i have added support for this in localisation file for the next udpate:
#Sys.msg.Yntsaaf#   You need to select an action first.

jistme

  • Guest
i have added support for this in localisation file for the next udpate:
#Sys.msg.Yntsaaf#   You need to select an action first.

'Information' in the titlebar needs one too.

Roadrunner

  • Sr. Member
  • ****
  • Posts: 377
Some months ago I translated additional Theater Mode words, for example

     #TMP.txt.by#   von

which are included in the German-2.xx.lng files. It looks like all these translations are not part of the new Deutsch.lngc (tried out with MB 2.0.4636). Only the ones, you have predefined like

    #TMP.txt.Up next...#   Demnächst...

are translated (both of the upper examples can be tested with "Album and Artist" view). Any possibility to include the others as well?

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34973



Lakrits

  • Jr. Member
  • **
  • Posts: 62
The lower casing is for prompts, and mixed casing for values - its just a personal preference i have. The german translation always uses Mixed case because i gather its important for that language. Also if you have a strong feeling about always using mixed case then thats fine with me as well
Oki doki.

Swedish also uses mixed case, so part of my question concerns that. But mostly it's my disability. It is difficult for me to read strings that start with a lower case letter – they are harder to focus on for some reason – even though I agree on the aesthetics you want to implement.

I'll upload a new version in a while :)

Lakrits/Mikael
Spikar'u'nte inglish? Föredrar du helt enkelt svenska?

   Du hittar svenska språkfiler i den här tråden.
---
Non loqueris lingua Anglorum? Grammaticus fastuosus Oxbrigiae es?

  In hoc filum documenta linguae Latinae nancisceris.

Xyzzy

  • Sr. Member
  • ****
  • Posts: 403
It seems #Main.menu.CoPl# is also used for Preferences>General>Minimise to list. Could the list entry get a separate string?

Which string is used for Send To>Device menu item? Is it used uniquely in this place?

Last Edit: October 03, 2012, 02:18:23 PM by Xyzzy