Re: Small feature request for future EU versions
Patrick Barnes wrote:
[snip]
> > I like your suggestion, but I just do not see the solution how to make
> > this way the stable templet for *any* alphabet now.
>
> Works for any alphabet and code page, and is faster, because it
> doesn't have to keep slicing the alphabet sequences.
Ok, I see "...for any alphabet...".
But my_case_LA() makes just single slicing on the alphabet_la sequence,
and yours_case_LA() has 3 supporting sequences.
Can you rename yous_case_LA() as case_La() or such? Just for short, to not
confuse?
> > Some alphabets have no case at all, some alphabets have different
> > numbers of upper and lower letters.
> > For example, computer Russian has 3 extra letters in upper case, which
> > are absent in Russian canonical grammar.
>
> The limitation of the above function is that LA_up and LA_lo must be
> the same length... what do you mean by 3 extra letters? What if you
> try to convert them to lower case? If it should just leave them as
> upper case, that's fine - just leave them out of the function.
Ok, I see "The limitation..." .
What about "...for any alphabet..."? 
Well, there are 3 lower-case letters in Russian, which can not stand
on the first place in a word.
There are no such the words in Russian at all.
So, you can not find them in any normal Russian text.
But some more or less artificial computer texts, like "ruSSIan" or "heLLo"
can include those additional upper-case letters.
And I can just include those letters into the alphabet_ru sequence
or exclude them and get the functions for canonical and for artificial
Russian languages.
Ok, Derek submitted his new library to Rob for these things.
I think, there is enough such a stuff in the RDS archives
now to not force Rob to learn our own crazy mumbos_jumbos.
Regards,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|
