Re: (R), (c) and ?

Richard Wordingham wrote: > Is there any reason why one should wish to select between sober and > funky displays of U+2122 TRADEMARK, U+00AE REGISTERED, and U+00A9 > COPYRIGHT character instance by character instance? I have to agree. If these characters need special cute emoji representations i

Re: (R), (c) and ™

I'd say highly subjective, generally speaking, but the problem here is that there are graphics representations of those and it's not clear when these should be preferred over just plain text representation. Hence my initial question if it was by accident that those chars got in (and yeah, maybe ea

Re: emoji are clearly the current meme fad

On 18 Dec 2014, at 00:41, Martin J. Dürst wrote: > On 2014/12/18 06:49, Michael Everson wrote: >> Clearly the plural of emoji is emojis. > > Not in Japanese, where there are no plural forms. I’m not concerned with the usage in Japanese. > The question of what it is/will be in English will be

Re: (R), (c) and ™

On Thu, 18 Dec 2014 09:42:13 -0200 Leonardo Boiko wrote: > For the record, the emoji selection issue is also affecting the Google > Talk/Hangouts web client, where U+2122 (trademark, ™), U+00AE > (registered, ®), U+00A9 (copyright, ©), and U+2194 (left right arrow, > ↔) seem to be treated as emoj

Re: (R), (c) and ™

yeahright :D On Thu, Dec 18, 2014 at 12:14 PM, Jonathan Rosenne < jonathan.rose...@gmail.com> wrote: > > To pick a nit, it should be COPYRIGHT rather than COPY RIGHT. > > > > Best Regards, > > > > Jonathan Rosenne > > > > *From:* Unicode [mailto:unicode-boun...@unicode.org] *On Behalf Of *Andrea >

RE: (R), (c) and ™

To pick a nit, it should be COPYRIGHT rather than COPY RIGHT. Best Regards, Jonathan Rosenne From: Unicode [mailto:unicode-boun...@unicode.org] On Behalf Of Andrea Giammarchi Sent: Thursday, December 18, 2014 1:10 PM To: Mark Davis ☕️ Cc: Unicode Public Subject: Re: (R), (c) and ™

Re: (R), (c) and ™

For the record, the emoji selection issue is also affecting the Google Talk/Hangouts web client, where U+2122 (trademark, ™), U+00AE (registered, ®), U+00A9 (copyright, ©), and U+2194 (left right arrow, ↔) seem to be treated as emoji and displayed in funky blue: http://namakajiri.net/pics/screensh

Re: (R), (c) and ™

Thanks Mark, I know that emoji != present in there but I need these formatted files for static analysis so I've just copied and pasted from a source file what I use to perform some validation check. (as side note, if these are incomplete I have problems ... any more updated source with same format?

Re: (R), (c) and ™

Note that emoji ≠ present in http://www.unicode.org/Public/UNIDATA/EmojiSources.txt It would probably be useful to read through http://www.unicode.org/reports/tr51/, which is where we are working on various aspects of emoji, in your case especially - http://www.unicode.org/reports/tr51/#Identi

Re: (R), (c) and ™

Thanks Mark, I mean not listened anywhere here: http://unicode.org/Public/UNIDATA/StandardizedVariants.txt I'd expect to find the following there: 00A9 FE0E; text style; # COPY RIGHT MARK 00A9 FE0F; emoji style; # COPY RIGHT MARK for the simple reason that 00A9 is listed as emoji: http://www.u

Re: (R), (c) and ™

2014-12-18, 12:31, Andrea Giammarchi wrote: I wonder if it's by accident that 00AE, 00A9, and 2122 are not listed as standard variant sensitive chars. Why would that be an accident any more than not listing 100,000 other characters there? Or to put it more constructively, why should they b

Re: (R), (c) and ™

On Thu, Dec 18, 2014 at 11:31 AM, Andrea Giammarchi < andrea.giammar...@gmail.com> wrote: > > standard variant sensitive ​It is not clear what you mean by "standard variant sensitive"​. Can you elaborate? Mark *— Il meglio è l’inimico del bene —* __

(R), (c) and ™

Hello there, I wonder if it's by accident that 00AE, 00A9, and 2122 are not listed as standard variant sensitive chars. OSX seems to threat them as such, so adding FE0F will force them to be an image, but I know there are few quirks in this behavior and I wonder if there should be an exception.