On Jan 29, 2011 8:37 PM, Mark Davis ☕ m...@macchiato.com wrote:
There are really 5 cases at issue:
Code point breaks
Grapheme-Cluster breaks (with three possible variants: 'legacy', extended,
and aksha)
Word breaks
Line breaks
Sentence breaks
Notes:
#1 is pretty trivial to do right in ES.
-discuss-boun...@mozilla.org] on behalf
of Erik Corry [erik.co...@gmail.com]
Sent: Sunday, January 30, 2011 12:32 AM
To: Mark Davis ☕
Cc: Mads Ager; Shawn Steele; es-discuss@mozilla.org
Subject: Re: Stupid i18n use cases question
On Jan 29, 2011 8:37 PM, Mark Davis ☕
m...@macchiato.commailto:m
[erik.co...@gmail.com]
Sent: Sunday, January 30, 2011 12:32 AM
To: Mark Davis ☕
Cc: Mads Ager; Shawn Steele; es-discuss@mozilla.org
Subject: Re: Stupid i18n use cases question
On Jan 29, 2011 8:37 PM, Mark Davis ☕ m...@macchiato.commailto:
m...@macchiato.com wrote:
There are really 5 cases
Cc: es-discuss@mozilla.org; Mads Ager; Mark Davis ☕
Subject: Re: RE: Stupid i18n use cases question
If downloading the data is insufficient then download the code too (in js).
Responsibility for correctness lies with the webpage authors
The alternative is a new way to make windows-only webpages
On Sun, Jan 30, 2011 at 10:32 AM, Shawn Steele
shawn.ste...@microsoft.com wrote:
I'm still trying to grok word processing in JavaScript (beyond the simple
case)
What's to grok? Microsoft is putting word processors on the web,
even. They don't want to go back to the server for all processing
On the phone yesterday we mentioned word/line breaking and grapheme clusters.
It didn't occur to me to ask about the use cases.
Why does someone need word/line breaking in js? It seems like that would
better be done by my rendering engine, like the HTML layout engine or my edit
control or
There are really 5 cases at issue:
1. Code point breaks
2. Grapheme-Cluster breaks (with three possible variants: 'legacy',
extended, and aksha http://www.unicode.org/glossary/#aksara)
3. Word breaks
4. Line breaks
5. Sentence breaks
Notes:
- #1 is pretty trivial to do
Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)
Internationalization is not a feature.
It is an architecture.
From: Mark Davis ☕ [mailto:m...@macchiato.com]
Sent: Saturday, January 29, 2011 11:36 AM
To: Shawn Steele
Cc: es-discuss@mozilla.org
Subject: Re: Stupid i18n use cases question
] on behalf
of Phillips, Addison [addi...@lab126.com]
Sent: Saturday, January 29, 2011 4:19 PM
To: Mark Davis ☕; Shawn Steele
Cc: es-discuss@mozilla.org
Subject: RE: Stupid i18n use cases question
...
For line breaking, the main thing would be to preformat some text. We (the
Lab126 we) use line and word
On Sat, Jan 29, 2011 at 9:24 PM, Shawn Steele
shawn.ste...@microsoft.com wrote:
I realize what line breaking's for, but I didn't think that would often be
done in JavaScript. You preformat some text in JavaScript?
Yeah, for use in SVG or rendering atop canvas, for example.
Mike
-discuss@mozilla.org
Subject: RE: Stupid i18n use cases question
...
For line breaking, the main thing would be to preformat some text. We (the
Lab126 we) use line and word breaking all the time.
Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs
11 matches
Mail list logo
