Skip to content

File encodings are not all UTF-8 #2

Open
@rsharvey

Description

@rsharvey

ERL: OTP 17.4
Exodm: master

Feel free to ignore this, it was discovered when I was trying to build something with the latest code and OTP version.

There are several files with non utf-8 encodings. In some cases, this just generates an error. In other modules where the "warnings_as_errors" flag is set, it fails the build.

In lhttpc:

ERROR: Failed to extract name from /home/git/feuerlabs/exodm/deps/lhttpc/src/lhttpc.app.src: {27, file_io_server, invalid_unicode}

Just deleting the comment at the top of the file or forcing UTF-8 encoding fixes this.

In yaws:

==> yaws (compile)
--- Will not overwrite /home/rob/git/feuerlabs/exodm/deps/yaws/etc/yaws/yaws.conf
--- Installing local config file at /home/rob/git/feuerlabs/exodm/deps/yaws/etc/yaws/yaws.conf.template
/home/rob/git/feuerlabs/exodm/deps/yaws/src/yaws_xmlrpc.erl:1: Non-UTF-8 character(s) detected, but no encoding declared. Encode the file in UTF-8 or add "%% coding: latin-1" at the beginning of the file. Retrying with latin-1 encoding.
ERROR: compile failed while processing /home/rob/git/feuerlabs/exodm/deps/yaws: rebar_abort
make: *** [compile] Error 1

Also the following files in yaws have different encodings:

/exodm/deps/yaws/src/yaws_jsonrpc.erl
/eoxdm/deps/yaws/src/yaws_rpc.erl

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions