ns.
> Where does the translation of the text take place please, and by whom or by
> which computer?
The question of when and how the message translation takes place is also out of
scope for the Working Group. Mr. Verdy has given a great summary introduction
to the process in a separa
}” ).
The Message Format Working Group is to define the *format* of the strings, not
their *repertoire*. That is, should the string be “Arrival: %s” or “Arrival:
${date}” or “Arrival: {0}”?
Does that answer your question?
--
Steven R. Loomis | @srl295 | git.io/srl295
> El ene. 10, 2020, a
2011 Thread:
https://www.unicode.org/mail-arch/unicode-ml/y2011-m08/0124.html
Please read in particular these two:
- https://www.unicode.org/mail-arch/unicode-ml/y2011-m08/0174.html
- https://www.unicode.org/mail-arch/unicode-ml/y2011-m08/0212.html
(tl;dr: 1. the PUA set is fixed, 2. being priva
On Mon, Jun 11, 2018 at 8:32 AM, William_J_G Overington <
wjgo_10...@btinternet.com> wrote:
> Steven R. Loomis wrote:
>
> >Marcel,
> > The idea is not necessarily without merit. However, CLDR does not
> usually expand scope just because of a suggestion.
> I us
> ISO 15924 is and ISO standard. Aspects of its content may be mirrored in
other places, but “moving its content” to CLDR makes no sense.
Fully agreed.
For what it's worth, I reopened a bug of Roozbeh's
https://unicode.org/cldr/trac/ticket/827?#comment:9 to make sure the ISO
15924 French content
CLDR already has localized script names. The English is taken from ISO
15924. https://cldr-ref.unicode.org/cldr-apps/v#/fr/Scripts/
On Tue, Jun 12, 2018 at 8:20 AM, Marcel Schneider via Unicode <
unicode@unicode.org> wrote:
> On Tue, 12 Jun 2018 15:58:09 +0100, Michael Everson via Unicode wrote:
Marcel,
The idea is not necessarily without merit. However, CLDR does not usually
expand scope just because of a suggestion.
I usually recommend creating a new project first - gathering data, looking
at and talking to projects to ascertain the usefulness of common messages..
one of the barriers
Richard,
> But the consortium has formally dropped the commitment to DUCET in CLDR.
> Even when restricted to strings of assigned characters, the
> CLDR and ICU no longer make the effort to support the DUCET
> collation.
CLDR is not a collation implementation, it is a data repository with
associ
Marcel,
On Fri, Jun 8, 2018 at 6:52 AM, Marcel Schneider via Unicode <
unicode@unicode.org> wrote:
>
> What got me started is that before even I requested a submitter ID (and
> the reason why I’ve requested one),
> "Characters | Category | Label | keycap" remained untranslated, i.e. its
> French t
Also just a public note. please do NOT fetch from unicode.org/Public as
part of continuous builds (Jenkins, travis, etc). That's too much load for
files that change *yearly*. Fetch one copy of the data and use your own
copy until it is time to update.
Yes, shasums and signatures are great. ICU (
Depending on DNS propagation, you may see minor glitches today. But the content
should all be back up.
-s
El [FECHA], "[NOMBRE]" <[DIRECCIÓN]> escribió:
>It seems to be back up as of 16:23 UTC.
>
>--
>Doug Ewell | Thornton, CO, US | ewellic.org
Yes, the web content is hosted by google sites, a web hosting provider.
As to it being down, i understand this is being looked into.
Enviado desde nuestro iPhone.
> El oct. 4, 2016, a las 5:51 AM, Cristian Secară escribió:
>
> În data de Tue, 4 Oct 2016 19:50:05 +0800, gfb hjjhjh a scris:
>
El 8/16/16 4:22 PM, "Unicode en nombre de Christoph Päper"
escribió:
>On a related matter, is there any document issued by the Unicode Consortium
>which acknowledges a standard set of “short names” as used in :colon_codes:?
>There are several more or less diverging collections:
See Annotati
William,
I work in the research laboratory (but do not speak for) a large information
technology company. I'm also their primary representative to Unicode and other
standards bodies.
I would not (and have not) leapt from an idea to a document to a standard. I
won't repeat the good and helpful
Hello!
The power symbol was already accepted, see
http://unicode.org/alloc/Pipeline.html
Steven
Enviado desde nuestro iPhone.
> El sept 7, 2015, a las 10:49 AM, Vadim A. Misbakh-Soloviov
> escribió:
>
> Hello there!
>
> First of all, I'm sorry in advance, if my message's tone is not suitab
Thanks Ken; and yes Doug; http://www.unicode.org/L2/L2015/15107.htm#143-C27 was
the reference I was looking for when I wrote my too- brief reply earlier. My
apologies.
S
Enviado desde nuestro iPhone.
> On May 27, 2015, at 2:06 PM, Doug Ewell wrote:
>
> Ken Whistler wrote:
>
>> Read on in
See the meeting minutes and the actual utr51.
Enviado desde nuestro iPhone.
> El may 16, 2015, a las 10:07 AM, Doug Ewell escribió:
>
> L2/15-145R says:
>
>> On some platforms that support a number of emoji flags, there is
>> substantial demand to support additional flags for the following:
>
Here's an analogy: it's more of a piano factory than a concert hall.
S
Enviado desde nuestro iPhone.
> El mar 27, 2015, a las 1:16 PM, Michael Norton
> escribió:
>
> (I know this is way too simplistic a response but it is kind of like giving
> everyone an invisible cloak and an invisible da
>
> El feb 9, 2015, a las 1:21 PM, Markus Scherer escribió:
>
>
> However, I would much prefer if everyone spent their considerable energy on
> upgrading protocols (e.g., IETF RFCs for email subject lines) and lobby
> relevant vendors (e.g., chat services & social network messages) to support
So, for reference as I hadn't seen it discussed yet, but shipping to USA:
ITEMS: 16.24 $USD
Shipping cost (mail) 5.24
Subtotal 21.48
(Plus California tax? 23.09 USD)
Not wanting to downplay annoyances others have noted but I was curious and
wanted to check the price.
S
Enviado desde nuest
On 07/23/2014 11:37 PM, Richard Wordingham wrote:
> On Wed, 23 Jul 2014 20:45:48 +0100
> fantasai wrote:
>> I would like to request that Unicode include, for each writing system
>> it encodes, some information on how it might justify.
> Unicode encodes scripts, and I suspect CLDR only really suppo
On 07/23/2014 03:23 PM, Eric Muller wrote:
> I would like to work with the exemplarCharacters data in the CLDR.
> That uses the UnicodeSet notation. Is there somewhere a parser for
> that notation, that would return me just the list of characters in the
> set? Something a bit like the UnicodeSet ut
David,
Please see the pipeline page and links Ken mentioned at
http://www.unicode.org/alloc/Pipeline.html - the document registry is now
available for perusal.
-s
El miércoles, 11 de septiembre de 2013, David Starner escribió:
> On Tue, Sep 10, 2013 at 11:34 AM, Whistler, Ken
> wrote:
> > Thos
013 at 10:13 PM, Steven R. Loomis
> wrote:
> > Richard,
> > For parse, it's pretty simple: U+0031 has a Unicode digit value. U+FE0E
> > does not. ( Nor is it part of the defined numbering systems in LDML - see
> > http://unicode.org/reports/tr35/#Numbering System D
On Tuesday, March 19, 2013, Richard Wordingham wrote:
> On Mon, 18 Mar 2013 17:28:30 -0700
> "Steven R. Loomis" > wrote:
> > On Monday, March 18, 2013, Richard Wordingham wrote:
>
> > > The issue is rather with emphatically plain text > > U+0032
Richard,
On Monday, March 18, 2013, Richard Wordingham wrote:
> On Mon, 18 Mar 2013 21:07:27 +
> "Whistler, Ken" > wrote:
> > It seems to me that the more
> > significant issue here would be whether the enclosing combining marks
> > are present, whether or not any variation selectors are pre
I don't know, but the sidebar says that a satisfied user is now employed as
translator for a hotel!
On Wed, Feb 20, 2013 at 4:38 PM, Richard Wordingham <
richard.wording...@ntlworld.com> wrote:
> On Wed, 20 Feb 2013 23:29:31 +
> "Whistler, Ken" wrote:
>
> > In the meantime, the eurotalk.com
On Thu, Jul 26, 2012 at 6:19 PM, Richard Wordingham <
richard.wording...@ntlworld.com> wrote:
> On Thu, 26 Jul 2012 17:01:53 -0700
> "Steven R. Loomis" wrote:
>
> > May I ask if you have a specific example in mind? Is the U in ICU
> > misleading somehow, or
On Thu, Jul 26, 2012 at 4:20 PM, Richard Wordingham <
richard.wording...@ntlworld.com> wrote:
> On Thu, 26 Jul 2012 14:33:08 -0700
> Ken Whistler wrote:
>
> > On 7/26/2012 1:21 PM, Richard Wordingham wrote:
> > > I thought the Unicode Consortium had a formal policy of forbidding
> > > untrue (or
On Mon, Jul 9, 2012 at 6:42 AM, Michael Everson wrote:
> On 9 Jul 2012, at 14:32, Harshula wrote:
> > Are you complaining about the inclusion of traditional native Sinhala
> terms for the letters? e.g. From the code chart:
> Yes, I was complaining about that.
>
> > The transliterated form appears
I'd rather see code pages become endangered, and code-page switching an
obscure footnote on the pages of history.
Please, don't invent any new code page systems.
Steven
On 08/19/2011 08:40 AM, srivas sinnathurai wrote:
Doug,
First of all flat code space is the primary functionality of Unicode
[EMAIL PROTECTED] wrote:
> IBM has a web pages to show the contents of their locale information; have
> you checked that?
You can browse the locale explorer at:
http://oss.software.ibm.com/icu/demo/
for example, go to Hindi (India) and you can see it's interesting
grouping pattern under NumberPa
Doug Ewell wrote:
> Why? As an illegal UTF-8 sequence, it shouldn't be interpreted as anything.
It wasn't interpreted as anything. It halted processing at that point
in the text, as an error.
George Zeigler wrote:
> I didn't get it. So what happens if a company had a Job site in Unicode
Here's a gotcha story ..
Someone was working on documentation files in XML. The PDF generator
all of a sudden started choking, complaining that there was "Illegal
character U+DC73" somewhere in the late stages of PDF generation. Well,
the low surrogate certainly didn't belong there. Software bug
g kong could also have zh_HK_SC for
simplified.
Opinions?
-steven
--
Steven R. Loomis - ICU Code Sculptor - [EMAIL PROTECTED] - +1 408.777.5845
IBM CET, Cupertino, Silicon Valley, California, USA - [EMAIL PROTECTED]
http://oss.software.ibm.com/icu --- personal: [EMAIL PROTECTED] -
se,
> Cyrillic, and Arabic on the same page, but we don't need to either. In email
> actually, Unicode would cause problems. W
--
Steven R. Loomis - ICU Code Sculptor - [EMAIL PROTECTED] - +1 408.777.5845
IBM CET, Cupertino, Silicon Valley, California, USA - [EMAIL PROTECTED]
http://o
You will find examples of Devanagari on the ICU locale explorer pages..
http://oss.software.ibm.com/icu/demo/
Try Marathi, Konkani, and Hindi.
The encoding should be UTF-8 by default or you can change it at the
bottom of the page.
Hindi especialy has an extensive but incomplete list of translat
to me like a transliteration problem at first. I have
somewhere a first cut at a unicode <-> braille mapping.
--
Steven R. Loomis - ICU Code Sculptor - [EMAIL PROTECTED] - +1 408.777.5845
IBM CET, Cupertino, Silicon Valley, California, USA - [EMAIL PROTECTED]
http://oss.software.ibm.com/icu --- personal: [EMAIL PROTECTED] -
"Ayers, Mike" wrote:
> This would allow proper
> rendering for both types of words, so that, say "piece" wouldn't be rendered
> with the "i" and "e" joined. Did I misunderstand?
As Mr. Adall said, the rendering appears as 'i' + 'e', and 'g' +
'\u0127'. There isn't a difference in rendering. Is
39 matches
Mail list logo
