Okay, Doug.
Type this inside the yellow text box in the following page:
kaaryyaalavala yanþra pañkþi
http://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would produce what
the text box shows.
On Mon, Mar 17, 2014 at 7:56 PM, Doug Ewell
MSKLC and KeyMan are fairly crude ways of creating input methods
For what you want to - you probably need a memory resident program
that traps the Latin input from the keyboard, processes the
(transliterated) input strings converting them into unicode Sinhala
strings, and then injects these back
Chris,
Keyman is capable of doing that and a lot more, but few keyboard layout
developers use it to its full potential.
As an example, I was asked by Harari teachers here in Melbourne to develop
a set of three keyboard layouts for them and their students.
The three keyboards were for three
Le 18/03/14 07:01, Naena Guru a écrit :
Okay, Doug.
Type this inside the yellow text box in the following page:
kaaryyaalavala yanþra pañkþi
http://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would produce
what the text box shows.
OK. I'd first
Hi Andrew
It may be possible with Keyman. I once even wrote a set of MS Word
macros that did the same thing (let users type in Romanized Tibetan
and output Tibetan characters) - however it stopped working when
Microsoft switched from Word Basic to VBA. :-(
At least Keyman hides all the messy
On 18/03/2014, Naena Guru naenag...@gmail.com wrote:
Okay, Doug.
Type this inside the yellow text box in the following page:
kaaryyaalavala yanþra pañkþi
http://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would produce what
the text box shows.
Le 18/03/14 14:35, Jean-François Colson a écrit :
Le 18/03/14 07:01, Naena Guru a écrit :
Okay, Doug.
Type this inside the yellow text box in the following page:
kaaryyaalavala yanþra pañkþi
http://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would
Jean-François Colson jf at colson dot eu wrote:
Type this inside the yellow text box in the following page:
kaaryyaalavala yanþra pañkþi
http://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would produce
what the text box shows.
Could an aware
On Mar 17, 2014, at 11:01 PM, Naena Guru wrote:Type this inside the yellow text box in the following page:kaaryyaalavala yanþra pañkþihttp://www.lovatasinhala.com/puvaruva.php
Please tell me what sequence of Unicode Sinhala codes would produce what the text box shows.Using the Sinhala Qwerty
On Mar 18, 2014, at 12:10 PM, Jean-François Colson wrote:
Using the Sinhala Qwerty layout in Mac OS X with the Apple
Sinhala fonts, I typed
karYYalvl ynhR p;kni
Shouldn’t it be p;khi?
Yes, sorry.karYYalvl ynhR
Tom, with typo spotted and corrected by Jean-François, seems to have
found it:
කාර්ය්යාලවල යනහ්ර
පඩකහි
The sequence of code points would thus be:
0D9A 0DCF 0DBB 0DCA 200D 0DBA 0DCA 200D 0DBA 0DCF 0DBD 0DC0 0DBD 0020
0DBA 0DB1 0DC4 0DCA 200D 0DBB 0020 0DB4 0DA9 0D9A 0DC4 0DD2
Naena, is this
I suspect it was a fishing expedition to illustrate how awkward it is to
type on Unicode keyboard layouts versus his system.
Ie still no clear separation of input and encoding in his responses.
On 19/03/2014 6:39 AM, Doug Ewell d...@ewellic.org wrote:
Tom, with typo spotted and corrected by
I know this is adding fuel to the fire but I’m sure that I am not the only one
to note that the way the text is rendered in Tom’s graphic differs from the way
the text is rendered with Iskoola Pota font in Win 7 and Nirmala UI font in Win
8.1. I have not analysed the difference, nor can I
On Mar 18, 2014, at 1:48 PM, Marc Durdin wrote:
Can anyone who is more knowledgeable in Unicode Sinhala tell me which is the
correct rendering? See graphic below.
image002.png
The OS X version is the most correct according my limited knowledge of the
script. I think the Apple font
The attached image (also at
http://ewellic.org/images/sinhala-babelpad.jpg) shows how I see Tom's
corrected string on Windows 7 running BabelPad, in both Iskoola Pota and
Nirmala UI.
Different rendering based on different operating systems, versions, and
applications is unfortunate, but no more
Le 18/03/14 20:37, Doug Ewell a écrit :
Tom, with typo spotted and corrected by Jean-François, seems to have
found it:
කාර්ය්යාලවල යනහ්ර
පඩකහි
The sequence of code points would thus be:
0D9A 0DCF 0DBB 0DCA 200D 0DBA 0DCA 200D 0DBA 0DCF 0DBD 0DC0 0DBD 0020
0DBA 0DB1 0DC4 0DCA 200D 0DBB 0020
I've done some more analysis now that I've arrived at my office (and if I'd
read Doug's email earlier, would have been able to see this too). The email I
received, on my notebook running Outlook 2010, has had U+200D stripped out from
that Sinhala text - hence the rendering difference. Now it
Jean-François Colson jf at colson dot eu wrote:
It seems there’s still a big difference in the second syllable.
Naena's original text kaaryyaalavala seems to imply the second
syllable begins with r followed by ya. Is the r supposed to form a
conjunct with the second ya, as his font shows,
On Mar 18, 2014, at 2:28 PM, Jean-François Colson wrote:The sequence of code points would thus be:0D9A 0DCF 0DBB 0DCA 200D 0DBA 0DCA 200D 0DBA 0DCF 0DBD 0DC0 0DBD 00200DBA 0DB1 0DC4 0DCA 200D 0DBB 0020 0DB4 0DA9 0D9A 0DC4 0DD2Naena, is this what you were looking for?It seems there’s still a big
On 3/18/2014 1:57 PM, Tom Gewecke wrote:
On Mar 18, 2014, at 1:48 PM, Marc Durdin wrote:
Can anyone who is more knowledgeable in Unicode Sinhala tell me which
is the correct rendering? See graphic below.
image002.png
The OS X version is the most correct according my limited knowledge of
PS A good source for info on the Sinhala codes, etc is
https://www.microsoft.com/typography/OpenTypeDev/sinhala/intro.htm___
Unicode mailing list
Unicode@unicode.org
http://unicode.org/mailman/listinfo/unicode
And I understand the issue now. My notebook did not have any “complex script”
languages installed as “Editing Languages” in MS Office Language Preferences.
Thus, it stripped out U+200D when presenting the Sinhala text. My office
computer had Arabic installed as an “Editing Language,” and so
On Mar 18, 2014, at 12:52 PM, Andrew Cunningham wrote:
I suspect it was a fishing expedition to illustrate how awkward it is to type
on Unicode keyboard layouts versus his system.
Interesting question perhaps. Is it more awkward to type 14 strokes as k a a r
y y a a l a v a l a or to
Different individuals, groups and communities can bring their own
expectations to input layout designs.
Design is a balance between capabilities and limitations of the input
framework versus the expectations of the user community around how they
language should work.
I work with multiple
On 16 Mar 2014, at 23:47, Doug Ewell d...@ewellic.org wrote:
Jean-François Colson jf at colson dot eu wrote:
The idea here was “that characters not on an ordinary QWERTY keyboard could
be entered _using_an_ordinary_QWERTY_keyboard._” Are there any dead keys on
an _ordinary_ (i.e. not one
Michael Everson everson at evertype dot com wrote:
The idea here was that characters not on an ordinary QWERTY keyboard
could be entered _using_an_ordinary_QWERTY_keyboard._ Are there any
dead keys on an _ordinary_ (i.e. not one using an
international(ized) driver) QWERTY keyboard?
Not on the
Naena Guru naenaguru at gmail dot com wrote:
Making a keyboard [layout] is not hard. You can either edit an
existing one or make one from scratch. I made the latest Romanized
Singhala one from scratch. The earlier one was an edit of US-
International.
I've made a couple dozen of them myself,
Making a keyboard is not hard. You can either edit an existing one or make
one from scratch. I made the latest Romanized Singhala one from scratch.
The earlier one was an edit of US-International.
When you type a key on the physical keyboard, you generate what is called a
scan-code of that key so
I disagree. Making a basic keyboard layout is not hard, just like making a
font without OpenType support is not that hard. Making a keyboard layout that
doesn’t force users to learn the nuances of the encoding of a script is more of
a challenge, and making a high quality keyboard layout that
In the modern PC world, the physical keyboard generates scan codes, and these
are not tied to what is printed on the key cap. Dead keys and modifiers are
implemented in software. But key repeat is implemented in hardware.
-Original Message-
From: Unicode
Marc,
Yes, making keyboard layouts is not difficult.
I believed that language tools are selected for each language manually when
input. I did not know that there is an automatic switching of language
tools say when you switch to French keyboard from English. That shouldn't
be difficult to make
Doug,
Making keyboard layouts for Unicode Singhala is hard not because of fault
of Unicode. It is the complexity of letter assembly. I have use the
Wijesekara keyboard on a 24in Olympia Singhala keyboard in 1970s. It is
radically different from US-English.
I tried to make a phonetic one to kind
On 18/03/2014 11:23 AM, Naena Guru naenag...@gmail.com wrote:
I tried to make a phonetic one to kind of relate to the English keys.
Still, you need to have many shifted keys to get common letters.
No you don't, you just need to understand the possibilities of what your
input framework is
Naena Guru wrote:
In the case of romanized Singhala, any processing that English
accepts, it accepts too. For RS, you select a font to display it in
the native script because if it is mixed with English, both are using
the same character space, just as when English and French are mixed.
But
Jean-François Colson jf at colson dot eu wrote:
The idea here was “that characters not on an ordinary QWERTY keyboard
could be entered _using_an_ordinary_QWERTY_keyboard._” Are there any
dead keys on an _ordinary_ (i.e. not one using an international(ized)
driver) QWERTY keyboard?
Not on the
35 matches
Mail list logo
