GNU bug report logs -
#29606
Command 'fold' dangerous with utf-8 input
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#29606: Command 'fold' dangerous with utf-8 input
which was filed against the coreutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 29606 <at> debbugs.gnu.org.
--
29606: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29606
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hello Mark,
First,
thank you for taking the time and effort
to test our development snapshot, and reporting results back.
This kind of feedback is critical in getting multibyte support ready.
Second,
I can confirm the behavior you are observing, reproduced here
with 'od' for easier output:
## POSIX single-byte locale:
$ echo "ß" | LC_ALL=C src/fold --bytes --width 1 | od -tc -An
303 \n 237 \n
$ echo "ß" | LC_ALL=C src/fold --width 1 | od -tc -An
303 \n 237 \n
## UTF8 locale:
$ echo "ß" | LC_ALL=en_CA.UTF-8 src/fold --bytes --width 1 | od -tc -An
303 237 \n
$ echo "ß" | LC_ALL=en_CA.UTF-8 src/fold --width 1 | od -tc -An
303 237 \n
On 2017-12-08 05:04 AM, Mark Roberts wrote:
> When --bytes is not specified, the program treats '\b', '\r' and '\t'
> specially. It assumes a tab width of eight (compile-time #define) and
> attempts to keep track of what the output will look like.
>
> This is absolutely not what I expected.
That is correct, and I share your sentiment: it also took me some time
to try and track down why it behaves this way, and whether it's by
design or a bug.
> But of course, when the program
> was first written, the words byte and character meant the same thing for
> printable characters. Printable bytes.
The reasoning for this behavior is explained in the OpenGroup's POSIX
standard page for fold, in the "RATIONAL" section:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/fold.html#tag_20_48_18
There, it is made clear:
"Historical versions of the fold utility assumed 1 byte was one
character and occupied one column position when written out. This is
no longer always true.
[....]
Note that although the width for the -b option is in bytes, a line is
never split in the middle of a character."
Therefore, the current implementation (of the development version) is
correct.
> I will attempt to suggest an improved text for the man-page so that
> others will not be surprised.
I agree that once multibyte support is added to fold(1), the man pages,
the help screen and texi manual must be updated to clearly
indicate the "-b/--bytes" only applies to \b \t \r and never to
multibyte characters.
If you find the time to send such a patch - great!
If not, I will add it sooner or later (hopefully sooner).
As such I'm closing this bug report, but further discussion (and
patches) are welcomed by replying to this thread.
regards,
- assaf
[Message part 3 (message/rfc822, inline)]
Dear maintainers,
I am using fold version 8.13 on a Debian 3.2.93-1
> cat filename | fold
If 'filename' contains utf8 characters consisting of more than one byte,
fold will consider breaking the line inside such a character. There is no
option to stop it doing that.
Except, of course "-s": break at spaces. But that may not be what the user
wants.
According to man-page, it counts columns by default, not bytes. This seems
not to be true. The switch "-b": count bytes, has no influence on the
output in my test case.
How to fix this?
I presume that either (1) the default behavior (counting columns) is not
what I expect, namely to count characters instead of bytes. This would
have to be clarified in man-page.
or (2) that the default isn't what the man-page says it is: possibly the
default set in the code is to count bytes. This would be an error.
or (3) that 'fold' fails to read my "LANG" environment variable which
clearly states a UTF-8 locale. This, in 2017, is an error.
Please write back to mroberts <at> rapid-arts-movement.de if you need example
data or clarifications.
Thank you,
Mark Roberts
This bug report was last modified 7 years and 169 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.