Your message dated Sat, 06 May 2017 16:56:17 +1000
with message-id <1733261.JVXA9TWjvj@jatayu>
and subject line Re: Bug#861904: qtikz: Strange leading <FEFF> character added
to newly created file.
has caused the Debian Bug report #861904,
regarding qtikz: Strange leading <FEFF> character added to newly created file.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
861904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qtikz
Version: 0.11~git20161122-1
Severity: normal
Dear Maintainer,
I have been noticing a strange behavior in qtikz when adding the
tikzpicture environment to new tikz files.
* qtikz
* Add tikzpicture environment
* Save as e.g. test.tikz
Saved file (attached as "test.tikz") contains an spurious leading <FEFF>
character.
This seems to only happen first time new file is written, no matter what
command is put by qtikz (not only tikzpicture).
Note that this char is not easily seen in all editors, I can see it in joe
and mc viewer. To make this more clear I have also attached as
"test-stripped.tikz" " the same file, but with that char removed.
Regards,
--
Agustin
\begin{tikzpicture}
\end{tikzpicture}\begin{tikzpicture}
\end{tikzpicture}
--- End Message ---
--- Begin Message ---
Hi Agustin,
> Saved file (attached as "test.tikz") contains an spurious leading <FEFF>
> character.
The <FEFF> is the "byte order mark" which is an (optional) part of unicode
standards that tells the consumer of the data whether the multi-byte data is
little endian or big endian.
The BOM is supposed to be seemlessly handled by anything that is accepting
UTF-8 encoded data such as the files produced by qtikz; tools not handling the
BOM are buggy so if the BOM is causing problems, please report bugs against
those tools. It sounds like joe and mc don't handle UTF-8 files correctly.
If you'd rather not have the BOM, you can disable the addition of the BOM to
documents in the qtikz settings.
Settings → Configure QtikZ → Editor → Encoding
UTF-8 without BOM
(I too dislike the BOM in what I think of as a 'plain text file' but I also
recognise that reliance on implicit encoding information is part of the reason
why encodings are such a mess now and so I just move on since it does no
harm.)
> This seems to only happen first time new file is written, no matter what
> command is put by qtikz (not only tikzpicture).
It's common to not add the BOM to existing documents that don't already
include it; if the original creator wanted the BOM to be implicit or
separately specified, then the next editor to touch the file should do the
same.
cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
--- End Message ---
