INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: Johnny B on May 11, 2015, 03:59:04 pm
-
Non-translatable phrases:
-
More non-translatable phrases:
-
Thanks for these. I'll go through them today.
-
"Allow tagging" is marked for translation. It might just not be in your translation file?
The same thing with "Enable OSD", "Left edge jumps to top in Grid View Styles", "Load / Save View", and "No change".
-
What language are you using? I could run it through our tool that gets the latest strings from the source code.
Just let me know. Thanks.
-
I updated the Czech language file from the latest source code. It'll be in build 109.
-
Thank you Matt, Theater View examples are still not translatable though.
-
Another phrases
-
The Label Wizard can't be translated. Sorry, but it's an MFC application and the text is dialog text.
-
...it's an MFC application and the text is dialog text.
I'm not sure what do you mean by that?
-
I'm not sure what do you mean by that?
It's just an internal detail. I mean that the program is coded in an older style and the text isn't translatable.
-
I see. I assume the same applies to Label Editor and Media Editor, correct?
-
I see. I assume the same applies to Label Editor and Media Editor, correct?
Yes.
-
Next build will allow translation of the Zoomed: 100% (Fit to window) type text.
-
I add some strings that cannot be translated in the french version (20.0.113):
Null Output
Disk Writer
Separator
...and please, can you make the string by in the pane view translatable?
-
Clone Library will make a new library... should be translatable.
-
And the View window keeps english strings everywhere.
-
New strings:
New
Replace slashes in expressions
-
I cannot translate the plug-in list.
-
Clone Library will make a new library... should be translatable.
Nice find. That's been marked for translation in the next build.
-
New string:
Episode Status
-
...That's been marked for translation in the next build.
In general by that you mean the phrase will also be added to the language file(s)?
If I understand the concept correctly once anything is "marked" it can be translated by putting the exact phrase at the very end of the language file, right? The problem is if translator adds it manually and later it is added as well by developers within the file where it belongs, duplicates are made, right?
Another complication is if translator is working on updated translation file but before it is finalized and delivered to developers, new updated language file(s) are released in latest build.
In other words it would be nice if we (translators) would know ahead when new updated language files are going to be released so we could deliver updates in time. End of month perhaps?
I hope I make sense and it's not confusing.
-
New strings:
Track Info
Spectrum Analyzer
Tabby
Drive
Default
-
I think there is an error in the order of these strings.
And create levels of folder structure 2
-->
And create 2 levels of folder structure
or
-->
Number of levels for folder structure: 2
-
A question about a translation. In the french version a double space is put between on and port. This bug doesn't exist in the english version.
-
When I add a new device, 4 items are proposed for synchronization:
Smartlists
Importés récemment
Lus récemment
Meilleurs morceaux
As you can see, the string Smartlists doesn't use the translation.
-
...That's been marked for translation in the next build.
In general by that you mean the phrase will also be added to the language file(s)?
If I understand the concept correctly once anything is "marked" it can be translated by putting the exact phrase at the very end of the language file, right? The problem is if translator adds it manually and later it is added as well by developers within the file where it belongs, duplicates are made, right?
Another complication is if translator is working on updated translation file but before it is finalized and delivered to developers, new updated language file(s) are released in latest build.
In other words it would be nice if we (translators) would know ahead when new updated language files are going to be released so we could deliver updates in time. End of month perhaps?
I hope I make sense and it's not confusing.
-
Varies & Ago
-
Varies & Ago
[Varies] will be marked for translation next build.
"Ago" should already be translatable.
-
Still not translatable
-
Number of files
Duration
Plays
Disk space
are still not translatable.
-
By is still not translatable.
-
GB MB and KB don't use the translations.
-
... and the View window doesn't offer any translation.
-
EULA should be translatable (EULA = CLUF in french, for Contrat de Licence Utilisateur Final).
-
never played and never skipped should offer singular and plural forms as many language use.
-
Default and Date (release)
-
TiVo Server and Start Server
Starting...
Trying Port
Running on Port
Server Stopped
-
The format of the date is wrong in french. We don't say samedi, juillet 4 but samedi 4 juillet (see attachement below). Add a string in the translation file so we can change that format.
-
[Artist]
[Name]
[Track #]
[Genre]
[Album]
-
Drive is in the translation file but is not used everywhere.
-
In the search window, the strings can't be translated (see attachement):
Audiobook
Podcast
Test Clip
Adult
etc.
-
Too many unknow.
<unknow album>
-
I have a question. What is the meaning of the word Counties? And what is the Finder wich appears in the string Show in Finder?
I can't translate things I don't understand.
-
playlist
-
Too many unknow.
<unknow album>
Coming in the first build of MC21:
Changed: Marked "<unknown album>" and "<unknown name>" for translation.
-
TiVo Server and Start Server
Starting...
Trying Port
Running on Port
Server Stopped
Next build of MC21 will mark those strings for translation.