This thread has got off-topic (reasonably; the new issues are important)
but back on the original point, if we do add ICU then:
On 03/12/12 11:32, Norbert Lindenberg wrote:
- Add the required set of ICU source files as separate files to the
Mozilla repository. The current version of ICU (50.1,
Neil writes:
> Ah, so that explains the fallback flash I experience on a site I
> frequent that makes heavy use of a downloaded symbol font. It is
> irksome because the fallback content is ASCII text ;-)
Just in case others read and want to copy this behaviour, sites
should not be encoding symbo
On 12/5/2012 8:07 AM, Benjamin Smedberg wrote:
On 12/3/2012 5:39 PM, Norbert Lindenberg wrote:
OK, just as an introduction, why we're doing this: The ECMAScript
Internationalization API (which has been approved by Ecma TC 39 and
is on track to become an Ecma standard next week) provides web
ap
On 05.12.12 17:07, Benjamin Smedberg wrote:
On 12/3/2012 5:39 PM, Norbert Lindenberg wrote:
OK, just as an introduction, why we're doing this: The ECMAScript
Internationalization API (which has been approved by Ecma TC 39 and is
on track to become an Ecma standard next week) provides web
applica
On 12/3/2012 5:39 PM, Norbert Lindenberg wrote:
OK, just as an introduction, why we're doing this: The ECMAScript
Internationalization API (which has been approved by Ecma TC 39 and is on track
to become an Ecma standard next week) provides web applications with the
ability to format numbers,
Mike Hommey wrote:
> On Tue, Dec 04, 2012 at 07:51:21AM -0500, Justin Wood (Callek) wrote:
>> Rafael Ávila de Espíndola wrote:
Actually, ICU has several options for how its data is packaged. One option
is libraries (which are not sharable between architectures, AFAIK), but
ano
On Tue, Dec 04, 2012 at 07:51:21AM -0500, Justin Wood (Callek) wrote:
> Rafael Ávila de Espíndola wrote:
> >>
> >> Actually, ICU has several options for how its data is packaged. One option
> >> is libraries (which are not sharable between architectures, AFAIK), but
> >> another possibility is to
On Tue, Nov 27, 2012 at 10:49 AM, Henri Sivonen wrote:
> Therefore, I propose that we adopt the following policy:
> 1) APIs that are shipped on the release channel shall be shipped
> without a prefix.
> 2) If we ship APIs that don't have specs already, we'll write specs.
In yesterday’s platform
On 5/12/12 10:54, Neil wrote:
John Daggett wrote:
Last time I looked, Webkit caches activated fonts, so the second time
the UA loads the same font (e.g. in a different document) it will be
shown immediately without fallback content first.
Ah, so that explains the fallback flash I experience o
John Daggett wrote:
Last time I looked, Webkit caches activated fonts, so the second time the UA
loads the same font (e.g. in a different document) it will be shown immediately
without fallback content first.
Ah, so that explains the fallback flash I experience on a site I
frequent that make
10 matches
Mail list logo
