Re: [gnome-love] Working with Bugzilla

If I create a bug report it is automatically added to "my bugs and patches" but if I see a bug report, and comment it or not, how do I add it to this list? On Mon, Aug 11, 2008 at 2:52 PM, Andre Klapper <[EMAIL PROTECTED]> wrote: > Am Montag, den 11.08.2008, 14:47 +0100 schrieb adrian.dmc: > > Hi

Re: GLib String support

(Duo to a mistake I'm re-sending this message...) >struct _GString >{ > gchar *str; > gsize len; > gsize allocated_len; > gboolean tainted : 1; >}; > > Let's add the important g_utf8_ functions to g_string, and let them > operate without

Re: GLib String support

Hi... I included the ASCII only version to remove the overhead when dealing with lowercasing, uppercasing, decimal or hexadecimal digits and things like that from applications that really don't need to bring the complexity of Unicode to them. As an example GTK signal strings could only use the ASC

GLib String support

Hi... Following my previous e-mail I'll present were my ideas for changing the support for strings in GLIb. When I look at the string functions in Glib there is a lot of inconsistency: error checking, what character set is supported and function naming; so I'm proposing to change, at least, the f

GLib String support

Hi... My first objective here was to redesign the Unicode property tables but I realized that it is the wrong starting point to start developing so as the title suggest I propose myself to optimize the basic string support of GLib (gstring, gstrfuncs and others) I already started optimizing the gu

Patches to gutf8.c

As no one replied/commented will post the patch (updated) in bugzilla. In the functions provided in *gutf8.c* there is some "instability" because some characters are accepted in certain functions and in others don't, this is because of the limitation to 0..10h that The Unicode Standard imposes

Patches to gutf8.c

Patch 1: changed the macro UTF8_COMPUTE definition to a more fast (made some tests) algorithm. Patch 2: changed the function g_utf8_find_next_char because if the next char is pointed by end it returns NULL. If I should proceed in a different way please inform. Keep up the good work... Best regard

Redesign of Unicode character tables (GLib)

Hi... I'm here to say that I created a blog where I'll try to document everything that I learn while analyzing The Unicode Standard thus making easy for other developers to quickly get in touch with Unicode. For what I realized, I'm working on a project that

Re: New subscriber: redesign of Unicode character tables (GLib)

>> Did you drop the mailing list from CC intentionally? Gmail did it... corrected... >> Sure, I'm willing to help you learn. It's a project I've wanted to do >> myself, but had not got the time for. I'll start writing my ideas down >> and we'll go from there. OK... I'm know analyzing the Stand

New subscriber: redesign of Unicode character tables (GLib)

Hi, I'm new here... My objective, for now, its to rework the Unicode support of GLib by redesigning its character tables, specially its size. I'll appreciate some guidelines and suggestion ("Give up!!" included). I'm currently reading/analyzing the Unicode Standard 5.1 and the GLib support for Un