cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <>
Subject Re: Unicode and XML files
Date Mon, 02 Dec 2013 15:38:52 GMT
Had this starred for a while, but just reading now.

Looks like your changes just add the BOM unconditionally (not dependent on
whether it was there already). That said, if it doesn't break anything, it
probably is more correct to have a BOM.

On Tue, Nov 26, 2013 at 10:31 AM, Josh Soref <> wrote:

> I have three pull requests which I haven’t actually submitted:
> BlackBerry [1], Cli [2], Plugman [3]
> Windows for historical reasons doesn’t default to treating text files as
> UTF-8. Instead files are typically treated as Latin-1 or some other random
> historical encoding. If you want a file to be treated by your typical
> Windows program as UTF-8, you are expected to insert the UTF-8 version of
> the Unicode BOM at the start of the file.
> Per ConfigurationFiles [4], CLI and Plugman take a user authored
> config.xml and generate a platform one (actually, the documentation there
> claims that only Plugman does so, but my work [2] indicates that CLI also
> does so occasionally…). That file is then used by platform code [1] and it
> could also be opened by the user (when there’s a problem).
> Since Windows editors (including Eclipse on Windows [5]…) don’t use UTF-8
> by default, the results can be fairly random or at least inconsistent with
> expectations.
> I’m not absolutely certain that I like my patch set, I could probably get
> away with only doing [1], but it feels like the right behavior for a parser
> would be to honor the input format when producing output, I.e. If there
> were a BOM in the user’s config.xml, produce a BOM in the generated one…
> Thoughts?
> [1]
> [2]
> [3]
> [4]
> [5]
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message