Re: Unicode in C

imho: hspell does hebrew spelling well. we have iconv, glib, qt ... for doing encoding conversions well. http://en.wikipedia.org/wiki/Unix_philosophy#McIlroy:_A_Quarter_Century_of_Unix on the other side, it will be very nice to have a utf-8 interface to hspell :-)

Re: Unicode in C

Nadav Har'El wrote on Tue, Mar 13, 2012 at 22:16:23 +0200: > On Tue, Mar 13, 2012, Elazar Leibovich wrote about "Re: Unicode in C": > > Something very important, one need to consider is Unicode normalization. > > That is, how to strip out the Niqud, and to substitute, say KAF WITH DAGESH > > (U+FB3

Re: Unicode in C

On Tue, Mar 13, 2012 at 10:16 PM, Nadav Har'El wrote: > On Tue, Mar 13, 2012, Elazar Leibovich wrote about "Re: Unicode in C": > > Something very important, one need to consider is Unicode normalization. > > That is, how to strip out the Niqud, and to substitute, say KAF WITH > DAGESH > > (U+FB3B)

Re: Unicode in C

On Tue, Mar 13, 2012, Elazar Leibovich wrote about "Re: Unicode in C": > Something very important, one need to consider is Unicode normalization. > That is, how to strip out the Niqud, and to substitute, say KAF WITH DAGESH > (U+FB3B) with just a KAF (U+05DB) etc. Is this really important? Does an

Re: Unicode in C

Something very important, one need to consider is Unicode normalization. That is, how to strip out the Niqud, and to substitute, say KAF WITH DAGESH (U+FB3B) with just a KAF (U+05DB) etc. I guess that you're doing that already to some degree in hspell, so (in case you're translating to ISO-8859-8)

Re: Unicode in C

On Tue, Mar 13, 2012 at 5:22 PM, Nadav Har'El wrote: > > Qt appears to use internally UTF-16. What major free software C library > actually prefer UTF-8? > Are you talking about the internal representation, or the external interface? The internal representation is in many cases UTF-16. Indeed, e

Re: Unicode in C

On Tue, Mar 13, 2012, Dan Kenigsberg wrote about "Re: Unicode in C": > In my opinion, it is nice to fit to modern standards of your major target > environment (read: utf8), but not necessary to cater to all encodings. It appears that the consensus on this list is that UTF-8 is indeed "the right wa

Re: Unicode in C

On Mon, Mar 12, 2012 at 03:05:56PM +0200, Nadav Har'El wrote: > Hi, I have a question that I was sort of sad that I couldn't readily > find the answer to... > > Let's say I want to create a C API (a C library), with functions which > take strings as arguments. What am I supposed to use if I want t

Re: I need help with a questioner

2012/3/11 Amichai Rotman I'd like to put a bunch of questions, in the form of multiple choices, and > have a kind of a street poll (e.g.: at the mall). > Android tablet with 3G (or WiFi tethering from your phone) + Google Forms. -- Arie ___ Linux-il m

Re: Unicode in C

On Tue, Mar 13, 2012 at 1:19 PM, Meir Kriheli wrote: > > Nitpick: It's actually ucs2/ucs4 (which preceded the above but are > compatible). > Double nitpick, UTF-16 and UCS-2 are identical representation, and it's better to always use the name UTF-16 as the FAQ says

Re: Unicode in C

Hi, 2012/3/13 Elazar Leibovich > 2012/3/13 kobi zamir > >> >> >>> So I guess that you're also in the UTF-8 camp. >>> >> >> yes, but my opinion about utf-8 is just my opinion. i like python and >> python defaults to utf-8. >> > > Python's internal representation is not UTF-8, but UTF-16, or UTF-

Re: Unicode in C

2012/3/13 kobi zamir > > >> So I guess that you're also in the UTF-8 camp. >> > > yes, but my opinion about utf-8 is just my opinion. i like python and > python defaults to utf-8. > Python's internal representation is not UTF-8, but UTF-16, or UTF-32, depends on build parameters. Thus python doe

Re: Unicode in C

I don't think that input/output matters so much, In something like hspell I/O should be modular so later on encoding can be added. After all it already has function to translate to/from internal representation. I believe that iso-8859-8 and utf8 should be good enough for starts. Ely 2012/3/13 kob

Re: Unicode in C

> > So I guess that you're also in the UTF-8 camp. > yes, but my opinion about utf-8 is just my opinion. i like python and python defaults to utf-8. gtk likes unicode and utf-8: http://www.gtk.org/api/2.6/glib/glib-Unicode-Manipulation.html qt likes more options: http://qt-project.org/doc/qt-4.8/

Re: Unicode in C

On Tue, Mar 13, 2012, kobi zamir wrote about "Re: Unicode in C": > imho because hspell only use hebrew, it can internally continue to use > hebrew only charset without nikud iso-8859-8 (or with nikud win-1255). I agree, and this has been my feeling all along. By using iso-8859-8 internally (and fo

Re: Unicode in C

On Mon, Mar 12, 2012, Omer Zak wrote about "Re: Unicode in C": > It depends upon your tradeoffs. >... > 2. Otherwise, specify two such APIs - one is UTF-8 based, one is fixed > size wide character based. Create two binary variants of the libhspell >... This is why I asked this question in the fir