All Projects

Hi Team,

Thanks a lot for great work of art and development!
There is however a critical bug for Russian l10n: if one chooses Russian from the initial boot menu of Topaz 2.0 stable, the encodings for NTFS become look like this: ru_RU.KOI-8.utf8 and because there is no such encoding set, all those partitions must first after booting in become unmounted (as the distro mounts them automatically which is great, but sadly not in this error case), then the encoding for ALL ntfs partitions in /etc/fstab must be manually changed under root to one of the normal one, like ru_RU.utf8 (I always just deleted that obsolete KOI-8 records), and then become again mounted normally.
This bug also causes an error or a couple of them during the boot-in process, and definitely prevents users from adequate access onto their ntfs partitions, as naturally all Cyrillic chars become unavailable, and mount problems, etc.

Just to mention: when the world does already have UTF, national encodings look as obsolete and as odd as using the sudo scheme while I totally agree with your philosophy of “if you want to become root, simply type “su -”, enter password and become root”.

The bug spoils everything equally out of a live CD or a live USB stick.

Just to notice: KOI-8 as a Russian national localization encoding is almost not used anywhere by now (March 2014). UTF8 has already for pretty long been a recommended and much more effective encoding set to properly map and operate over Cyrillic chars. The great example of simple UTF8 implementation of l10n is in a commercial by now live CD/USB distro of PartedMagic.
Thus a question: is it posssible to get a rebuilt version of the same Topaz 2.0 or much better a newer stable bootable elive system with the described bug fixed?

Thank you!

PLEASE be describable, clear, and direct. Think that we need to understand, found, and solve the bug.

Remember to set the Due in Version box into the next stable version number.

Thank you