Bug #586
open
Illegal characters in translations
70%
Description
> I read this post : > > https://mail.gna.org/public/doudoulinux-lang/2011-09/msg00018.html > and checked the French translation of doudou-rewrite-ascii and > splashy-themes-doudoulinux. > > Of course I found some non-ascii characters in > splashy-themes-doudoulinux. > > In the absence of other posts on the list about this, can you confirm > that the non-ascii characters are not allowed in this file? They are not allowed in doudou-rewrite-ascii but allowed in splashy-themes-doudoulinux as long as the font we're using to write text into the image supports the corresponding UTF-8 characters. Note that splashy-themes-doudoulinux switches of font for at least Chinese and Cyrillic for this reason. Anyway I noticed few weeks ago on Transifex that doudou-rewrite-ascii has some languages with non-ASCII chars. This will break the messages in the very first screen and then this is a bit weird. Translators should correct them on Transifex, unless the library unaccent shows good results on them (but who can check this in every language?).
Le dimanche 17 juin 2012 à 09:35:21, Jean-Michel Philippe a écrit : > > > Anyway I noticed few weeks ago on Transifex that doudou-rewrite-ascii > > > has some languages with non-ASCII chars. This will break the messages in > > > the very first screen and then this is a bit weird. Translators should > > > correct them on Transifex, unless the library unaccent shows good > > > results on them (but who can check this in every language?). > > > > The list of languages involved is attached. Project maintairers may > > modify any resources, but if none is available I could do with your > > approval. > > > > Thanks for this diagnosis. I propose we wait for a week to let people > answer. Alternatively, you may try to contact them using Transifex mails > since not everybody has registered our mailing lists. After a week, the translations have not been corrected so I sent today a message to each translator concerned to solicit their help.
Files
Updated by Stéphane Aulery over 12 years ago
Remains fa, pt, sr@latin, sr, sv, and te languages to process.
Updated by Jean-Michel Philippe over 12 years ago
I suggest we use “unaccent” for languages using a Latin alphabet (pt, sr@latin, sv). Moreover the Cyrillic version of Serbian should use the same texts as the Latin one. For Persian and Telugu, it may happen that transliteration is nonsense, which would require to use the English texts. We need to check with translators…
By the way, I understood that Grub2 is able to display any Unicode character. Currently the DDL boot loader is Syslinux. I think it is recommended on LiveCD's but I don't know for what reason. And this doesn't mean that Grub wouldn't work. I even think I had made successful trials a long time ago with Grub as the CD boot loader. If you have the courage and time to make investigations, this would be welcome ;).
Updated by Stéphane Aulery over 12 years ago
For sv, we seek a solution with the translator. As for the others I raise this weekend.
Should I look for documentation to confirm that it is possible to use Grub (2) with unicode characters and it was done, or do I modify a version of "LiveCD DoudouLinux" to test this solution?
I have no idea how to do the second.
Updated by Stéphane Aulery over 12 years ago
I sent the message to the relevant translators (see attachment). I think the Persian translator will not respond because his account has no activity for more than 9 months.
Updated by Jean-Michel Philippe over 12 years ago
For sv, we seek a solution with the translator. As for the others I raise this weekend.
Ok, good job!
Should I look for documentation to confirm that it is possible to use Grub (2) with unicode characters and it was done, or do I modify a version of "LiveCD DoudouLinux" to test this solution?
I have no idea how to do the second.
The quickest start is to check in the documentation of Grub. If you want to test it for real, in my opinion the easiest way with less risks is to perform a real installation of DDL into a virtual machine with grub as a boot loader (the default!), see on our blog:
http://blog.doudoulinux.org/post/2012/02/28/Using-Debian-to-install-DoudouLinux
Updated by Stéphane Aulery about 12 years ago
- Priority changed from Urgent to High
- % Done changed from 50 to 70
Remains fa, pt and te languages to process.
Updated by Stéphane Aulery about 12 years ago
According to the manual, Grub2 supports utf-8 internally (https://www.gnu.org/software/grub/manual/grub.html). It should also be added unicode font file (unicode.pf2) reached either at startup. Archlinux Grub2 manual describes how to do (https://wiki.archlinux.org/index.php/GRUB2).
Attention to encrypted partitions that prevent read the font file (https://lists.ubuntu.com/archives/foundations-bugs/2012-February/064662.html).
I might buy myself a usb key for crash tests.
Updated by Jean-Michel Philippe about 12 years ago
You're right, an USB key is a good solution. But buy one of good quality, the low cost ones usually don't support rewriting an entire USB image several times.
Concerning the way to declare the font with Grub2, there is a dedicated paragraph in ArchLinux wiki:
https://wiki.archlinux.org/index.php/GRUB2#Background_image_and_bitmap_fonts
Seems to be quite easy!