On 22.02.2018 05:01, David Starner via Unicode wrote:
On Wed, Feb 21, 2018 at 7:55 AM Jeb Eldridge via Unicode
wrote:
Where can I post suggestions and feedback for Unicode?
Here is as good as any place. There are specific places for a few
specific things, but likely if you do have something
On Wed, Feb 21, 2018 at 7:55 AM Jeb Eldridge via Unicode <
unicode@unicode.org> wrote:
> Where can I post suggestions and feedback for Unicode?
>
Here is as good as any place. There are specific places for a few specific
things, but likely if you do have something that's likely to get changed,
yo
http://www.unicode.org/faq/faq_on_faqs.html#34
The Unicode website has a section for feedback in its menu, but in separate
projects for TUS and for CLDR.
There are also feedbacks requested for every proposed amendment to the
standard, annexes, and data. First search the relevant topic on the
website, then look at the side bar if there's no spec
On 2/21/2018 7:23 AM, Jeb Eldridge via
Unicode wrote:
Where can I post suggestions and feedback
for Unicode?
What kinds of suggestions / what kind of
feedback are
Kent Karlsson wrote:
> Consider English. If I write "", that may well be a spell error.
Or even "Ŋŋŋŋ!", as Michael Everson wrote in WG2 N2306.
-Doug Ewell
Fullerton, California
> > No, with proper reordering (and "normal" display mode), the e-matra at
> > the beginning of the second word would appear to be last glyph of the
> > first "word". Similarly, for the second case, the e-matra glyph would
> > have come to the left of the pa. The fluent reader (ok, not me...)
> --- Kent Karlsson <[EMAIL PROTECTED]> wrote:
> > >
> > > No fallback rendering is coming into picture with your explanation.
> >
> > Yes, there is. A character sequence (say)
> > is very unlikely to have a ligature, specially adapted (and fitting)
> > adjustment points, or similar. The ren
--- Kent Karlsson <[EMAIL PROTECTED]> wrote:
> >
> > No fallback rendering is coming into picture with your explanation.
>
> Yes, there is. A character sequence (say)
> is very unlikely to have a ligature, specially adapted (and fitting)
> adjustment points, or similar. The rendering would i
--- Kent Karlsson <[EMAIL PROTECTED]> wrote:
> >
> > Without that dotted circle appearing, the e-matra would appear to
> > have been properly encoded,
>
> No, with proper reordering (and "normal" display mode), the e-matra at
> the beginning of the second word would appear to be last glyph of
Keyur Shroff wrote:
...
>
> No fallback rendering is coming into picture with your explanation.
Yes, there is. A character sequence (say)
is very unlikely to have a ligature, specially adapted (and fitting)
adjustment points, or similar. The rendering would in that sense
need to use a fallba
--- Kent Karlsson <[EMAIL PROTECTED]> wrote:
>
> > Clearly, since in this case the sign is not
> > preceded by any consonant base, it has to be rendered using one of the
> > mechanisms specified in fallback rendering of non-spacing marks.
>
> If it is preceded by a SPACE (or is first in a string
.
Kent Karlsson wrote,
> > I add that this is a good way of displaying a combining mark that has no
> > base character, i.e. one occurring at the begin of a line or paragraph.
>
> No, those should be displayed *as if* preceded by a SPACE (TUS 3.0 page 121).
So it says. But, the 'space method' c
At 01:20 AM 1/30/2003, Marco Cimarosti wrote:
However, I totally agree with Kent that this funny rendering is *not* a
requirement of the Unicode standard, as Keyur Shroff seems to suggest. It is
just an example of many "several methods [that] are available to deal with"
strange sequences.
Perha
Keyur Shroff wrote:
> > However, I totally agree with Kent that this funny
> rendering is *not* a
> > requirement of the Unicode standard, as Keyur Shroff seems
> to suggest. It
> > is just an example of many "several methods [that] are
> available to deal
> > with" strange sequences.
>
> A seq
> Let me give a proper example this time. Consider a "Vowel Sign E" [U+0947]
> appearing after any non-consonant character. This sign is generally
> attached to the consonants. It has zero advance width with negative left
> side bearing in the font.
Ok.
> Clearly, since in this case the sign is
> > I don't know where you find support for that position in that text.
> > Can you please quote? There are no "invalid base consonants" for
> > any dependent vowel (for Indic scripts; similarly for any
> > other script).
>
> Actually, there is a mention of displaying combining marks on dotted
--- Marco Cimarosti <[EMAIL PROTECTED]> wrote:
>
> I add that this is a good way of displaying a combining mark that has no
> base character, i.e. one occurring at the begin of a line or paragraph.
>
> However, I totally agree with Kent that this funny rendering is *not* a
> requirement of the
Kent Karlsson wrote:
> Keyur Shroff wrote
> [...]
> > In Indic scripts any sign that appear in text not in
> > conjunction with a
> > valid consonant base may be rendered with dotted circle as fallback
> > mechanism (Section 5.14 "Rendering Nonspacing Marks"
> > http://www.unicode.org/uni2book/ch0
To support what Kayur has to say I will add few more
things.
Take for instance a "vowel sigh" (matras as we call here in
India) e.g. say is e (U093F), is combined with a consonant like ka (U0915) in
the sequence it forms ke. (Please see the first image). The repositioning of the
shape ha
--- Marco Cimarosti <[EMAIL PROTECTED]> wrote:
> Keyur Shroff wrote:
> > But sometimes a user may want visual representation of these
> > symbols in two different ways: with dotted circle and
> > without dotted circle.
>
> Why not using a dotted circle character explicity, when you want to see
>
Keyur Shroff wrote
> Kent Karlsson <[EMAIL PROTECTED]> wrote:
> >
> > A space followed by a dependent vowel sign should display just the
> > dependent vowel sign, no dotted circle. Indeed, (except for a "show
> > invisibles" mode, or a "character chart" display mode) no (Indic or
> > other)
> >
Keyur Shroff wrote:
> But sometimes a user may want visual representation of these
> symbols in two different ways: with dotted circle and
> without dotted circle.
Why not using a dotted circle character explicity, when you want to see one?
> Example of
> this could be RAsup on top of dotted cir
--- Kent Karlsson <[EMAIL PROTECTED]> wrote:
>
> A space followed by a dependent vowel sign should display just the
> dependent vowel sign, no dotted circle. Indeed, (except for a "show
> invisibles" mode, or a "character chart" display mode) no (Indic or
> other)
> text that does not contain th
--- Marco Cimarosti <[EMAIL PROTECTED]> wrote:
> Why not representing INV with a double ZWJ? E.g.:
>
> ISCII Unicode
> KA halant INV KA virama ZWJ ZWJ
> RA halant INV RA virama ZWJ ZWJ (i.e., repha)
> INV halant RA ZWJ ZWJ virama RA
> The [new] INV character in Unicode can also be used for displaying dependent
> vowel matras without dotted circle.
A space followed by a dependent vowel sign should display just the
dependent vowel sign, no dotted circle. Indeed, (except for a "show
invisibles" mode, or a "character chart" dis
Keyur Shroff wrote:
> In the FAQ
>http://www.unicode.org/faq/indic.html#16
>
> It is mentioned that following are equivalent
>
> ISCII Unicode
> KA halant INV KA virama ZWJ
> RA halant INV RAsup (i.e., repha)
The last line is really bizarre! I would agree that
> You can always search the big Unihan.txt file on the kJapaneseKun
> and kJapaneseOn fields, which provide whatever information we have
> on pronunciation of the characters in Japanese.
>
> If you are just stuck looking up stuff because it isn't marked up
> for Japanese, try getting Sanseido's
11-digit boy suggested:
> 1. Unicode points are NUMBERS. Numbers can be written in ANY base.
> Knowing decimal values of codepoints is sometimes useful, so please
> print them in the next edition of the Unicode book.
The UTC has already decided not to do that, as it clutters up the
charts. Hex
29 matches
Mail list logo
