Re: Seeking gucharmap string freeze permission

On Wed, 17 Aug 2005, Danilo Åegan wrote:

> Hi Behdad,
> Last Monday at 23:15, Behdad Esfahbod wrote:
> > What is a ucharmap good for if it doesn't support the latest
> > version of the Unicode standard?
> This version?
> I mean, it's the one that came out on March 31, 2005, or almost 5
> months ago.  If it wasn't that urgent at that time (or during the
> remaining 4 and a half months), is it really urgent now?

Because unfortunately gucharmap is in the unmaintained mode of
operation.  Recently Roozbeh applied a patch to Pango to updated
to 4.1, and I completed 4.1 support in Pango by updating the bidi
tables.  It was just after that when Behnam noticed gucharmap and
submitted a patch.  Noah has only been involved at the
accepted/rejected level recently.

So, is it urgent, probably not.  We can even live with Unicode
3.2, in one way or the other.

> > We are trying to update gucharmap to Unicode 4.1 but that
> > involved some 29 string addition/changes, mostly writing script
> > names of Unicode block names.  They are expected to be either
> > very easy (similar to existing entries) or very hard (those that
> > remain untrsnalted for quite a while anyway) to translate.
> My suggestion would be to leave them untranslated at this time.  If it
> wasn't important till now, I guess we can live with them being
> untranslated for another release.  That way, you get Unicode 4.1
> support, yet no string freeze breakage.

I don't understand.  We've planned to update most of the tables
anyway.  Do you mean we may apply the patch that involves strings
or not?

> Christian Rose may have a different opinion, though.
> (And I'm not sure if this doesn't break the feature freeze either, but
> I'm not going to play a policeman here :)

What kind of feature do you have in mind? ;)

Updating tables is dirty work that maintainers forget most of the
time.  That's why I believe a central Unicode Characters Database
library is in place.

> Cheers,
> Danilo


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]