Re: Unicode UTF-8 Compatible Version of Gutcheck
Walt Farrell <[email protected]> Thu, 26 Feb 2015 14:07:08 -0500
| Newsgroups | gmane.culture.literature.e-books.gutenberg.volunteers |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============4323929477512578677==
Content-Type: multipart/alternative;
boundary="------------040501030705020905050800"
This is a multi-part message in MIME format.
--------------040501030705020905050800
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
On 2/26/2015 1:30 PM, James Adcock wrote:
> Message
>
> Huh. Not obvious to me what he is doing in bookloupe.
>
Bookloupe was intended to be the UTF-8-aware replacement for gutcheck.
However, if I remember correctly, at the time the author wrote it PG
wanted it to report all the same errors as gutcheck would or they would
not agree to switch over to using it.
So it ended up only partially UTF-8-aware, as with full UTF-8 awareness
it wouldn't report some errors that gutcheck would have reported. But as
far as I know Bookloupe is what PG now uses, not gutcheck.
--
Walt
--------------040501030705020905050800
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
<div class=3D"moz-cite-prefix">On 2/26/2015 1:30 PM, James Adcock
wrote:<br>
</div>
<blockquote cite=3D"mid:BLU404-EAS3241334BD86A390EBC1A34AE140-MsuGFMq8XAE@public.gmane.org=
"
type=3D"cite">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered
medium)">
<title>Message</title>
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Huh.=C2=A0 N=
ot
obvious to me what he is doing in bookloupe.</span><br>
</p>
</div>
</blockquote>
<br>
Bookloupe was intended to be the UTF-8-aware replacement for
gutcheck. However, if I remember correctly, at the time the author
wrote it PG wanted it to report all the same errors as gutcheck
would or they would not agree to switch over to using it.<br>
<br>
So it ended up only partially UTF-8-aware, as with full UTF-8
awareness it wouldn't report some errors that gutcheck would have
reported. But as far as I know Bookloupe is what PG now uses, not
gutcheck. <br>
<br>
-- <br>
Walt<br>
</body>
</html>
--------------040501030705020905050800--
--===============4323929477512578677==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ3V0dm9sLWQg
bWFpbGluZyBsaXN0Cmd1dHZvbC1kQGxpc3RzLnBnbGFmLm9yZwpodHRwOi8vbGlzdHMucGdsYWYu
b3JnL21haWxtYW4vbGlzdGluZm8vZ3V0dm9sLWQK
--===============4323929477512578677==--