Ne, ze by Suse nemelo problemy, ale zrovna cairo?
$ zypper se cairo * Načítají se nainstalované balíky [100%] S | Repozitář | Typ | Jméno | Verze | Arch --+-------------------------------------------------------------------+---------+--------------------+-----------+------- i | openSUSE-10.3-OSS-KDE 10.3 | package | cairo | 1.4.10-25 | x86_64 | http://download.opensuse.org/repositories/openSUSE:10.3/standard/ | package | cairo | 1.4.10-25 | i586 i | http://download.opensuse.org/repositories/openSUSE:10.3/standard/ | package | cairo | 1.4.10-25 | x86_64 i | openSUSE-10.3-OSS-KDE 10.3 | package | cairo-32bit | 1.4.10-25 | x86_64 i | http://download.opensuse.org/repositories/openSUSE:10.3/standard/ | package | cairo-32bit | 1.4.10-25 | x86_64 | http://download.opensuse.org/repositories/openSUSE:10.3/standard/ | package | cairo-devel | 1.4.10-25 | i586 ....
Red Hat Linux 8.0 (September 2002) was the first distribution to take the leap of switching to UTF-8 as the default encoding for most locales. The only exceptions were Chinese/Japanese/Korean locales, for which there were at the time still too many specialized tools available that did not yet support UTF-8. This first mass deployment of UTF-8 under Linux caused most remaining issues to be ironed out rather quickly during 2003. SuSE Linux then switched its default locales to UTF-8 as well, as of version 9.1 (May 2004). It was followed by Ubuntu Linux, the first Debian-derivative that switched to UTF-8 as the system-wide default encoding. With the migration of the three most popular Linux distributions, UTF-8 related bugs have now been fixed in practically all well-maintained Linux tools. Other distributions can be expected to follow soon.UTF-8 and Unicode FAQ
rpm -Uvh http://rpm.livna.org/livna-release-8.rpm
Musim priznat, ze me popisovane zmeny prijemne prekvapily. Moje pocity z pouzivani Fedory 7 jsou totiz dost smisene. Osobne mi vadi predevsim: