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

hiccup

  • Hero Member
  • *****
  • Posts: 9107
could you add (or return?) support for empty localization strings?
Maybe I misunderstand the issue, but couldn't you simply enter a space for the translation string?

boroda

  • Hero Member
  • *****
  • Posts: 5171
yes, i can in *this* case. but it seems that i rather frequently had been using empty strings earlier (this doesn't work anymore) and spaces will add extra separator between text parts/parameters.

hiccup

  • Hero Member
  • *****
  • Posts: 9107
and spaces will add extra separator between text parts/parameters.
Then use zero-width spaces?

boroda

  • Hero Member
  • *****
  • Posts: 5171
i don't like invisible characters. i'll try to use spaces.

hiccup

  • Hero Member
  • *****
  • Posts: 9107
i'll try to use spaces.
Make sure to verify if they haven't got lost after the xml was compiled.

Or maybe Steven can confirm if trailing spaces get removed or not when compiling the translation files.
Last Edit: August 10, 2022, 04:16:51 PM by hiccup

hiccup

  • Hero Member
  • *****
  • Posts: 9107

hiccup

  • Hero Member
  • *****
  • Posts: 9107
Missing from translation file:



Also notice that 'Trefwoorden'  (Keywords) is displayed three times, also for Mood and Occasion.

(I think I renamed those fields to something else, and it doesn't get picked up)
Last Edit: September 02, 2022, 07:11:35 AM by hiccup

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34974
the new translations will be added to the next file and the 2 duplication's fixed for the next update

boroda

  • Hero Member
  • *****
  • Posts: 5171
notes about last new3.5.txt.

it seems that:


#Tag.ctl.origalb#      original album:


is not used. instead lowecased:


#Main.field.177#   Original Album


is used.

---------------------------

"Search Field Shortcuts" is not localizable:


Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34974
"Search Field Shortcuts" is in the file already as: #Main.menu.SeaFiSho#
and looking at the code #Tag.ctl.origalb# is being used
Not sure what is going on. Lets see if others report the same

boroda

  • Hero Member
  • *****
  • Posts: 5171
"Search Field Shortcuts" is in the file already as: #Main.menu.SeaFiSho#
yes, my fault. i've accidentally commented out this entry.

and looking at the code #Tag.ctl.origalb# is being used
Not sure what is going on. Lets see if others report the same


hiccup

  • Hero Member
  • *****
  • Posts: 9107
I have difficulties understanding this one:
#Sys.ctl.B93499E5#   link to the source picture

It shows up under 'downloaded album cover storage'.
So, after it was downloaded, the downloaded image is getting linked to the source picture?
What is the source picture?

hiccup

  • Hero Member
  • *****
  • Posts: 9107
and looking at the code #Tag.ctl.origalb# is being used
Not sure what is going on. Lets see if others report the same

I am seeing the same as Boroda is reporting.
#Main.field.177# is being displayed both in the main panel and in the Tag Editor (tags 2).
The only difference is that in the Tag Editor it's transformed to lower case.

Steven

  • Administrator
  • Hero Member
  • *****
  • Posts: 34974
regarding original album, i realise now that the prompt is overridden with the field header. That was because the user can override the label. Happy to remove that so it shows the Tag.ctl.origalb value instead

hiccup

  • Hero Member
  • *****
  • Posts: 9107
regarding original album, i realise now that the prompt is overridden with the field header.
The fact that the Tag Editor panel now follows tag name changes was an improvement.
Does this mean that translation elements such as Tag.ctl.origalb could best be considered obsolete?
And if so, would that also apply to all other tag names that are showing in the Tag Editor?