LRO/PDF
Jony
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Hudson
> Sent: Saturday, March 27, 2004 5:05 AM
> To: [EMAIL PROTECTED]
> Subject: RTL -> LTR
>
>
> What is the recommended method for reversing the normal
> direction of text? Fo
> On 2004.03.26, 23:37, Rick McGowan <[EMAIL PROTECTED]> wrote:
> > The Unicode Technical Committee has posted new issues for public
> > review and comment. Details are on the following web page:
>
> I just added the following to the On-Line Report Form:
>
> > U+0140 : LATIN SMALL LETTER L WITH MID
Hi Srivas, Peter Kirk, Peter Constable, List Members
Peter Constable wrote:
> Peter Kirk wrote:
> > Are these dependent on the font, as some have
> > suggested, or are they prescribed by Uniscribe? Do different versions
> of
> > Uniscribe differ in this respect, as I rather think?
>
> At present,
Peter Jacobi wrote,
> Using the Linux version of Abiword, which uses the Pango renderer,
> both the Code 2000 and the MS Latha font display the vowel signs without the
> unwanted dotted circle. NBSP and normal SPACE give identical results.
> For Code 2000 only, the dotted circle or a similiar er
From: "Peter Kirk" <[EMAIL PROTECTED]>
> When I learned French at school we were taught that all French initial
> h's were silent. But I'm sure there is a lot wrong with French as I was
> taught it.
Well it's true that we almost NEVER pronounce any leading h like in English or
German (at least wit
At 05:32 PM 3/26/2004, John Cowan wrote:
Asmus Freytag scripsit:
> Another drawback is the fact that
> too few systems handle any variation selectors gracefully.
Well, at least they should be easy to handle in fonts: add the selectors
to the font as invisible characters, and then create mandatory
[EMAIL PROTECTED] wrote:
So, if the question is how to make an OpenType font *not* display the dotted
circle on Windows with Uniscribe, one idea would be to add a spacing glyph to
U+25CC (DOTTED CIRCLE) in the font. This spacing glyph should be a no-contour
glyph, perhaps with the same advance wi
John,
Look at UTR#20 and at UAX#9 (the 4.01. version is due out shortly).
Taken together they suggest that the non-plain text way is to keep such
text direction overrides out of band (i.e. in markup) and to apply the
bidi algorithm segment by segment in a marked up file.
If you export to plain te
Philippe Verdy scripsit:
> The convention used [...] is to mark the dictionnary entries at the
> letter H with a leading asterisk before all words that have an aspirated
> h (of course this is only a "standard" notation in dictionnaries,
> there's no need to use the asterisk in normal texts).
My
Asmus Freytag scripsit:
> This can be tricky esp,. when the user doesn't know a VS is present
> and the font used to view the data doesn't have an alternate glyph.
Well, surely it'll turn into the black blob, or the reversed question
mark, or whatever. It won't just vanish, except in a font whic
At 05:47 PM 3/27/2004, John Cowan wrote:
Asmus Freytag scripsit:
> This can be tricky esp,. when the user doesn't know a VS is present
> and the font used to view the data doesn't have an alternate glyph.
Well, surely it'll turn into the black blob, or the reversed question
mark, or whatever. It
Asmus Freytag wrote,
> Surly not!
Intentional pun, inadvertent one, or Freudian slip?
> Uninterpreted VS characters should *not* turn into black blobs. If we had
> wanted that to happen, we would have coded different characters.
U+E000 COMBINING BLACK BLOB? Censors would probably love it.
>
> [Original Message]
> From: <[EMAIL PROTECTED]>
>
> Asmus Freytag wrote,
>
> > Uninterpreted VS characters should *not* turn into black blobs. If we
had
> > wanted that to happen, we would have coded different characters.
>
> U+E000 COMBINING BLACK BLOB? Censors would probably love it.
>
> > >
13 matches
Mail list logo
