gnome terminal displaying utf-8 unicode text
gnome-terminal does not display utf-8 unicode text correctly, atleast the telugu codes 0x0C00-0x0C7F and I believe most indic code tables. I would like to know which source files I should look to for to correct the behavior. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome terminal displaying utf-8 unicode text
On Tue, 14 Jun 2005, Krishna Mohan Gundu wrote: gnome-terminal does not display utf-8 unicode text correctly, atleast the telugu codes 0x0C00-0x0C7F and I believe most indic code tables. What do you mean does not display? I would like to know which source files I should look to for to correct the behavior. I'm a random Joe here, but I do not think rendering complex scripts is in the near future of gnome-terminal (vte to be exact.) --behdad http://behdad.org/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: G2.12 with jhbuild
On Tue, 2005-14-06 at 08:22 +0800, James Henstridge wrote: The problem is that newer pkg-config's pkg.m4 caches PKG_CHECK_MODULES() ... James. Having had quite a few pains myself when trying to build gnome from jhbuild, I wonder if it would be better to have a [EMAIL PROTECTED] for quickly resolving build problems... Cheers, Ryan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Language and Culture Capplet update
Hi Peter, all the Gnome Hackers, I'm CCing d-d-l since this is a discussion about l10n API addition that will affect many developers as well. I've added my comments to bug Peter Nugent opened: http://bugzilla.gnome.org/show_bug.cgi?id=307121 and I'd appreciate if any of the hackers responsible for relevant pieces of code (glib or g-c-c, though I seriously doubt we want this API in g-c-c) can comment on this. I should state that this is kind of functionality that GTP seriously wants to see in Gnome! Peter, it'd also be nice to get a cleaner and simpler overview of the proposed API, and the reasoning behind it (i.e. why are date/time formats locales provide not enough, and how do we expect API users to select each of the formats; next, why is this not possible without introducing new API, i.e. what's the reason for it?). I'm holding my judgement until this is explained. When we resolve that, we should probably discuss the way to store settings (since it'd be hard to make Glib depend on GConf, and introducing pluggable backends sounds like overengineering). Cheers, Danilo Today at 10:58, Peter Nugent wrote: I have filed a bug 307121 with updated code and screenshots for this capplet. I would appreciate any feedback people can provide, especially owners of apps which use locale data. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 2.11/2.12 targeting GTK+ 2.8 (ie cairo based)
Le vendredi 10 juin 2005 à 13:10 -0400, Luis Villa a écrit : Each of the major distributors could (should?) package 2.7.0 I've put .deb packages (i386) of the current pango/gtk CVS for Ubuntu here: deb http://people.ubuntu.com/~seb128/gtk ./ Cheers, Sebastien Bacher ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: G2.12 with jhbuild
On 6/14/05, Ryan McDougall [EMAIL PROTECTED] wrote: On Tue, 2005-14-06 at 08:22 +0800, James Henstridge wrote: The problem is that newer pkg-config's pkg.m4 caches PKG_CHECK_MODULES() ... James. Having had quite a few pains myself when trying to build gnome from jhbuild, I wonder if it would be better to have a [EMAIL PROTECTED] for quickly resolving build problems... You're welcome to use http://mail.gnome.org/mailman/listinfo/gnome-build-status for that. I suppose we could punt anything that isn't a confirmed build breakage there? Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 2.11/2.12 targeting GTK+ 2.8 (ie cairo based)
On 6/14/05, Vincent Untz [EMAIL PROTECTED] wrote: Le mardi 14 juin 2005 à 11:57 +0200, Sebastien Bacher a écrit : Le vendredi 10 juin 2005 à 13:10 -0400, Luis Villa a écrit : Each of the major distributors could (should?) package 2.7.0 I've put .deb packages (i386) of the current pango/gtk CVS for Ubuntu here: deb http://people.ubuntu.com/~seb128/gtk ./ Fantastic! Do you think that asking breezy users to try it on the Ubuntu forums and/or mailing lists is appropriate? Might be worth waiting for http://bugzilla.gnome.org/show_bug.cgi?id=306216 to be fixed before pimping it too widely? Luis (using it now) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Bugzilla: Reducing bugspam and finding patches
There are a few changes in Bugzilla that I want to spam everyone about. One is a patch report, the other changes are in the handling of bug-buddy reports. When you are drowning in bugspam wouldn't it be nice to get an easy overview of your patches? Perhaps an overview of patches that need reviewing in your product(s)? Maybe you'd like to see your submitted patches that haven't been reviewed? Maybe even patches that still have accepted-commit_now? Despair no more. Elijah Newren's patch report coupled with my frontend does everything you want and more. See for yourself and try the FREE evaluation version at: http://bugzilla.gnome.org/reports/patch-status.cgi That report has been linked from the 'Reports for Maintainers' section: http://bugzilla.gnome.org/reports/reports.cgi#maintainers (Above comment was a subtle hint to ensure everyone bookmarks both links) That was the patch report. Now on to the bug-buddy reports. There are some tools to reduce the amount of bugspam you receive. Basically you want to avoid bugspam that is: 1. Not for your product 2. An OpenOffice.org crasher 3. Already fixed (duplicate) These can now be avoided if the bugreport is a crasher reported using bug-buddy. 1. Not for your product This usually occurs with bug-buddy reports. You get a new crasher, but it is for another product. We can now move these bugreports automatically using the filename of the crashed program. When the bug is moved a warning will be added: Bugreport moved from See for example: http://bugzilla.gnome.org/show_bug.cgi?id=307574 (scroll below the stacktrace) If your product receives a lot of misreported bugs, and think they follow a pattern, contact Bugsquad (mailing list or #bugs). This can be the name of a program and the product it should be moved to, but other suggestions/ observations are welcome as well. Note: The bugreports will *not* be moved from every product. For a bugreport to be moved, the original product has to have at least one configured program. This was done on purpose as not to move (example) gtk+ bugreports back to gnome-panel. 2. OpenOffice.org crashers Bugzilla.gnome.org has been rejecting OpenOffice.org crashers since May 19. Since that time we've rejected over 300 of those. 3. Already fixed (duplicate) Some crashers have been fixed a long time ago, but they still receive daily bugreports. These bugreports can now be rejected automatically. For this the first 5 functions of the stacktrace are used, coupled with the GNOME version (to prevent regressions being rejected). If you have such a bug and it still receives a lot of duplicates, please contact Bugsquad with the bug number. Persons interested in doing the work yourself or those afraid of Bugsquad, please see: http://cvs.gnome.org/viewcvs/*checkout*/halloween/bugzilla.gnome.org/program-map.txt (The file to modify + documentation for #1 -- moving of bugreports) and http://cvs.gnome.org/viewcvs/*checkout*/halloween/bugzilla.gnome.org/crashers-map.txt (The file to modify + documentation for #3 -- rejecting fixed crashers) If above isn't clear, please contact me. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: ANNOUNCE: Deskbar Applet 0.3
On Tue, 2005-06-14 at 11:13 +1000, Nigel Tao wrote: ABOUT: This is a small Gnome applet that is like Google's Deskbar, but it 1) runs on Linux, and 2) can use search engines other than Google. This is pretty nifty. --d -- Davyd Madeley http://www.davyd.id.au/ PGP Fingerprint http://www.davyd.id.au/pgp/ 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome terminal displaying utf-8 unicode text
Hi, I would like to know which source files I should look to for to correct the behavior. You actually want to be looking at vte, the terminal rendering widget for gnome-terminal. There are multiple levels to getting indic text to work well. 1) getting cat text_file.txt to work 2) getting ls to align columns right 3) getting line editing to work (e.g., shells) 4) getting programs like vi to work 1 and 2 are going to be a lot easier than 4. I'm not really sure how hard 3 would be. --Ray Strode ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
