Re: Fonts installation
Am Mittwoch, den 29.08.2007, 12:06 +0530 schrieb shirish: Hi all, I tried installing a truetype font by using the instructions in https://help.ubuntu.com/community/FontInstallHowto I tried all the ways but dunno if the font got installed or not. I also did a sudo fc-cache -f -v and there it does show the font, here's the output :- This is not an user support list. But open System Preferences Fonts Details Go to fonts folder. Drag and drop your font to this folder. Cheers, Sebastian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Raising i18n awareness among developers
Hello, I'd like to raise some internationalization issues Ubuntu has faced and is facing currently. As a translator and user of Ubuntu in my native language I've sometimes felt that it would be useful to have better awareness of i18n issues among the developers in general. I hope this will help people to remember that when doing any new stuff, keep i18n in mind and tested. I also hope this will help finding people to fix not just the bugs (which are usually not _that_ bad) but the wider issues I describe towards the end of this post. Maybe there'd even be some hired person(s) specifically looking at these kind of issues in the future. Contents of this post: History, Gutsy, Wider Issues == History == As some history, we've, for example, had a bug in Rosetta preventing complete translations at a release time until edgy [1], and several bugs in each released version about non-complete i18n of applications and various other aspects like installer. For example at least [2], [3], [4], [5], [6] in Feisty (Feisty is better than any release before, though!). Also Ubuntu documentation translation updates haven't yet been done for Feisty, they were supposed to be done because there was so little time to translate documentation for Feisty. Hopefully the problems [7] can be resolved quickly (there's reportedly a problem with generating the docs). [1] https://bugs.launchpad.net/rosetta/+bug/102382 [2] https://bugs.launchpad.net/rosetta/+bug/106756 [3] https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/103292 [4] https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/103917 [5] https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/95796 [6] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/45741 [7] https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/123963 == Gutsy == Currently we have some problems with gutsy, besides the fact the installer is not translatable yet at all which is being fixed. Hopefully [8] too, which is also in Feisty. The installer currently doesn't install support for any language besides English [9], plus both on the live CD and in an installed Ubuntu Examples folder isn't translated [10]. The new xdg-user-dirs currently also works suboptimally [11], of which there's going to be further investigation indeed before the release (thanks!), I hope that it will work in an optimal way in the release. I'm currently not seeing any actual applications that couldn't be translated at all, besides problems with Rosetta lagging behind badly and missing a feature to keep restricted manager translated at the moment [12]. I do believe they'll be solved near/after the string freeze and before release this time. For an example about a new Ubuntu program, displayconfig-gtk seems very properly translatable though currently translations have to be sent to the bzr repository until Rosetta catches up. As a whole, gutsy is looking better than feisty again, which is great, but there are big issues still left, read more below. [8] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/103925 [9] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/131294 [10] https://bugs.launchpad.net/ubuntu/+source/example-content/+bug/45489 [11] https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/123435 [12] https://bugs.launchpad.net/rosetta/+bug/130138 == Wider Issues == I don't doubt the automatic language support downloading wouldn't be fixed to some extent soon, but most probably not optimally. That brings me to the bigger problem of the difficulty of having Ubuntu in one's native language: (0. the Win32 part of the live cd doesn't have translations) 1. When starting Ubuntu from the live CD, it starts in English unless the user (let's suppose a newbie) strikes F2 in the boot menu 2. When the desktop shows, even if the person chose non-English language, generally support for any other language is not on the CD (more languages are needed to be dropped in each release), and besides the installer which includes all translations most stuff is in English 3. In the installer, it's not indicated that the person should _really_ have network connection enabled for the language support to be downloaded, plus even with the connection it's currently broken like stated ([[9]) 4. Before or after installation, if the user happens to find Language Selector, and has the default language as one's native language (ie. selected in the boot menu or in the installer if already installed), the selector does not suggest installing support for the Default Language selected if there was no network connection during installation [13] [13] https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/135752 To fix the numbered problems, besides including instructions for 1. and 3. in our ubuntu-fi.org's installation guide [14] that hopefully some Finnish people read before installing, I've done one blueprint [15] to collect ideas and other blueprints. The blueprint was briefly discussed
Re: About Sound System
On Thu, 2007-08-30 at 18:48 +0300, nick nick wrote: Guys i wonder why should simple users of ubuntu know how to setup their sound servers and drivers in order to use at the same time programs that use their sound card?I think the whole sound system after the system installation should be pre-configured in a way that would not require from the user to configure his programs whatever driver/audio server they use/require(might use a kind of emulator or a more clever audio server?), is that possible to implement? (I'm not sure if this post goes here it's just a short complaint) This was a problem when OSS (open sound system) was the only way to get sound in Linux. To get around this KDE came up with ARTS (I forget what it stands for) and GNOME came up with ESD (enlightened sound daemon). Then the kernel got ALSA (advanced Linux sound architecture) which gave solved the OSS issue of only having one sound device, but also featured OSS emulation for programs which need it. These days we have these things running on top of each other (ALSA and ESD for GNOME, ALSA and ARTS for KDE), and mixing desktop environments can run all of them (for instance I use Kopete, KDE's messaging program, in GNOME, which means I'm running ESD and ARTS on top of ALSA). These usually play nice together, and it is only for specific cases like games and sometimes Flash that things can go wrong (usually it is proprietary software like that which doesn't work with the newer systems, although I think Audacity still relies on OSS and stops other programs making sound). To get around this we now have yet another sound server, called PulseAudio, which can emulate ESD if needed. PulseAudio sounds great on paper, but I tried installing it on a Feisty system and it ended up stopping all sounds from everything unless I ran killall pulseaudio, so let's just hope that this does a better job than all of the previous attempts Cheers, Chris Warburton PS: I'm not an expert on this or anything, I've just been around for a while and suffered through all the problems of each system :) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Non-critical bug fixes/new hardware drivers in stable releases?
Hi, I've been lurking/occasionally posting here for a while, and I would like to bring up an issue that has been a real annoyance in my attempted use of Ubuntu (as well as other Linux distributions, notably Debian) this summer. In short, while I feel that Ubuntu has made real progress with regards to desktop Linux - comparing Hoary and Feisty (the last release I had used prior to this summer) is like night and day. More works out of the box, it's FAR easier to get all the popular non-free codecs, and it generally feels like a modern desktop operating system. However, in installing Ubuntu I ran into a whole slew of issues that, while not will make your system explode/lets hackers in/causes data loss bad, are quite annoying nevertheless. Some examples include: 1. Many USB storage devices can't be properly unmounted using the GUI. One must use the console or use non-optimal workarounds (that are distinctly UNSUPPORTED) to fix this. The bug in particular can be found at https://bugs.launchpad.net/ubuntu/+bug/99538 2. My laptop (a MacBook, don't laugh :) ) won't suspend-to-RAM with the default kernel. To be precise, it will suspend, but it will not resume :) This is fixed in newer kernels (such as those in Gutsy) and can be worked around with a kernel recompile in 2.6.20. However, one must either compile a kernel or use apt-pinning with Gutsy sources to use this fix - a decidedly unsupported and nonintuitive fix. 3. Many other examples that I can't think of off the top of my head - though one may see many of these by looking at the Howto configure XYZ wiki pages. Words such as recompile, add this repository, etc etc seem to be a constant occurence here. This is especially apparent when it comes to new hardware that has drivers, albeit ones that weren't ready as of the stable release. What these issues have in common is that, under current policy (which calls for updates for security/data loss type issues ONLY), there is little or no chance of having them fixed in the stable release. While I can see the merit of keeping changes to stable to a minimum, it seems like the existing policy of Ubuntu (and many distributions - I'm not blaming Ubuntu in particular) is leaving many users out in the cold with regards to their issues until the next release. I can see this policy for a server or enterprise desktop (and thus the LTS releases), but not a normal desktop. For desktop users, it ends up making them fix some bugs/hardware support issues themselves using the command line/third-party repositories/building from source - which is something that should be avoided. Has there been any consideration to easing the stable release updates policy to accommodate issues like these? I'm not necessarily advocating that the stable release receive every update under the sun (certainly not feature-only updates), but it seems like allowing more bug fixes/new drivers to enter the stable release would be beneficial to many end users. I think that many users are probably turned off by the recompile, add this unsupported software, hack this code, etc etc (I know this is what always ends up pushing me away from Linux) and this would go a long way towards alleviating this. Any comments? I'm especially wondering what developers think of this issue... Tim -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
