If I understand right. Just use notepad++ with utf-8, and save and send like it is. You will process the rest. No problem. I'll do itF1RMB wrote: ↑Thu Aug 03, 2023 9:36 amHi,
I'm sorry, but you killed the encoding. You should use UTF-8.
I suggest you to use notepad++ (if you're using Windows), select UTF-8 in the Encoding menu.
The file you uploaded uses non standard extended ASCII text, hence it's unusable in its current state.
Cheers.
---
Daniel
Updated localisation files
Re: Updated localisation files
Last edited by TA2RU on Thu Aug 03, 2023 2:12 pm, edited 3 times in total.
Re: Updated localisation files
If the resulting file is still correct regarding the texts you translated, yes.TA2RU wrote: ↑Thu Aug 03, 2023 1:20 pmIf I understand right. Just use notepad++ with utf-8, and save and send like it is. You will process the rest. No problem. I'll do itF1RMB wrote: ↑Thu Aug 03, 2023 9:36 amHi,
I'm sorry, but you killed the encoding. You should use UTF-8.
I suggest you to use notepad++ (if you're using Windows), select UTF-8 in the Encoding menu.
The file you uploaded uses non standard extended ASCII text, hence it's unusable in its current state.
Cheers.
---
Daniel
Cheers.
---
Daniel
Re: Updated localisation files
This should be OKF1RMB wrote: ↑Thu Aug 03, 2023 2:05 pmIf the resulting file is still correct regarding the texts you translated, yes.TA2RU wrote: ↑Thu Aug 03, 2023 1:20 pmIf I understand right. Just use notepad++ with utf-8, and save and send like it is. You will process the rest. No problem. I'll do itF1RMB wrote: ↑Thu Aug 03, 2023 9:36 amHi,
I'm sorry, but you killed the encoding. You should use UTF-8.
I suggest you to use notepad++ (if you're using Windows), select UTF-8 in the Encoding menu.
The file you uploaded uses non standard extended ASCII text, hence it's unusable in its current state.
Cheers.
---
Daniel
Cheers.
---
Daniel
Re: Updated localisation files
Hi,
Yes, the encoding looks fine, thanks.
I quickly checked the length of the strings, and some are too long (we're limited to 16 characters), sometimes less (in case of option value, etc).
Cheers.
---
Daniel
Yes, the encoding looks fine, thanks.
I quickly checked the length of the strings, and some are too long (we're limited to 16 characters), sometimes less (in case of option value, etc).
Cheers.
---
Daniel
Re: Updated localisation files
Hi,
I checked lenght of string, but I think I missed some of them. I'll do it again.
Just one more question. Is the quotation included characters or should I count without them
With a change I'll inform you
Ilker
Re: Updated localisation files
Hi,
No, the quotation marks aren't included.
Cheers.
---
Daniel
No, the quotation marks aren't included.
Cheers.
---
Daniel
Re: Updated localisation files
Last version of catalan files
ThanksRe: Updated localisation files
.daytime_theme_day = "Tema dia", // MaxLen: 16
.daytime_theme_night = "Tema nit", // MaxLen:
.theme_chooser = "Elecció tema", // Maxlen: 16
.theme_fg_text_input = "Text Inici", // MaxLen: 16 (+ colour rect)
.theme_fg_splashscreen = "Front Inici", // MaxLen: 16 (+ colour rect)
.theme_bg_splashscreen = "Fons Inici", // MaxLen: 16 (+ colour rect)
.daytime_theme_night = "Tema nit", // MaxLen:
.theme_chooser = "Elecció tema", // Maxlen: 16
.theme_fg_text_input = "Text Inici", // MaxLen: 16 (+ colour rect)
.theme_fg_splashscreen = "Front Inici", // MaxLen: 16 (+ colour rect)
.theme_bg_splashscreen = "Fons Inici", // MaxLen: 16 (+ colour rect)
Re: Updated localisation files
Hi,
Thanks.
I checked the diff, there are even mode.
Soon, the new format will be released, the advantage is that only one file per language is needed.
Cheers.
---
Daniel
Thanks.
I checked the diff, there are even mode.
Soon, the new format will be released, the advantage is that only one file per language is needed.
Cheers.
---
Daniel