Re: New Unicode Working Group: Message Formatting

las 2:48 p. m., James Kass via Unicode > escribió: > > > On 2020-01-10 9:55 PM, announceme...@unicode.org wrote: >> But until now we have not had a syntax for localizable message strings >> standardized by Unicode. > > What is the difference between “localizabl

Re: New Unicode Working Group: Message Formatting

* sentences On 2020-01-10 10:48 PM, James Kass wrote: On 2020-01-10 9:55 PM, announceme...@unicode.org wrote: But until now we have not had a syntax for localizable message strings standardized by Unicode. What is the difference between “localizable message strings” and “localized

Re: New Unicode Working Group: Message Formatting

On 2020-01-10 9:55 PM, announceme...@unicode.org wrote: But until now we have not had a syntax for localizable message strings standardized by Unicode. What is the difference between “localizable message strings” and “localized sentances”?  Asking for a friend.

Re: how to make custom combining diacritical marks for arabic letters?

middle, end, separate B characters instead > of using simple arabic B, that would be easier. (you can see in the > example that that characters are used). (using different forms of > letter can also be achieved by using php or javascript, etc). > > > > > 2018-05-17 22:12 GMT+03:

Free emoji (from Re: Videos on YouTube)

Johannes Bergerhausen wrote: West is located in the former US embassy, a brutalist building by Marcel Breuer (Bauhaus): www.westdenhaag.nl On that web page is a link to the following web page. http://www.westdenhaag.nl/exhibitions/20_02_Alphabetum_6 The title

Re: Videos on YouTube

m 11:34 schrieb wjgo_10...@btinternet.com via Unicode > : > > I searched on YouTube for > > Gutenberg Mainz > > and filtered for > > This week > > and I found 12 videos uploaded 3 days ago about a symposium called > Alphabetica 2019. > > Apparently hel

Call for Papers: G21C Grapholinguistics in the 21st century, Paris June 2020

Happy New Year to everybody on this list! Except for the Internationalization and Unicode Conference (see https://www.unicodeconference.org/; submission deadline March 6, 2020), this list very rarely sees calls for papers, but this one should definitely be of interest at least to a subset of

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On Sat, 4 Jan 2020 22:15:59 + James Kass via Unicode wrote: > For the Grantha examples above, Grantha (1) displays much better > here. It seems daft to put a spacing character between a base > character and any mark which is supposed to combine with the base > character. A

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On 2020-01-04 12:50 PM, Richard Wordingham via Unicode wrote: dev2: कः꣡ dev3: क꣡ः Grantha: (1) ጕ፧ጃ (2) ጕጃ፧ The second Grantha spelling is enabled by a Harfbuzz-only change to the USE categorisations. It treats Grantha visarga and spacing anusvara as though inpc=Top rather than inpc

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On Thu, 2 Jan 2020 20:20:34 + Richard Wordingham via Unicode wrote: > There's a project whose basis I can't find to convert Indian Indic > rendering at least to use the USE. Now, according to the > specification of the USE, visarga, anusvara and cantillation marks > are al

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On Thu, 2 Jan 2020 15:07:04 -0800 Norbert Lindenberg wrote: >> On Jan 2, 2020, at 12:20, Richard Wordingham via Unicode >> wrote: >> So, the problem should already be solved for Grantha, and, >> if the plans come to fruition, will work with a font whose >>

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On Thu, 2 Jan 2020 07:52:55 + James Kass via Unicode wrote: > > I've been looking at Microsoft's specification of Devanagari > > character order.  In > > > https://docs.microsoft.com/en-us/typography/script-development/devanagari, > > the consonant

Re: Call for feedback on UTS #18: Unicode Regular Expressions

e above line, but a recap that didn't have precisely the same description. It's best to point to the exact description, and have that be in one place. Mark On Thu, Jan 2, 2020 at 6:40 PM Karl Williamson via Unicode < unicode@unicode.org> wrote: > One thing I noticed in reviewing this is the

Re: Call for feedback on UTS #18: Unicode Regular Expressions

One thing I noticed in reviewing this is the removal of text about loose matching of the name property. But I didn't see an explanation for this removal. Please point me to the explanation, or tell me what it is. Specifically these lines were removed: As with other property values, names

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On 2020-01-02 1:04 AM, Richard Wordingham wrote in a thread deriving from this one, > Have you found a definition of the ISCII handling of Vedic characters? No.  It would be helpful.  ISCII apparently wasn't really used much.  It would also be helpful to know the encoding order in any

Re: One encoding per shape (was Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara)

On Wed, 1 Jan 2020 20:11:04 + James Kass via Unicode wrote: > On 2020-01-01 11:17 AM, Richard Wordingham via Unicode wrote: > > > That's exactly the sort of mess that jack-booted renderers are > > trying to minimise.  Their principle is that there should be only >

Re: One encoding per shape (was Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara)

On Wed, 1 Jan 2020 23:09:49 + James Kass via Unicode wrote: > On 2020-01-01 8:11 PM, James Kass wrote: > > It’s too bad that ISCII didn’t accomodate the needs of Vedic > > Sanskrit, but here we are. > > Sorry, that might be wrong to say.  It's possible that it's Un

Re: One encoding per shape (was Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara)

On 2020-01-01 8:11 PM, James Kass wrote: It’s too bad that ISCII didn’t accomodate the needs of Vedic Sanskrit, but here we are. Sorry, that might be wrong to say.  It's possible that it's Unicode's adaptation of ISCII that hinders Vedic Sanskrit.

One encoding per shape (was Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara)

On 2020-01-01 11:17 AM, Richard Wordingham via Unicode wrote: > That's exactly the sort of mess that jack-booted renderers are trying > to minimise.  Their principle is that there should be only one encoding > per shape, though to be fair: > > 1) some renderers accept canoni

Re: emojis for mouse buttons?

and rtl writing. On Wed, 1 Jan 2020 10:08:42 -0500 John W Kennedy via Unicode wrote: > As I have already said, this will not do. Mouses do not have “left” > and “right” buttons; they have “primary” buttons, which may be on the > left or right, and “secondary” buttons, which may be on

Re: emojis for mouse buttons?

ot; > -- Charles Williams. "Bors to Elayne: On the King's Coins" > > > On Jan 1, 2020, at 6:43 AM, Marius Spix via Unicode > wrote: > > > > Cecause the middle button of many mice is a scroll button, I think, we > > need five different characters:

Re: emojis for mouse buttons?

. -- John W. Kennedy "Compact is becoming contract, Man only earns and pays." -- Charles Williams. "Bors to Elayne: On the King's Coins" > On Jan 1, 2020, at 6:43 AM, Marius Spix via Unicode > wrote: > > Cecause the middle button of many mice is a scroll

Re: emojis for mouse buttons?

23:04:39 +0100 Philippe Verdy via Unicode WROTE: > Playing with the fiolling of the middle cell to mean a double click > is a bad idea, it would be better to add one or two rounded borders > separated from the button, or simply display two icons in sequence > for a double click

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On Wed, 1 Jan 2020 01:19:02 + James Kass via Unicode wrote: > A workaround until some kind of satisfactory adjustment is made might > be to simply use COLON for VISARGA.  Or... > >  VISARGA ⇒ U+02F8 MODIFIER LETTER RAISED COLON > ANUSVARA⇒U+02D9 DOT ABOVE > > ...

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

A workaround until some kind of satisfactory adjustment is made might be to simply use COLON for VISARGA.  Or...  VISARGA ⇒ U+02F8 MODIFIER LETTER RAISED COLON ANUSVARA⇒U+02D9 DOT ABOVE ...as long as the font(s) included both those characters. य॑ यॆ॑ य॑ं -- anusvara last यॆ॑ं -- " य॑: --

Re: Long standing problem with Vedic tone markers and post-base visarga/anusvara

On 2019-12-21 6:27 AM, Shriramana Sharma via Unicode wrote: However, even the simplest Vedic sequence (not involving Sama Vedic or multiple tone marker combinations) like दे॒वेभ्य॑ः throws up a dotted circle, and one is expected (see developer feedback in that bug report) to input the visarga

Re: emojis for mouse buttons?

-styles could use more realistic 3D-like rendering with extra shadows... Le mar. 31 déc. 2019 à 22:16, wjgo_10...@btinternet.com via Unicode < unicode@unicode.org> a écrit : > How about the following. > > A filled upper cell to mean click, > > a filled upper cell and a fille

Re: emojis for mouse buttons?

be unambiguous in monochrome as a display default. William Overington Tuesday 31 December 2019 -- Original Message -- From: "Philippe Verdy via Unicode" To: "Shriramana Sharma" Cc: "unicode Unicode Discussion" Sent: Tuesday, 2019 Dec 31 At 15:49 Subject

Re: emojis for mouse buttons?

day 31 December 2019 -- Original Message -- From: "Philippe Verdy via Unicode" To: "unicode Unicode Discussion" Sent: Tuesday, 2019 Dec 31 At 13:13 Subject: emojis for mouse buttons? A lot of application need to document their keymap and want to display keys.

Re: emojis for mouse buttons?

mpact is becoming contract, Man only earns and pays." -- Charles Williams. "Bors to Elayne: On the King's Coins" > On Dec 31, 2019, at 10:52 AM, Philippe Verdy via Unicode > wrote: > >  > I say "emoji" because they would belong to the subsets of emo

Re: emojis for mouse buttons?

t in three cells by horizontal and vertical strokes, and one of the three cells filled (representing the wire or the wireless waves is not necessary). Le mar. 31 déc. 2019 à 14:57, Shriramana Sharma a écrit : > Why are these called "emojis" for mouse buttons rather than just > "

Re: emojis for mouse buttons?

Why are these called "emojis" for mouse buttons rather than just "characters" for them? On Tue, 31 Dec, 2019, 18:45 Philippe Verdy via Unicode, wrote: > A lot of application need to document their keymap and want to display > keys. > > For now there are emojis fo

emojis for mouse buttons?

A lot of application need to document their keymap and want to display keys. For now there are emojis for mouses (several variants: 1, 2 or 3 buttons), independently of the button actually pressed. However there's no simple emoji to represent the very common mouse click buttons used in lot of

Twitter corrects Kwanzaa emoji

https://thehill.com/policy/technology/476086-social-media-users-call-out-twitter-over-kwanzaa-emoji

Re: Not accepted by UTC but in ISO ballot?

repertoire. --Ken On 12/27/2019 7:06 AM, Shriramana Sharma via Unicode wrote: Now I'm wondering about the similar category "not accepted by UTC, and not in ISO ballot" – why such a character would be mentioned on the pipeline at all…

Videos on YouTube

I searched on YouTube for Gutenberg Mainz and filtered for This week and I found 12 videos uploaded 3 days ago about a symposium called Alphabetica 2019. Apparently held in Amsterdam. It seems that the videos were listed for that search as the notes include "Presented in collaboration

Re: Not accepted by UTC but in ISO ballot?

Dec, 2019, 07:19 Ken Whistler, wrote: > Shriramana, > > On 12/20/2019 6:29 PM, Shriramana Sharma via Unicode wrote: > > I was looking at the pipeline for something else, and for the first > > time I see a character category: “not accepted by the UTC but in ISO > > ballot”

Re: Not accepted by UTC but in ISO ballot?

Shriramana, On 12/20/2019 6:29 PM, Shriramana Sharma via Unicode wrote: I was looking at the pipeline for something else, and for the first time I see a character category: “not accepted by the UTC but in ISO ballot” and two characters in it. Those two characters changed status as of December 4

proofreading symbols (Korrekturzeichen) according to DIN 16511

Hello, after some clumsy and therefore unsuccessful efforts to find equivalents to the proofreading symbols defined in DIN 16511 I joined this list to ask where I can fin these symbols or lookalikes of them in Unicode. Here a webpage I found that lists these symbols and their meanings:

Re: Re: NBSP supposed to stretch, right?

So I was wondering whether TeX only does this to the ~ input character or the actual NBSP Unicode character too?

Re: NBSP supposed to stretch, right?

On 12/19/19, James Kass via Unicode wrote: > > There's a bug report for the LibreOffice application here... > https://bugs.documentfoundation.org/show_bug.cgi?id=41652 > ...which shows an interesting history of the situation. LOL two years ago almost to the date Shriramana Sharma s

Aw: Not accepted by UTC but in ISO ballot?

So, WG2 N5058, was literally a TROLL submission. > Gesendet: Samstag, 21. Dezember 2019 um 03:29 Uhr > Von: "Shriramana Sharma via Unicode" > An: "UnicoDe List" > Betreff: Not accepted by UTC but in ISO ballot? > > I was looking at the pipeline for some

Long standing problem with Vedic tone markers and post-base visarga/anusvara

https://github.com/harfbuzz/harfbuzz/issues/2017 should provide the context for this. Ever since the early days of Devanagari Unicode, scholars like me dealing with Vedic Sanskrit orthography have been experiencing this problem, but chalked it upto early days and consequent insufficient support

Re: NBSP supposed to stretch, right?

On 2019-12-21 2:43 AM, Shriramana Sharma via Unicode wrote: Ohkay and that's very nice meaningful feedback from actual developer+user interaction. So the way I look at this going forward is that we have four options: 1) With the existing single NBSP character, provide a software option

Re: NBSP supposed to stretch, right?

On 12/21/19, Richard Wordingham via Unicode wrote: > On Fri, 20 Dec 2019 17:25:17 +0530 > Shriramana Sharma via Unicode wrote: > >> I don't expect NBSP to ever disappear, because spaces disappear only >> at linebreaks, and NBSP simply doesn't stand at linebreaks. > &

Re: [EXTERNAL] Re: NBSP supposed to stretch, right?

On 12/21/19, Shriramana Sharma wrote: > 1) > > With the existing single NBSP character, provide a software option to > either make it flexible or inflexible, but this preference should be > stored as part of the document and not the application settings, else > shared documents would not preserve

Re: [EXTERNAL] Re: NBSP supposed to stretch, right?

On 12/21/19, Murray Sargent wrote: > I checked with the Word team and they actually tried out stretching NBSP > back in 2015 in the "good client" mode. But customer feedback was negative. > The problem is that NBSP is used sometimes when stretching isn't wanted such > as between the end of a

Not accepted by UTC but in ISO ballot?

I was looking at the pipeline for something else, and for the first time I see a character category: “not accepted by the UTC but in ISO ballot” and two characters in it. So IIUC while technically people are free to submit a document to the ISO separately without submitting to UTC, it has always

Re: NBSP supposed to stretch, right?

On Fri, 20 Dec 2019 17:25:17 +0530 Shriramana Sharma via Unicode wrote: > So I never asked for NBSP to disappear. I said I want it to *stretch*. > And to my mind "stretch" means to become wider than one's normal > width. It doesn't include decreasing or disappearing w

Re: HEAVY EQUALS SIGN

On 12/20/2019 7:17 AM, wjgo_10...@btinternet.com via Unicode wrote: It is indeed interesting that the Notice of Non-Approval itself uses italics for emphasis in two places. That text, at the present time, cannot be expressed in Unicode plain text with the emphasis that the Notice of Non

Re: HEAVY EQUALS SIGN

On the matter of my document proposing using Variation Selector 14 for requesting an italic glyph for a letter, Unicode Inc. has also published a Notice of Non-Approval. https://www.unicode.org/alloc/nonapprovals.html It is indeed interesting that the Notice of Non-Approval itself uses

Re: NBSP supposed to stretch, right?

From our colleague’s web site, http://jkorpela.fi/chars/spaces.html “On web browsers, no-break spaces tended to be non-adjustable, but modern browsers generally stretch them on justification.” Jukka Korpela then offers pointers about avoiding unwanted stretching. and “The change in the

Re: NBSP supposed to stretch, right?

On 2019-12-17 12:50 AM, Shriramana Sharma via Unicode wrote: I would have gone and filed this as a LibreOffice bug since that's the software I use most, but when I found this is a cross-software problem, I thought it would be best to have this discussed and documented here (and in a future

Re: HEAVY EQUALS SIGN

On 2019-12-18 12:42 PM, Marius Spix via Unicode wrote: Unicode has a HEAVY PLUS SIGN (U+2795) and a HEAVY MINUS SIGN (U+2796). I wonder, if a HEAVY EQUALS SIGN could complete that character set. This would allow emoji phrases like  ➕= ❤️. (man plus cat equals love) looking typographically

Re: HEAVY EQUALS SIGN

On Wednesday, December 18, 2019 9:43:06 PM PST Joao S. O. Bueno via Unicode wrote: > Maybe it would make more sense to try and check whether modification > combining characters to shift the change the combined character into other > weight/decoration/color and/or other character effe

Re: NBSP supposed to stretch, right?

U+0020 SPACE U+00A0 NO-BREAK SPACE These two characters are equal in every way except that one of them offers an opportunity for a line break and the other does not. If the above statement is true, then any conformant application must treat/process/display both characters identically.

Re: NBSP supposed to stretch, right?

On 12/17/2019 5:49 PM, James Kass via Unicode wrote: Asmus Freytag wrote, > And any recommendation that is not compatible with what the overwhelming > majority of software has been doing should be ignored (or

Re: HEAVY EQUALS SIGN

09:42, Marius Spix via Unicode wrote: > Unicode has a HEAVY PLUS SIGN (U+2795) and a HEAVY MINUS SIGN (U+2796). > I wonder, if a HEAVY EQUALS SIGN could complete that character set. > This would allow emoji phrases like  ➕= ❤️. (man plus cat equals > love) looking typographicall

HEAVY EQUALS SIGN

Unicode has a HEAVY PLUS SIGN (U+2795) and a HEAVY MINUS SIGN (U+2796). I wonder, if a HEAVY EQUALS SIGN could complete that character set. This would allow emoji phrases like  ➕= ❤️. (man plus cat equals love) looking typographically better, when you replace the equals sign with a new HEAVY

Re: NBSP supposed to stretch, right?

Asmus Freytag wrote, > And any recommendation that is not compatible with what the overwhelming > majority of software has been doing should be ignored (or only enabled on > explicit user input). > > Otherwise, you'll just advocating for a massively breaking change. It seems like the

Re: NBSP supposed to stretch, right?

On 12/17/2019 11:31 AM, James Kass via Unicode wrote: So it follows that any justification operation should treat NO-BREAK SPACE and SPACE identically. And any recommendation that is not compatible with what the overwhelming majority of software

Re: NBSP supposed to stretch, right?

On Tue, 17 Dec 2019 06:20:39 +0530 Shriramana Sharma via Unicode wrote: > Hello. I've just tested LibreOffice, Google Docs and MS Office on > Linux, Android and Windows, and it seems that NBSP doesn't get > stretched like the normal space character when justified alignment &

Re: NBSP supposed to stretch, right?

On 2019-12-17 10:37 AM, QSJN 4 UKR via Unicode wrote: Agree. By the way, it is common practice to use multiple nbsp in a row to create a larger span. In my opinion, it is wrong to replace fixed width spaces with non-breaking spaces. Quote from Microsoft Typography Character design standards

Re: NBSP supposed to stretch, right?

On 12/17/2019 2:41 AM, Shriramana Sharma via Unicode wrote: On Tue 17 Dec, 2019, 16:09 QSJN 4 UKR via Unicode, <unicode@unicode.org> wrote: Agree. By t

Re: NBSP supposed to stretch, right?

On Tue 17 Dec, 2019, 16:09 QSJN 4 UKR via Unicode, wrote: > Agree. > By the way, it is common practice to use multiple nbsp in a row to > create a larger span. In my opinion, it is wrong to replace fixed > width spaces with non-breaking spaces. > Quote from Microsoft Typography C

Fwd: NBSP supposed to stretch, right?

Agree. By the way, it is common practice to use multiple nbsp in a row to create a larger span. In my opinion, it is wrong to replace fixed width spaces with non-breaking spaces. Quote from Microsoft Typography Character design standards: «The no-break space is not the same character as the figure

NBSP supposed to stretch, right?

Hello. I've just tested LibreOffice, Google Docs and MS Office on Linux, Android and Windows, and it seems that NBSP doesn't get stretched like the normal space character when justified alignment requires it. Let me explain. I'm creating a document with the following text typeset in 12 pt Lohit

Fwd: ICU 66preview available

Dear Unicoders, If you use ICU, then testing with ICU 66*preview* is a good way of trying out Unicode 13 *beta* . (Just please don't use these snapshots in production releases.) Best regards,

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Tue, 3 Dec 2019 17:35:14 +0530 विश्वासो वासुकिजः (Vishvas Vasuki) via Unicode wrote: > On Tue, Dec 3, 2019 at 3:48 PM Richard Wordingham via Unicode < > unicode@unicode.org> wrote: > > On Tue, 3 Dec 2019 02:05:35 + > > Richard Wordingham via Unicode wrote: &

Re: Proposal to add Roman transliteration schemes to ISO 15924.

I think the 'Latn' in sa-Latn-t-sa-m0-iast is unnecessary, though it partly depends on the range of the IAST transform. If the transformation can only convert to the Roman script then 'Latn' is superfluous; I'm not sure if the extension is formally enough to rule out Devanagari. On the other

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Tue, 3 Dec 2019 02:05:35 + Richard Wordingham via Unicode wrote: > I'm still trying to work out what to do for IAST. Is it just: > > sa-t-m0-iast > > if one finds that > > sa-Latn > > allows too much latitude? For material that is a transcription ra

Re: Proposal to add Roman transliteration schemes to ISO 15924.

c 3, 2019 at 2:31 AM Richard Wordingham via Unicode < unicode@unicode.org> wrote: > On Mon, 2 Dec 2019 09:09:02 -0800 > Markus Scherer via Unicode wrote: > > > On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode < > > unicode@unicode.org> wrote: > &g

Re: A neat description of encoding characters

On 12/2/19 7:01 AM, Costello, Roger L. via Unicode wrote: >From the book titled "Computer Power and Human Reason" by Joseph Weizenbaum, p.74-75 It's a reasonably good explanation of binary numbers and "encoding" in a more usual sense than we use it here in Unicod

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Tue, 3 Dec 2019 01:27:39 + Richard Wordingham wrote: > On Mon, 2 Dec 2019 09:09:02 -0800 > Markus Scherer via Unicode wrote: > > > On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode < > > unicode@unicode.org> wrote: > > > > &g

Re: A neat description of encoding characters

On 2019-12-03 12:59 AM, Richard Wordingham via Unicode wrote: On Mon, 2 Dec 2019 12:01:52 + "Costello, Roger L. via Unicode" wrote: From the book titled "Computer Power and Human Reason" by Joseph Weizenbaum, p.74-75 Suppose that the alphabet with which we wish

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Mon, Dec 2, 2019 at 5:47 PM विश्वासो वासुकिजः (Vishvas Vasuki) via Unicode wrote: > But that says that the definitions are at >> > >> https://github.com/unicode-org/cldr/releases/tag/latest/common/bcp47/transform.xml >> , >> but all one currently gets from

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Mon, 2 Dec 2019 09:09:02 -0800 Markus Scherer via Unicode wrote: > On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode < > unicode@unicode.org> wrote: > > > You don't need an ISO 15924 script code. You need to think in terms > > of BCP 47. Sanskri

Re: A neat description of encoding characters

On Mon, 2 Dec 2019 12:01:52 + "Costello, Roger L. via Unicode" wrote: > From the book titled "Computer Power and Human Reason" by Joseph > Weizenbaum, p.74-75 > > Suppose that the alphabet with which we wish to concern ourselves > consists of 256 dis

Re: Proposal to add Roman transliteration schemes to ISO 15924.

On Mon, Dec 2, 2019 at 8:42 AM Roozbeh Pournader via Unicode < unicode@unicode.org> wrote: > You don't need an ISO 15924 script code. You need to think in terms of BCP > 47. Sanskrit in Latin would be sa-Latn. > Right! Now, if you want to distinguish the different transc

Re: Proposal to add Roman transliteration schemes to ISO 15924.

may also be useful to you: https://tools.ietf.org/html/rfc6497 On Mon, Dec 2, 2019, 7:48 AM विश्वासो वासुकिजः (Vishvas Vasuki) via Unicode wrote: > bcc: as an FYI - plz respond on > the unicode mailing list as needed. > > namaste! > > Sanskrit has traditionally been wr

Re: A neat description of encoding characters

Liang Hai via Unicode wrote: > Grrr… It’s an okayish analog for binary numbers, but not really relevant > to character encoding. Encoded characters are just assigned with integers, > which could in turn be represented in any base. > > The binary nature of computers’ way of stori

Re: A neat description of encoding characters

encoding works—unless you really want to start explaining character encoding with those so basic ideas such as “What is electricity?”, “What is a computer?”, … Best, 梁海 Liang Hai https://lianghai.github.io > On Dec 2, 2019, at 20:01, Costello, Roger L. via Unicode > wrote: > > F

A neat description of encoding characters

>From the book titled "Computer Power and Human Reason" by Joseph Weizenbaum, >p.74-75 Suppose that the alphabet with which we wish to concern ourselves consists of 256 distinct symbols. Imagine that we have a deck of 256 cards, each of which has a distinct symbol of our alphabet printed on

RE: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

From: Unicode On Behalf Of Costello, Roger L. via Unicode Sent: Tuesday, November 19, 2019 11:00 AM To: unicode@unicode.org Subject: Is the Unicode Standard "The foundation for all modern software and communications around the world"? Hi Folks, Today I received an email from t

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

On Tue, 19 Nov 2019 20:02:55 + James Kass via Unicode wrote: > On 2019-11-19 6:59 PM, Costello, Roger L. via Unicode wrote: > > Today I received an email from the Unicode organization. The email > > said this: (italics and yellow highlighting are mine) > > >

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

On 2019-11-19 11:00 PM, Mark E. Shoulson via Unicode wrote: Why so concerned with these minutiæ? Were you in fact misled?  (Doesn't sound like it.)  Do you know someone who was, or whom you fear would be?  What incorrect conclusions might they draw from that misunderstanding, and how serious

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

On 11/19/2019 3:00 PM, Mark E. Shoulson via Unicode wrote: It says "foundation", not "sum total, all there is."  I don't think this is much overreach.  MAYBE it counts as "enthusiastic", but not misleadi

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

ho was, or whom you fear would be?  What incorrect conclusions might they draw from that misunderstanding, and how serious would they be?  Doesn't sound like this is really anything serious even if you were right. ~mark On 11/19/19 1:59 PM, Costello, Roger L. via Unicode wrote: Hi Folks,

RE: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

everything (good things and not so good too). Best Regards, Jonathan Rosenne -Original Message- From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of James Kass via Unicode Sent: Tuesday, November 19, 2019 10:03 PM To: unicode@unicode.org Subject: Re: Is the Unicode Standard

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

On 11/19/2019 12:04 PM, Michael Everson via Unicode wrote: Of course it’s not “misleading”. Human language is best conveyed by text. One could insert the language in [ ] to make the claim sound less like an overreach. It doesn't even impede

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

On 2019-11-19 6:59 PM, Costello, Roger L. via Unicode wrote: Today I received an email from the Unicode organization. The email said this: (italics and yellow highlighting are mine) The Unicode Standard is the foundation for all modern software and communications around the world, including

Re: Is the Unicode Standard "The foundation for all modern software and communications around the world"?

Of course it’s not “misleading”. Human language is best conveyed by text. Michael Everson > On 19 Nov 2019, at 18:59, Costello, Roger L. via Unicode > wrote: > > Hi Folks, > > Today I received an email from the Unicode organization. The email said this: > (italics an

Is the Unicode Standard "The foundation for all modern software and communications around the world"?

Hi Folks, Today I received an email from the Unicode organization. The email said this: (italics and yellow highlighting are mine) The Unicode Standard is the foundation for all modern software and communications around the world, including all modern operating systems, browsers, laptops, and

Re: New Public Review on QID emoji

Asmus Freytag wrote as follows. Just because a select group of people engages in communication about the arcane details of a proposed specification it doesn't mean that the outcome will benefit some entirely different and larger group communicate better. This is logically true. However the

Re: New Public Review on QID emoji

On 2019-11-13 3:00 AM, Asmus Freytag via Unicode wrote: The current effort starts from an unrelated problem (Unicode not wanting to administer emoji applications) and in my analysis, seriously puts the cart before the horse. But it does solve the unrelated problem. There's nothing stopping

Re: New Public Review on QID emoji

On 11/12/2019 12:32 PM, wjgo_10...@btinternet.com via Unicode wrote: > Just because you can write something that is a very detailed specification doesn't mean that it is, or ever should be, a standard. Yes, but that does not m

Re: New Public Review on QID emoji

Asmus Freytag wrote as follows. If leading standardization was such a good thing in communication, why don't we see more "dictionaries of words not yet in use"? After all, it would be a huge benefit for people coining new terms to have their definitions already worked out. Nothing inherent in

Re: New Public Review on QID emoji

On 11/12/2019 8:41 AM, wjgo_10...@btinternet.com via Unicode wrote: Asmus Freytag wrote as follows. While I have a certain understanding for the underlying concerns, it still is the case that this proposal promises to be a bad

Re: New Public Review on QID emoji

Asmus Freytag wrote as follows. While I have a certain understanding for the underlying concerns, it still is the case that this proposal promises to be a bad example of "leading standardization": throwing out a spec in the hopes it may be taken up and take off, instead of something that

RE: New Public Review on QID emoji

WJGO >>Yet if QID emoji are implemented by Unicode Inc. without also being implemented by ISO/IEC 10646 then that could lead to future problems, ... Peter Constable wrote as follows. Neither Unicode Inc. or ISO/IEC 10646 would _implement_ QID emoji. That is correct. I should have made

<    1   2   3   4   5   6   7   8   9   10   >