This repository has been archived by the owner on Oct 4, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
False-Errors With Latin1 #169
Comments
Here's a link to the repository where I've encountered this problem: I had to suppress the ## Hugo Interactive Fiction
###########################
; Hugo sources are strictly in ISO-8859-1 (aka Latin1).
; https://www.generalcoffee.com/hugo
[hugo/*.{hug,h,g}]
; charset = latin1 # BUGGY: reports acute accent as invalid char.
; (see: github.com/jedmao/eclint#169)
indent_style = space
indent_size = unset
end_of_line = unset
trim_trailing_whitespace = true
insert_final_newline = true because it was reporting the following errors for the
|
tajmone
added a commit
to tajmone/highlight-test-suite
that referenced
this issue
Nov 14, 2019
* Hugo Syntax: * Merge `hugo-lang-dev` branch into `master` with new Hugo v1.1.0 syntax, as submitted to Highlight (See: saalen/highlight!122). This should make the Highlight GitLab CI tests for Hugo pass, since the Hugo syntax has changed considerably and the old tests no longer apply. * Repository Settings: * Tweak and optimize Git setting. * Add Hugo patterns to Git and EditorConfig setting. * Polish all Hugo files to pass EClint validation. NOTE: Had to disable `charset = latin1` for Hugo in `.editorconfig` due to a bug reporting acute accents as an invalid Latin1 chars. ( See: jednano/eclint#169 )
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
EClint reports as an error the presence of an acute accent ($B4:
´
) inside an ISO-8859-1 encoded file configured tocharset = latin1
:The text was updated successfully, but these errors were encountered: