Pre-Proposal Zend_Unicode

[André Hoffmann]

Hi,
after we decided that most of the functionality of Zend_Locale_UTF8 will be replaced by iconv functions, I suggest putting some leftovers that are not covered by iconv in a separate class which is not meant to be for internal use, but for the end-user(which doesn't say that it can't be used by internal components).
As Zend_Locale_UTF8 it's not needed by Zend_Locale anymore I suggest putting it out of the 'locale' name space and name it something like Zend_Unicode.
It's supposed to provide Unicode string functionalites using the UCD.
That is case folding, numeric values and maybe also word/sentence breaking.

--
best regards,
André Hoffmann

[Willie Alberty]

On Nov 2, 2006, at 12:04 PM, André Hoffmann wrote:

> after we decided that most of the functionality of Zend_Locale_UTF8  
> will be replaced by iconv functions, I suggest putting some  
> leftovers that are not covered by iconv in a separate class which  
> is not meant to be for internal use, but for the end-user(which  
> doesn't say that it can't be used by internal components).
> As Zend_Locale_UTF8 it's not needed by Zend_Locale anymore I  
> suggest putting it out of the 'locale' name space and name it  
> something like Zend_Unicode.
> It's supposed to provide Unicode string functionalites using the UCD.
> That is case folding, numeric values and maybe also word/sentence  
> breaking.

I love this idea and already have an application for it. Please see:  
http://www.nabble.com/Zend_Locale_UTF8-updated%2C-some-new-ideas- 
tf2447791s16154.html

I would like to work with you on such a class because I have already  
written a fair amount of code as well.

--

Willie Alberty, Owner
Spenlen Media
[hidden email]

http://www.spenlen.com/

[Thomas Weidner]

As the base for UTF8 has changed for possible general purpose and it's not used by I18N anymore, I will clear SVN from Zend_Locale_UTF8.

 

Until the proposal for Zend_Unicode is accepted by Zend we can offer the code for Unicode(UTF8) class through the proposal by an added file (zip/tar).

 

I'm also not sure if Zend_Unicode should be related to I18N.

As the use now seems more general it should be related to Zend_Formats.

 

Any suggestions ?

 

Greetings

Thomas

 

----- Original Message -----

From: [hidden email]

To: [hidden email]

Sent: Thursday, November 02, 2006 9:04 PM

Subject: [fw-i18n] Pre-Proposal Zend_Unicode

Hi,
after we decided that most of the functionality of Zend_Locale_UTF8 will be replaced by iconv functions, I suggest putting some leftovers that are not covered by iconv in a separate class which is not meant to be for internal use, but for the end-user(which doesn't say that it can't be used by internal components).
As Zend_Locale_UTF8 it's not needed by Zend_Locale anymore I suggest putting it out of the 'locale' name space and name it something like Zend_Unicode.
It's supposed to provide Unicode string functionalites using the UCD.
That is case folding, numeric values and maybe also word/sentence breaking.

--
best regards,
André Hoffmann

[Ahmed Shreef-2]

On 11/2/06, Thomas Weidner <[hidden email]> wrote:

 

I'm also not sure if Zend_Unicode should be related to I18N.

As the use now seems more general it should be related to Zend_Formats.

 

Any suggestions ?

I think that the domain of Zend_Formats should be only for formating data without going deeper in how the data is encoded. the encoding of characters is a lower layer IMHO.

and leaving the Unicode related things in I18n is better as Unicode was created to solve this type of problems in the first place.

I can't say that I'm experienced in this things (I'm still a student) , but I hope this is helping :)

thank you,
--
Ahmed Shreef
Web Developer
Egypt

[Thomas Weidner]

Hy,

 

I'm also not sure if Zend_Unicode should be related to I18N.

As the use now seems more general it should be related to Zend_Formats.

 

I think that the domain of Zend_Formats should be only for formating data without going deeper in how the data is encoded. the encoding of characters is a lower layer IMHO.

and leaving the Unicode related things in I18n is better as Unicode was created to solve this type of problems in the first place.

Unicode now is not used for Localization and Internationalization.

 

Unicode itself is a format for character encoding and therefor as you said it yourself its more related to the format group.

 

Character Encoding has nothing to do with Internationalization.

Using UTF8 within a xml document doesnt mean that it's localized.

 

Maybe because it's a more deeper thing it's more related to core but it could also be included in a new group (addons?).

 

Greetings

Thomas