Re: Unicode UTF-8 Compatible Version of Gutcheck
"Al Haines" <[email protected]> Thu, 26 Feb 2015 16:12:58 -0800
| Newsgroups | gmane.culture.literature.e-books.gutenberg.volunteers |
|---|---|
| Message-ID | <AAD23070CBCA48E79E3F44CFD772E9C7@ahainesPC> |
This is a multi-part message in MIME format.
--===============8683347451724209307==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0005_01D051DF.167CF830"
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01D051DF.167CF830
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Actually, the WWers pretty much have had to use both since PG decided to =
accept only a single text file of whatever character set was needed to =
express the source material. =20
=20
To use 48325 as an example, Gutcheck sees this line (line 27 of the =
submitted file):
=20
_=E2=80=9CTHE WIDE, WIDE WORLD,=E2=80=9D =E2=80=9CQUEECHY,=E2=80=9D
=20
like this:
=20
_=C3=A2=E2=82=AC=C5=93THE WIDE, WIDE WORLD,=C3=A2=E2=82=AC=C2=9D =
=C3=A2=E2=82=AC=C5=93QUEECHY,=C3=A2=E2=82=AC=C2=9D
=20
resulting in a "missing space" warning. If the line is too long, =
Gutcheck will also issue a "line too long" warning.
=20
Bookloupe sees the line properly, but doesn't/can't check the quotes. =20
=20
Gutspell sees the strange characters as part of the word, and flags the =
word as a misspell. This isn't limited to quotes--words adjacent to, or =
that contain, Unicode em-dashes, apostrophes, or ellipses cause the same =
problem.
=20
To check quotes, and to have Gutspell work properly, the WWers have to =
use Unitame to generate a temporary Latin1 text file from the UTF8 file, =
and Gutcheck/Jeebies/Gutspell the Latin1 file.
=20
=20
As a WWer, I don't mind UTF8 text files that contain necessary Unicode =
characters, e.g. Greek, etc, but UTF8 text files that contain only =
Unicode quotes, apostrophes, em-dashes, and similar NON-necessary =
Unicode characters, are just a nuisance. If a text file doesn't need =
Unicode characters, submit a Latin1 text file. It's a lot easier on the =
WWers.
=20
=20
Al
=20
=20
-----Original Message-----
From: gutvol-d [mailto:gutvol-d-bounces-4LCm/o+qPMZ96Xl/[email protected]] On Behalf Of =
Walt Farrell
Sent: Thursday, February 26, 2015 11:07 AM
To: Project Gutenberg Volunteer Discussion
Subject: Re: [gutvol-d] Unicode UTF-8 Compatible Version of Gutcheck
On 2/26/2015 1:30 PM, James Adcock wrote:
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.=20
--=20
Walt
------=_NextPart_000_0005_01D051DF.167CF830
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dutf-8">
<TITLE>Message</TITLE>
<META name=3DGENERATOR content=3D"MSHTML 10.00.9200.17229"></HEAD>
<BODY bgColor=3D#ffffff text=3D#000000>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015>Actually, the WWers pretty much have had =
to use=20
both since PG decided to accept only a single text file of whatever =
character=20
set was needed to express the source material. =
</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT><FONT color=3D#0000ff size=3D2=20
face=3DArial><SPAN class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN =
class=3D535533523-26022015>To use=20
48325 as an example, </SPAN></FONT><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D535533523-26022015>Gutcheck sees this line (line 27 of the =
submitted=20
file):</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015> _=E2=80=9CTHE WIDE, WIDE =
WORLD,=E2=80=9D=20
=E2=80=9CQUEECHY,=E2=80=9D</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN =
class=3D535533523-26022015>like=20
this:</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015> _=C3=A2=E2=82=AC=C5=93THE =
WIDE, WIDE WORLD,=C3=A2=E2=82=AC=C2=9D=20
=C3=A2=E2=82=AC=C5=93QUEECHY,=C3=A2=E2=82=AC=C2=9D</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015>resulting in a "missing space" warning. =
If the=20
line is too long, Gutcheck will also issue a "line too long"=20
warning.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015>Bookloupe sees the line properly, =
but=20
doesn't/can't check the quotes. </SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015>Gutspell sees the strange characters as part =
of the=20
word, and flags the word as a misspell. This isn't limited to=20
quotes--words adjacent to, or that contain, Unicode em-dashes,=20
apostrophes, or ellipses cause the same =
problem.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN =
class=3D535533523-26022015>To=20
check quotes, and to have Gutspell work properly, the WWers have to use =
Unitame=20
to generate a temporary Latin1 text file from the UTF8 file, and=20
Gutcheck/Jeebies/Gutspell the Latin1 file.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN =
class=3D535533523-26022015>As a=20
WWer, I don't mind UTF8 text files that contain necessary Unicode =
characters,=20
e.g. Greek, etc, but UTF8 text files that contain only Unicode quotes,=20
apostrophes, em-dashes, and similar NON-necessary Unicode characters, =
are just a=20
nuisance. If a text file doesn't need Unicode characters, submit a =
Latin1=20
text file. It's a lot easier on the WWers.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015></SPAN></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial><SPAN=20
class=3D535533523-26022015>Al</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial></FONT> </DIV>
<DIV><FONT color=3D#0000ff size=3D2 face=3DArial></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV lang=3Den-us class=3DOutlookMessageHeader dir=3Dltr =
align=3Dleft><FONT size=3D2=20
face=3DTahoma>-----Original Message-----<BR><B>From:</B> gutvol-d=20
[mailto:gutvol-d-bounces-4LCm/o+qPMZ96Xl/[email protected]] <B>On Behalf Of </B>Walt=20
Farrell<BR><B>Sent:</B> Thursday, February 26, 2015 11:07 =
AM<BR><B>To:</B>=20
Project Gutenberg Volunteer Discussion<BR><B>Subject:</B> Re: =
[gutvol-d]=20
Unicode UTF-8 Compatible Version of Gutcheck<BR><BR></FONT></DIV>
<DIV class=3Dmoz-cite-prefix>On 2/26/2015 1:30 PM, James Adcock =
wrote:<BR></DIV>
<BLOCKQUOTE cite=3Dmid:BLU404-EAS3241334BD86A390EBC1A34AE140-MsuGFMq8XAE@public.gmane.org=20
type=3D"cite">
<META name=3DGenerator=20
content=3D"Microsoft Word 15 (filtered medium)">
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; =
}
P.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
LI.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
DIV.MsoNormal {
FONT-SIZE: 11pt; FONT-FAMILY: "Calibri",sans-serif; MARGIN: 0in 0in 0pt
}
A:link {
COLOR: #0563c1; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: #0563c1; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: #954f72; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: #954f72; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri",sans-serif; COLOR: windowtext; mso-style-type: =
personal
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri",sans-serif; COLOR: #1f497d; mso-style-type: =
personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
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=3DWordSection1>
<P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Huh. Not =
obvious to me=20
what he is doing in =
bookloupe.</SPAN><BR></P></DIV></BLOCKQUOTE><BR>Bookloupe=20
was intended to be the UTF-8-aware replacement for gutcheck. However, =
if I=20
remember correctly, at the time the author wrote it PG wanted it to =
report all=20
the same errors as gutcheck would or they would not agree to switch =
over to=20
using it.<BR><BR>So it ended up only partially UTF-8-aware, as with =
full UTF-8=20
awareness it wouldn't report some errors that gutcheck would have =
reported.=20
But as far as I know Bookloupe is what PG now uses, not gutcheck. =
<BR><BR>--=20
<BR>Walt<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0005_01D051DF.167CF830--
--===============8683347451724209307==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ3V0dm9sLWQg
bWFpbGluZyBsaXN0Cmd1dHZvbC1kQGxpc3RzLnBnbGFmLm9yZwpodHRwOi8vbGlzdHMucGdsYWYu
b3JnL21haWxtYW4vbGlzdGluZm8vZ3V0dm9sLWQK
--===============8683347451724209307==--