Christopher Fynn wrote:
The Transliteration feature types allows text is one format to be
displayed using another format. An example is taking a hiragana string
and displaying it as katakana. This is an exclusive feature type.
Currently defined selectors for this feature are:
o Hir
srintuar wrote:
Danilo Segan wrote:
The only possible reform that would alleviate this condition would
be to completely unify the latin and cyrillic scripts or to
eliminate one of them. Then cyrillic or latin could simply be a font
setting for users of all languages.
(I dont know if this is even
Danilo Segan wrote:
You have problems to do google searchs in Serbian because a text
can be in two different scripts;
I'm actually more concerned with the display and input problem,
rather than doing Google searches (I mentioned Google only to show
that people care about la
Hi Pablo,
Today at 23:17, Pablo Saratxaga wrote:
> It is indeed a good feature to do so;
> but the *smallest* unit for which language information is usefull
> are *words*, not characters/letters.
Indeed. But how do you achieve that? It's easiest to have characters
hold language information. O
Kaixo!
On Thu, Nov 18, 2004 at 01:50:28PM +0100, Danilo Segan wrote:
> The issue is whether you would care about being able to differentiate
> in your text processor between languages or not.
It is indeed a good feature to do so;
but the *smallest* unit for which language information is usefull
On Thursday 2004.11.18 18:46:46 +0100, David Gómez wrote:
> Hi Keld ;),
>
> > Hmm, I see it differently. All the "fully composed" characters are
> > indeed full characters in their own right,
>
> That depends on the script, i guess. In Spanish, composed characters
> are _not_ characters in their
Hi Chris ;),
> You are not lost at all.
You're right, you're patch works perfectly ;)). Thanks a lot ;)
> The compose table stored in the kernel uses
> 8-bit values, and it's probably not going to be fixed. (How would you
> fix it? Should we keep input characters at 8-bit and change the output
Hi Keld ;),
> Hmm, I see it differently. All the "fully composed" characters are
> indeed full characters in their own right,
That depends on the script, i guess. In Spanish, composed characters
are _not_ characters in their own rigth (maybe is ntilde a composed
character? i think not ;)). But i
On Thu, Nov 18, 2004 at 11:44:09AM -0500, Edward H. Trager wrote:
> On Thursday 2004.11.18 01:44:07 +, Christopher Fynn wrote:
>
> Hmmm, I'll have to read that document again and think about this one.
> One of the problems with Unicode is that it is, in many ways, such a mess.
> Based on first
On Thursday 2004.11.18 01:44:07 +, Christopher Fynn wrote:
> Edward H. Trager wrote:
>
> >Mlterm (http://mlterm.sourceforge.net/) is a multilingual-capable terminal
> >emulator which handles combining characters. Mlterm with a console-based
> >mail reader like mutt works pretty well. However
Hi Henry,
Yesterday at 15:21, Henry Spencer wrote:
> Do you say "a-acute" or "acute-a"?
Imagine asking a German:
Do you say twenty-one or one-and-twenty? :)
Ein-und-zwanzig, natÃrlich. :)
Not arguing here on any side, just pointing out that there're always
exceptions :)
Cheers,
Danilo
--
Hi Antoine,
Yesterday at 13:37, Antoine Leca wrote:
> srintuar wrote:
>> FWIW, I'd assert that "j" in Spanish is not the same thing as
>> "j" in English (and that one is easily proved), apart from them being
>> represented with the same *glyph*.
>
> You picked (certainly involuntarily) a very ins
12 matches
Mail list logo
