Project

General

Profile

Actions

Bug #10356

closed

Some translations not loaded

Added by Dan Smith over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
02/07/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next (py3)
Model affected:
All
Platform:
Windows
Debug Log:
I read the instructions above:

Files

debug.log (910 Bytes) debug.log with CHIRP 20230208 MELERIX ., 02/08/2023 11:43 PM
untranslated strings 1.png (79 KB) untranslated strings 1.png with CHIRP 20230209 MELERIX ., 02/09/2023 07:01 PM
clipboard-202302091603-6vqbf.png (47.2 KB) clipboard-202302091603-6vqbf.png Dan Smith, 02/10/2023 12:03 AM
developer mode on.png (19.4 KB) developer mode on.png MELERIX ., 02/12/2023 03:16 AM
developer mode off.png (16.8 KB) developer mode off.png MELERIX ., 02/12/2023 03:16 AM
Actions #1

Updated by Dan Smith over 1 year ago

FYI @MELERIX ., let's continue discussion here. I've got fixes for this that I will push for tomorrow. There were some errors in your logs related to translations that I have not reproduced, but I've definitely fixed some stuff and get a fully-translated UI on Windows for es_ES. If you could test tomorrow's build and attach a debug log, that would be appreciated.

As mentioned, the splash "welcome" tab is an image, so it will not be translated. Also some driver messages (in the clone box) need to be marked and translated before they will work.

Actions #2

Updated by Dan Smith over 1 year ago

Also, I hadn't done a full message merge in a while, so your recent es_ES translation may be missing some more strings that are now present.

Actions #3

Updated by Dan Smith over 1 year ago

@MELERIX . did you get a chance to test today's build?

Actions #4

Updated by MELERIX . over 1 year ago

well, I've tested today few hours ago with CHIRP 20230208 and now some translation that were previously properly translated now are non-translated at all xD

no idea what could be causing this, but I'll test again with the new next build to see if the issue persists or not.

Actions #5

Updated by Dan Smith over 1 year ago

Can you grab a debug log? Like I said, there were errors in your log that I could not reproduce at all, so I'm curious to see a log on today's build. I was certainly not expecting it to be worse, but we need to chase that down regardless.

Actions #6

Updated by MELERIX . over 1 year ago

Actions #7

Updated by MELERIX . over 1 year ago

maybe we need to rename "es_ES" to just "es" to make it as a global spanish translation, because "es_ES" is for spanish (spain) only, and probably that is causing the issue.

Actions #8

Updated by Dan Smith over 1 year ago

So your system thinks it is es_CL, so I guess that's why it's not loading.

If you go into the installed chirp directory, under chirp/locale you should see the es_ES directory. You could try renaming it to either es or es_CL and see if it will load.

Actions #9

Updated by MELERIX . over 1 year ago

well, my system is "es_CL" because I'm in Chile :P

and yes, I've renamed the translation to "es" and now the translation is working fine.

[2023-02-08 20:59:25,910] chirp.logger - DEBUG: CHIRP next-20230208 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-02-08 20:59:26,195] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230208 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-02-08 20:59:26,196] chirp.wxui - DEBUG: System locale: es_CL (740)
[2023-02-08 20:59:26,198] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: es_CL (de,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from D:\APPS DE RADIOCOMUNICACIONES\chirp-next-20230208-win32\chirp\locale
[2023-02-08 20:59:26,200] chirp.wxui - DEBUG: Translation loaded=True for wxstd: es_CL (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-02-08 20:59:27,015] chirp.wxui.main - INFO: Server reports next-20230208 is latest

btw, there are different variants of Spanish Langs, such as es_ES, es_CL, es_AR, es_BO, es_US etc, but I'm not sure if needed to make a translation for each one separately, so making a main "es" translation with neutral Spanish I guess is enough for all Spanish Langs, unless somebody else wants to make an specific translation for his own Spanish lang variation later.

Actions #10

Updated by Dan Smith over 1 year ago

well, my system is "es_CL" because I'm in Chile :P

I didn't know, and I had to look up what es_CL was :) I assumed Spain because es_ES but good to know...

and yes, I've renamed the translation to "es" and now the translation is working fine.

Okay, cool.

[2023-02-08 20:59:25,910] chirp.logger - DEBUG: CHIRP next-20230208 on Win32 (Unknown 10.0:19045) (Python 3.10.8)
[2023-02-08 20:59:26,195] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.19045-SP0 // CHIRP/next-20230208 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-02-08 20:59:26,196] chirp.wxui - DEBUG: System locale: es_CL (740)
[2023-02-08 20:59:26,198] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: es_CL (de,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from D:\APPS DE RADIOCOMUNICACIONES\chirp-next-20230208-win32\chirp\locale
[2023-02-08 20:59:26,200] chirp.wxui - DEBUG: Translation loaded=True for wxstd: es_CL (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-02-08 20:59:27,015] chirp.wxui.main - INFO: Server reports next-20230208 is latest

btw, there are different variants of Spanish Langs, such as es_ES, es_CL, es_AR, es_BO, es_US etc, but I'm not sure if needed to make a translation for each one separately, so making a main "es" translation with neutral Spanish I guess is enough for all Spanish Langs, unless somebody else wants to make an specific translation for his own Spanish lang variation later.

Yes, and I believe that we can make your translation be the base es one and if anyone cares for one of the others, they can copy it and do the work and that one will take precedent for their es variant.

I'll get it moved now, thanks!

Actions #11

Updated by MELERIX . over 1 year ago

now testing with CHIRP 20230209 and the following strings are missing (the ones in red color), and others strings (the ones in blue color) have issues to fit in the UI, I guess due the lenght of text, so maybe "auto-size" or something like that could solve the issue.

Actions #12

Updated by Dan Smith over 1 year ago

Ah, okay yeah. The red ones are generated from internal column names, so they're not marked for translation. That's easy to fix.

The blue ones are because I convert spaces to newlines in long names to make them wrap. In english we only ever have one space, but yours with two end up as three lines. Just making them only two lines should fix it.

Otherwise lots more is properly translated than before right?

Actions #13

Updated by MELERIX . over 1 year ago

I see, well... in Spanish some translated phrases needs to have two spaces due grammatic, for example "Tuning Step" to "Paso de sintonización", and if I translate it as "Paso sintonización" there will be no issues in the UI, but.. the phrase in Spanish will be incorrectly translated xD

I was thinking that "auto-size" could be used for columns and could solve the issue so the columns can automatically resize according to text length, but I'm not sure if possible in CHIRP UI, so is just an idea/suggestion.

Actions #14

Updated by Dan Smith over 1 year ago

I see, well... in Spanish some translated phrases needs to have two spaces due grammatic, for example "Tuning Step" to "Paso de sintonización", and if I translate it as "Paso sintonización" there will be no issues in the UI, but.. the phrase in Spanish will be incorrectly translated xD

Oh, I understand, I meant only convert the first space to a newline, not remove the spaces.

I was thinking that "auto-size" could be used for columns and could solve the issue so the columns can automatically resize according to text length, but I'm not sure if possible in CHIRP UI, so is just an idea/suggestion.

Yeah, the columns do auto-size horizontally, just not vertically. Even if they did, a whole line for "de" is too much wasted space. Here's what it looks like now (tomorrow):

Actions #15

Updated by MELERIX . over 1 year ago

oh, thanks, that looks much better ;)

Actions #17

Updated by Dan Smith over 1 year ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF