Language translation contributions invited

[BarryK]

This thread is an invitation to contribute non-English translations for the new Kirkstone-series of EasyOS.

It is easy-peasy to contribute, see this blog post:

https://bkhome.org/news/202302/the-next ... nager.html

I am just about to announce Easy 4.99, a Release Candidate for 5.0.
Download it, write to a USB-stick, choose your language at bootup, after reaching the desktop connect to the Internet, then choose "MoManager" in the "Utility" menu category.

Probably a good idea to post your intention to contribute for a particular language here first, to avoid duplicate efforts. I think maybe esmourguit will want to continue with maintaining the French translations.

EDIT 2023-06-11
The MoManager tutorial page has been updated:

"Translate EasyOS to your language"
https://easyos.org/dev/translate-easyos ... guage.html

[BarryK]

Here is the release announcement for Easy 4.99, with download links:

viewtopic.php?t=8072

While I think of it, when you use MoManager to create a .mo file, which is the translations for a particular app, there is a window that asks for an email address. There is no need to enter anything, just press the ENTER key.

And as I posted in the 4.99 announcement, I intend to speed-up that "Please wait, scanning files..." delay.

[BarryK]

Announcement for 4.101:

https://bkhome.org/news/202302/easyos-k ... or-50.html

esmourguit has tested 4.101 and contributed some fr translations. Thanks very much!

[Maybe]

Hey @BarryK! I am now slowly translating EasyOS v.5 into Russian. The .mo file with the Russian language for the rox file manager is missing. I use MOmanager to translate the interface, but rox.mo is very large and needs a lot of work. Dear Barry, is it possible to use .mo from EasyOS Dunfeel from langpack. If yes, how to do it right?

From Dmitry (Russia)

[BarryK]

Hey @BarryK! I am now slowly translating EasyOS v.5 into Russian. The .mo file with the Russian language for the rox file manager is missing. I use MOmanager to translate the interface, but rox.mo is very large and needs a lot of work. Dear Barry, is it possible to use .mo from EasyOS Dunfeel from langpack. If yes, how to do it right?

From Dmitry (Russia)

Great that you are tackling the ru translation!

Yes, you can grab any ru .mo files from elsewhere and put them into /usr/share/locale/ru/LC_MESSAGES

Then in momanager you can select the file on the left side and click "Edit" button to update the translations, if required.

[Maybe]

Hello! Here is a small job of translating EasyOS 5.x series into Russian (see attached file)

https://drive.google.com/file/d/1jgPVuv ... share_link

From Dmitry (Russia)

[BarryK]

Hello! Here is a small job of translating EasyOS 5.x series into Russian (see attached file)

https://drive.google.com/file/d/1jgPVuv ... share_link

From Dmitry (Russia)

That's great!

I have put your ru translations into woofQ; however, they have just missed out for Easy 5.2.
They will be in Easy 5.2.1 -- which likely will be in the near future.

[Maybe]

EasyOS translation update into Russian, see attached file

[BarryK]

Ha ha, you just missed out on 5.2.1, that I have just now uploaded.
But your previous translations are in 5.2.1.

Thanks for the latest.

[madanadam]

I have started (again) Turkish translation. There is wrong characters on screen at bootup messages. Can this is fixable or will I ASCII'fy special characters?

Image6185899148806791275.jpg (161.99 KiB) Viewed 3114 times

[BarryK]

I have started (again) Turkish translation. There is wrong characters on screen at bootup messages. Can this is fixable or will I ASCII'fy special characters?

Image6185899148806791275.jpg

@madanadam
That's a problem with the terminal font in the initrd.

If you click on the 'initrd' file to open it up, and look in ~/initrd-expanded/lib/consolefonts, there are a couple of png files that show what the characters look like.

If you look at ~/initrd-expanded/init script, around lines 482 and 493, you can see which console font gets loaded.

...now that is interesting, "tr" isn't in the list, so neither of those fonts get loaded. Only the kernel inbuilt font is being used.

OK, you could experiment with adding "tr", save 'init', click on the 'initrd' file to update, then reboot.

You could try both fonts, see which one renders Turkish characters better.

Thanks for helping out with translating.

[madanadam]

Hi
I added "tr" after "sl" at line 485 and 497. Now I will try to add Turkish console keyboard option at kmap selection section

[Maybe]

EasyOS Russian translation update, see attached file:

From Dmitry (Russia)

[BarryK]

EasyOS Russian translation update, see attached file:

From Dmitry (Russia)

Thanks, it will be in the upcoming 5.2.2.

[MrBoom]

Hi @BarryK!
I made a small Spanish translation update:

newtranslations-es-20230520.tar.gz

Spanish (es) translation update.

(11.67 KiB) Downloaded 80 times

EasyOS (and MoManager!) are awesome, thank you!

[BarryK]

MrBoom,
That's great!
I have added the translations and they will be in Easy 5.3.1, maybe released in about a week.

[MrBoom]

MrBoom,
That's great!
I have added the translations and they will be in Easy 5.3.1, maybe released in about a week.

Great, thank you!

So far I've translated QuickSetup, EasySetup, EasyApps, the "Save Session" dialog, and the names of most menu categories. I didn't upload the first tarball (20230519) yesterday because I thought previous translations were included in the new tarballs, but I think that's not how it works (I believe the tarball I uploaded in my last post was missing a few translations).

I think it'll be easier if I upload all of them (including the tarball with all the translations) to a folder in Drive.

Here's the link:
https://drive.google.com/drive/folders/ ... jYutXOkns4

As a side note, the /usr/sbin/ask-save-zram1 (savesession.mo WOOF) script created by MoManager is not showing the "Click SAVE SESSION button to save now:" text (it's the line that appears at the bottom-left -next to the buttons- in the save session dialog), so I couldn't translate that last line yet.

[BarryK]

As a side note, the /usr/sbin/ask-save-zram1 (savesession.mo WOOF) script created by MoManager is not showing the "Click SAVE SESSION button to save now:" text (it's the line that appears at the bottom-left -next to the buttons- in the save session dialog), so I couldn't translate that last line yet.

Thanks for reporting that. I have fixed the script.
The fixed script will be in 5.3.1.

[MrBoom]

As a side note, the /usr/sbin/ask-save-zram1 (savesession.mo WOOF) script created by MoManager is not showing the "Click SAVE SESSION button to save now:" text (it's the line that appears at the bottom-left -next to the buttons- in the save session dialog), so I couldn't translate that last line yet.

Thanks for reporting that. I have fixed the script.
The fixed script will be in 5.3.1.

Glad to help, thank you!

I've updated the translation again (one of the newtranslations tarballs is splitted because I had to reboot the machine). The link is the same as before.

[BarryK]

I've updated the translation again (one of the newtranslations tarballs is splitted because I had to reboot the machine). The link is the same as before.

Good, got them.

[bullpup]

Any need for Dutch translations?

[BarryK]

Any need for Dutch translations?

That's entirely up to you and anyone else who wants a Dutch EasyOS.
Some big apps like LibreOffice already have nl translation, but there's heaps of little apps and scripts that don't.

[MrBoom]

I had to reinstall EasyOS (I'm on 5.3.1 now), and I lost some of the translation work I had done in 5.3, as I was a little bit ahead of the translation included in 5.3.1.

However, I still have the last "translations" tarball, so I don't expect this to be a problem at all.

If I understand correctly, I should be able to bring back the last translation from the tarball if I copy the .mo files from the tarball to /usr/share/locale/es/LC_MESSAGES, the .desktop files to /usr/share/applications, and so on...I think I should look at the paths in the tarball and then copy every file to the right location.

Is this correct? And if so...Is there anything I should not do, or are there any files I should not overwrite while recovering the translation files with this method?

[BarryK]

I had to reinstall EasyOS (I'm on 5.3.1 now), and I lost some of the translation work I had done in 5.3, as I was a little bit ahead of the translation included in 5.3.1.

However, I still have the last "translations" tarball, so I don't expect this to be a problem at all.

If I understand correctly, I should be able to bring back the last translation from the tarball if I copy the .mo files from the tarball to /usr/share/locale/es/LC_MESSAGES, the .desktop files to /usr/share/applications, and so on...I think I should look at the paths in the tarball and then copy every file to the right location.

Is this correct? And if so...Is there anything I should not do, or are there any files I should not overwrite while recovering the translation files with this method?

Yes, I think that should be ok.

[MrBoom]

I had to reinstall EasyOS (I'm on 5.3.1 now), and I lost some of the translation work I had done in 5.3, as I was a little bit ahead of the translation included in 5.3.1.

However, I still have the last "translations" tarball, so I don't expect this to be a problem at all.

If I understand correctly, I should be able to bring back the last translation from the tarball if I copy the .mo files from the tarball to /usr/share/locale/es/LC_MESSAGES, the .desktop files to /usr/share/applications, and so on...I think I should look at the paths in the tarball and then copy every file to the right location.

Is this correct? And if so...Is there anything I should not do, or are there any files I should not overwrite while recovering the translation files with this method?

Yes, I think that should be ok.

Done! Everything seems to be fine.

I've uploaded several files, the menu is fully translated now: https://drive.google.com/drive/folders/ ... jYutXOkns4

If I remember correctly, translations-es-20230524.tar.gz was the last file created in 5.3.
From that point onwards, all files should have been created with 5.3.1 (translations-es-20230603.tar.gz being the last one so far).

MoManager was creating empty desk_strings.es and menu_strings.es files when I tried to translate them (it does the same thing with all the SSS domains files). I found the text in the original files with pFind. I copied it & pasted it into the empty .es files, and then translated them & saved them. Apparently, it worked just fine (desk_strings and menu_strings are translated now).

I also added two missing strings in desk_strings.es, one for "share" and another one for "kirkstone". If there is anything wrong with this procedure, let me know and I'll undo the changes immediatly.

[BarryK]

MrBoom,
Thanks, got them. Expect them in Easy 5.3.2, due out very soon.

[madanadam]

I have initialized Turkish translation. I will correct after automatic trasnlation. It's only a starting point

newtranslations-tr-20230605.tar.gz

(35.98 KiB) Downloaded 64 times

[BarryK]

I have initialized Turkish translation. I will correct after automatic trasnlation. It's only a starting point
newtranslations-tr-20230605.tar.gz

Thanks, it will be in next release, coming soon.

[madanadam]

Latest Turkish Language files. Now menu categories are totally translated :

[BarryK]

Latest Turkish Language files. Now menu categories are totally translated :

Thanks.
It is easier for me if you just send the "newtranslations" tarballs. Do you still have them?

In Easy 5.4.1, MoManager now creates backups of the newtranslations tarballs.
The tarball is of the format newtranslations-tr-20230617.tar.gz, but if you rerun momanager on the same day, when you exit if it sees an earlier newtranslations tarball, it will rename it to newtranslations-tr-20230617-1.tar.gz
In fact, there can also be backups of backups, "-2", "-3"

Note, the MoManager page has been updated recently, with request to only send the newtranslations tarballs:

https://easyos.org/dev/translate-easyos ... guage.html