W3C home > Mailing lists > Public > www-validator-cvs@w3.org > October 2011

[Bug 10174] Bogus error reported for UTF-8 characters in larger documents

From: <bugzilla@jessica.w3.org>
Date: Sat, 29 Oct 2011 18:44:23 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1RKDtH-0006oB-9x@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10174

--- Comment #9 from Ville Skyttä <ville.skytta@iki.fi> 2011-10-29 18:44:22 UTC ---
(In reply to comment #7)

> And in reading the curl docs, I'm not sure why the --data-binary switch would
> be used in this case. The curl man page says, "To post data purely binary, you
> should instead use the --data-binary option.".

The curl man page is indeed pretty confusing wrt. what exactly --data does. 
But it does say this: "-d/--data is the same as --data-ascii." and then later
for --data-binary "Data is posted in a similar manner as --data-ascii does,
except that newlines are preserved and conversions are never done.".  I don't
think it's actually a matter of binary vs text, but rather posting as-is or
with some conversions.

Not sure what conversions they mean other than something related to newlines,
but I have verified locally with wireshark is that --data-binary POSTs files
as-is as I want it to (and like the validator does), and --data on the other
hand at least discards newlines, probably also leading whitespace (which would
mean problems with line and column numbers in results if validator did that).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 29 October 2011 18:44:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:47 UTC