#5254 closed defect (fixed)
displaying text files with borgström ....
Reported by: | ThurnerRupert | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | lowest | Milestone: | 0.11 |
Component: | general | Version: | |
Severity: | trivial | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
it seems that source:/sandbox/pycon/workflow/AUTHORS has a characterset which cannot be displayed correctly, in this case jonas borgström. should it be like that or is this a bug in trac?
Attachments (0)
Change History (6)
comment:1 by , 18 years ago
comment:2 by , 17 years ago
The location does not match anymore.
source:trunk/AUTHORS is now the right place.
Easily fixed by doing a:
$ iconv -f iso8859-1 -t utf-8 AUTHORS > new && mv new AUTHORS && svn commit
It writes an UTF-8 BOM and should be recognised by any decent editor worth its encoding salt.
comment:3 by , 17 years ago
Wow:
Avoid usage of BOM markers in UTF-8 files.
This can cause A LOT of issues on non-Windows platforms, and should be avoided.
For example, it can cause a Python script file not to execute on Unix.
comment:4 by , 17 years ago
Wasn't this fixed by [6281]? Are there any remaining issues with this, or can the ticket be closed?
follow-up: 6 comment:5 by , 17 years ago
Milestone: | 0.11.1 → 0.11 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Yes, that file is in UTF-8 now (and there's no BOM marker in it, to address eblot's concerns).
comment:6 by , 17 years ago
Replying to cboos:
Yes, that file is in UTF-8 now (and there's no BOM marker in it, to address eblot's concerns).
Thanks ;-)
It's usually due to a mismatch between ISO-8859-1 and UTF-8.
Jonas' last name is a really good test for this issue, which has already been fixed in several Python source files ;-)
In this case, the file is encoded as ISO-8859-1 while most of the other files are using UTF-8. It guess it should be converted to UTF-8 then.