(Re-sending as I was informed that "posting by email is not allowed"; apologies
to those who get this email twice.)
From: mozilla.dev.platf...@googlegroups.com
[mailto:mozilla.dev.platf...@googlegroups.com] On Behalf Of L. David Baron
>
> On Friday 2017-05-26 11:53 -0600, Tom Tromey wrote:
>> Ho
On Fri, May 26, 2017 at 4:12 AM, wrote:
> Still, sometimes XML fragments come up and even if they are not 100% XML
> spec compliant i still have to process them. This includes encoding
> detection as well, when the XML declaration is missing from the fragments.
>
​Where do the fragments come fro
On Friday 2017-05-26 11:53 -0600, Tom Tromey wrote:
> > "David" == L David Baron writes:
>
> David> I agree it would be good to have a somewhat more "proper" spec for
> David> this. In terms of process, I think probably the most important
> David> (and lowest overhead) aspect of "proper" is
> "David" == L David Baron writes:
David> I agree it would be good to have a somewhat more "proper" spec for
David> this. In terms of process, I think probably the most important
David> (and lowest overhead) aspect of "proper" is having the revision
David> history of the specification in pu
On Fri, May 26, 2017 at 1:50 AM, Gregory Szorc wrote:
> On Thu, May 25, 2017 at 7:43 AM, Eric Rescorla wrote:
>
>> I'd like to second Ehsan's point, but also expand upon it into a more
>> general observation.
>>
>> As it becomes progressively more difficult to build Firefox without mach,
>> it b
On Thu, May 25, 2017 at 7:43 AM, Eric Rescorla wrote:
> I'd like to second Ehsan's point, but also expand upon it into a more
> general observation.
>
> As it becomes progressively more difficult to build Firefox without mach,
> it becomes
> increasingly important that mach respect people's workf
On Thu, May 25, 2017 at 5:31 AM, Ehsan Akhgari
wrote:
> On 05/19/2017 02:44 PM, Gregory Szorc wrote:
>
>> `mach build` attempts to parse compiler warnings to a persisted
>> "database."
>> You can view a list of compiler warnings post build by running `mach
>> warnings-list`. The intent behind thi
On Friday, May 26, 2017 at 10:01:18 AM UTC+3, Henri Sivonen wrote:
> > Think of XML files without the "encoding" attribute in the declaration or
> > HTML files without the meta charset tag.
>
> Per spec, these must be treated as UTF-16 if there's a UTF-16 BOM and
> as UTF-8 otherwise. It's highl
On Thu, May 25, 2017 at 10:44 PM, wrote:
> Think of XML files without the "encoding" attribute in the declaration or
> HTML files without the meta charset tag.
Per spec, these must be treated as UTF-16 if there's a UTF-16 BOM and
as UTF-8 otherwise. It's highly inappropriate to run heuristic
d
9 matches
Mail list logo
