Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

> >>Yes, yes, I think this is an idea which could fly. >> >>--Ken >> > >Good. It is a solution which could be very useful for people writing >programs in Java, Pascal and C and so on which programs take in plain text >files and process them for such purposes as producing a desktop publishing >pa

Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

William Overington wrote, > > No, it is a story about an artist who wanted to paint a picture of a horse > and a picture of a dog and, since he knew that the horse and the dog were > great friends and liked to be together and also that he only had one canvas > upon which to paint, the artist pa

Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

William, So let me see if I understand this correctly. Let's take 2 perfectly good standards, Unicode and HTML, and make some very minor tweaks to them, such as changing the meaning of U+FFFC and a special format for filenames in the beginning of the file and a new extension, so we have somethin

Re: Furigana

On 08/14/2002 12:45:22 AM Kenneth Whistler wrote: >But even at the time, as the record of the deliberations would >show, if we had a more perfect record, the proponents were clear >that the "interlinear annotation characters" were to solve an >internal anchor point representation problem. I rec

Re: Furigana

On 08/14/2002 05:53:58 AM "James Kass" wrote: >Once a meaning like >"INTERLINEAR ANNOTATION ANCHOR" has been assigned to >a code point, any application which chooses to use that code >point for any other purpose would be at fault. Since it's for internal use only, nobody would ever know. Unicode

Re: Furigana

On 08/14/2002 04:17:29 AM "James Kass" wrote: >Can't apps needing internal processing code points which >are only going to be deleted before export simply use the PUA? NO! E.g. if your word processor used E000 to indicate an anchor point for a table, and I use E000 for capital U-bar, what's goi

Re: Tildes on vowels

On 08/13/2002 10:08:00 AM "William Overington" wrote: I've been ignoring the list for a few days, but come back to find that not much has changed. >>2) Superscript, subscript, combining above, and other forms of >>identifying placement of characters, are better left to markup or other >>render

Re: Double Macrons on gh (was Re: Tildes on Vowels)

On 08/14/2002 02:36:37 PM "William Overington" wrote: >> U+0360 COMBINING DOUBLE TILDE > >> U+035D COMBINING DOUBLE BREVE >> U+035E COMBINING DOUBLE MACRON >> U+035F COMBINING DOUBLE LOW LINE > >I also note U+0361 COMBINING DOUBLE INVERTED BREVE and U+0362 COMBINING >DOUBLE RIGHTWARDS ARROW BELOW

RE: Furigana

On 08/14/2002 10:52:32 AM Michael Everson wrote: >I'm saying I WANT to use these characters. They solve an apparent >need of mine They only *appear* to you to solve that need, but in fact do not offer a good solution. Markup is recommended for your need. - Peter ---

Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

On 08/14/2002 02:04:50 PM "William Overington" wrote: >As this concerns the U+FFFC character and the Unicode Technical Committee is >due to meet next week, I think it might be helpful if this idea is discussed >before the meeting as a straightforward idea like this might mean that the >possibi

Re: Double Macrons on gh (was Re: Tildes on Vowels)

On 08/14/2002 04:34:27 PM "Doug Ewell" wrote: >Broad ranges of Planes 0 and 1 have been tentatively blocked out on the >Roadmap for RTL scripts. Oh? I was somewhat sharply rebuked a few years for suggesting that such a thing be done. References to relevant documentation, please? - Peter --

Re: RE: Furigana

On 08/14/2002 01:16:29 AM starner wrote: >That seems to be basically what William Overington is proposing, >except these characters only handle furigana, instead all markup. Not quite. WO has proposed characters to be used in interchange. These are only intended for internal use by programmers.

Re: Double Macrons on gh (was Re: Tildes on Vowels)

At 09:38 +0100 2002-08-16, [EMAIL PROTECTED] wrote: >On 08/14/2002 04:34:27 PM "Doug Ewell" wrote: > >>Broad ranges of Planes 0 and 1 have been tentatively blocked out on the >>Roadmap for RTL scripts. > >Oh? I was somewhat sharply rebuked a few years for suggesting that such a >thing be done. Ref

Re: Gutenberg's ligatures (spins off from Re: Tildes on vowels)

Michael Everson wrote, > >Appropriate font technology for Latin ligature display exists, > >but it isn't enabled yet in Microsoft's Uniscribe.* > > That doesn't mean that this particular cataloguing of ligatures in > the PUA is a good idea. > > >The Golden Ligatures Collection simply offers f

Re: New version of TR29:

Mark Davis wrote: > There is a new version of Unicode Technical Report #29: Text Boundaries on > , covering grapheme-cluster, word and > sentence boundaries. There are significant modifications to this version; > for a summary, see

Re: Furigana

[EMAIL PROTECTED] wrote: > > On 08/14/2002 12:45:22 AM Kenneth Whistler wrote: > > >But even at the time, as the record of the deliberations would > >show, if we had a more perfect record, the proponents were clear > >that the "interlinear annotation characters" were to solve an > >internal an

Re: The existing rules for U+FFF9 through to U+FFFC. (spins from Re: Furigana)

Kenneth Whistler replied to my posting as follows. >> An interesting point for consideration is as to whether the following >> sequence is permitted in interchanged documents. >> >> U+FFF9 U+FFFC U+FFFA Temperature variation with time. U+FFFB >> >> That is, the annotated text is an object replace

Silly proposals

Hi list, Couldn't the Unicode consortium do something about the silly proposals discussed here? Or is it that you enjoy discussing silly proposals? If so, then fine. But I was under the strange assumption that you had better things to do with your time. *shrug*. I'm thinking most of these si

Re: Discrepancy between Names List & Code Charts?

John Hudson scripsit: > The newish Gagauz Turkish Latin-script orthography derives from both > Turkish and Romanian models. This has led to a peculiar hybrid, in which > the cedilla is used for the s and the commaaccent is used for the t. ME's remarks in _The Alphabets of Europe_ seem downri

Re: Furigana

Tex Texin scripsit: > At the time (in the discussion), I don't think we had many examples of > what the uses would be, and it wan't clear that many were needed, since > the functionality could be arrived at with higher level protocols. One application that has always seemed obvious to me is regu

RE: OCR characters

I believe, Eric is talking about the characters on the attached page 8 of the OCR standard. Regards Arnold > -Original Message- > From: Eric Muller [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 7:44 PM > To: [EMAIL PROTECTED] > Subject: OCR characters > > > In our OCR fo

Re: Discrepancy between Names List & Code Charts?

On Fri, 16 Aug 2002, John Cowan wrote: > John Hudson scripsit: > > > The newish Gagauz Turkish Latin-script orthography derives from both > > Turkish and Romanian models. This has led to a peculiar hybrid, in which > > the cedilla is used for the s and the commaaccent is used for the t. > >

some cedillas

The Times Atlas of the World uses t-cedilla, d-cedilla, and h-cedilla in transcriptions of Yemen placenames. -- Michael Everson *** Everson Typography *** http://www.evertype.com

Re: OCR characters

Eric Muller had written: > In our OCR fonts, we have two glyphs named "erase" [...] > and "grouperase" [...] I suspect those are mandated by these > standards. On the other hand, and I can't find traces of those in > Unicode, Arnold F. Winkler wrote: > I believe, Eric is talking about the c

Re: some cedillas

Michael Everson scripsit: > The Times Atlas of the World uses t-cedilla, d-cedilla, and h-cedilla > in transcriptions of Yemen placenames. But is it correct? The National Geographic map on my wall uses s-cedilla in Romanian place names, and that's definitely wrong. -- Knowledge studies other

Re: some cedillas

At 10:58 -0400 2002-08-16, John Cowan wrote: >Michael Everson scripsit: > >> The Times Atlas of the World uses t-cedilla, d-cedilla, and h-cedilla >> in transcriptions of Yemen placenames. > >But is it correct? The National Geographic map on my wall uses s-cedilla >in Romanian place names, and

Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

James Kass wrote as follows. >William Overington wrote, > >> >> No, it is a story about an artist who wanted to paint a picture of a horse >> and a picture of a dog and, since he knew that the horse and the dog were >> great friends and liked to be together and also that he only had one canvas >>

Re: An idea for keeping U+FFFC usable. (spins off from Re: Furigana)

Tex Texin wrote as follows. >William, > >So let me see if I understand this correctly. > >Let's take 2 perfectly good standards, Unicode and HTML, Yes. and make some >very minor tweaks to them, No. such as changing the meaning of U+FFFC and a >special format for filenames in the beginning of

Re: Double Macrons on gh (was Re: Tildes on Vowels)

wrote: >> Broad ranges of Planes 0 and 1 have been tentatively blocked out on >> the Roadmap for RTL scripts. > > Oh? I was somewhat sharply rebuked a few years for suggesting that > such a thing be done. References to relevant documentation, please? It looks like the dog ate my homework. The

Re: Furigana

John, Why would you want them to be for internal-use only? When you exchange regular expressions wouldn't you want operators such as "any character" to be passed as well, and standardized so that there is agreement on the meaning of the expression? It is also not clear to me that it is desirable

Re: Mac OS X Keyboard Layouts (was Re: new version of Keyman)

Arsa Deborah Goldsmith <[EMAIL PROTECTED]>: >There is lots of good news about keyboards in Mac OS X 10.2, none of Thank you for that rapid, if intriguing response, Deborah. >which I'm allowed to discuss until August 24, unfortunately. If you >have signed an Apple non-disclosure agreement, write

Re: some cedillas

At 06:57 AM 16-08-02, Michael Everson wrote: >The Times Atlas of the World uses t-cedilla, d-cedilla, and h-cedilla in >transcriptions of Yemen placenames. I would expect those cedillas to be dots below the letters for standard Arabic transliteration. John Hudson Tiro Typeworks www.

Re: Mac OS X Keyboard Layouts (was Re: new version of Keyman)

Arsa Deborah Goldsmith <[EMAIL PROTECTED]>: >There is lots of good news about keyboards in Mac OS X 10.2, none of Thank you for that rapid, if intriguing response, Deborah. >which I'm allowed to discuss until August 24, unfortunately. If you >have signed an Apple non-disclosure agreement, write

Re: Furigana

Tex Texin scripsit: > Why would you want them to be for internal-use only? When you exchange > regular expressions wouldn't you want operators such as "any character" > to be passed as well, and standardized so that there is agreement on the > meaning of the expression? Regular expressions are u

22nd Unicode Conference, Sep 2002, San Jose, CA -- Just 3 weeks to go!

*** Register now! > Just 3 weeks to go > Register now! > Just 3 weeks to go *** Twenty-second International Unicode Conference (IUC22) Unic

Re: Furigana

John Cowan wrote: > > Tex Texin scripsit: > > > Why would you want them to be for internal-use only? When you exchange > > regular expressions wouldn't you want operators such as "any character" > > to be passed as well, and standardized so that there is agreement on the > > meaning of the exp

Revised proposal for "Missing character" glyph

Proposed unknown and missing character representation. This would be an alternate to method currently described in 5.3. The missing or unknown character would be represented as a series of vertical hex digit pairs for each byte of the character. BMP characters would be represented with 4 hex di

RE: OCR characters

Otto, I am looking at ISO 1073/II-1976: The two erase characters are the only members of set #5, reference numbers are 120 and 121. The "Remarks" column is empty. 6.4 says : Application advise is given in the column "Remarks", where it is indicated, inter alia, which characters are included fo

RE: OCR characters

Folks, that is my VERY LAST post on this VERY OLD subject: In the L2 document register I found L2/98-397 http://www.unicode.org/L2/L2/98396.pdf which is a proposal for ISO/IEC TR 15907, a Type 3 TR for the revision of ISO 1073/II:1976. On page 18 is a note that says: NOTE – The glyphs previou

Unicode.org downtime reminder

This is a reminder. The Unicode.ORG system (web services, ftp, and mail lists) will be taken off-line sometime today for maintenance and upgrades. We will keep the downtime as short as possible. You will receive another note when the system comes back up, but it may note be possible to warn you

Re: The existing rules for U+FFF9 through to U+FFFC. (spins from Re: Furigana)

On 08/15/2002 06:41:59 AM "William Overington" wrote: >>In essence, though not formally, U+FFF9..U+FFFC are non-characters as >>well, and the Unicode "semantics" just tells what programs *may* find them >>useful for. Unicode 4.0 editors: it might be a good idea to emphasize >>the close relation