- From: CE Whitehead <cewcathar@hotmail.com>
- Date: Tue, 6 Oct 2009 20:26:08 -0400
- To: <ishida@w3.org>, <www-international@w3.org>
- Message-ID: <BLU109-W2421493EBCA4F8F133704EB3CD0@phx.gbl>
I have one more proofreading comment for:
"Requirements for String Identity Matching and String Indexing"
(W3C Working Group Note 15 September 2009).
3.3; Sentence 3
"It may also provide a bit more time, in that we are just defining what might happen naturally anyway instead of having to fight uphill from day one."
{ COMMENT: wordy:
>= "By doing so we are defining what might happen naturally anyway . . ."
}
Best,
--C. E. Whitehead
cewcathar@hotmail.com
* * *
From: cewcathar@hotmail.com
To: ishida@w3.org; www-international@w3.org
Date: Mon, 5 Oct 2009 15:37:22 -0400
Subject: RE: New Working Group Note: Requirements for String Identity Matching and String Indexing
Hi!
My initial comments on:
"Requirements for String Identity Matching and String Indexing"
http://www.w3.org/TR/charreq/
are on proofreading!
2.3 PAR 2, last sentence
"A process shall not assume that the interpretations of two canonical-equivalent character sequences are distinct. Additions may include some presentation forms."
{CORRECTION:
"canonical-equivalent"
>= "canonically-equivalent"
See text at: http://en.wikipedia.org/wiki/Unicode_equivalence for an example of the use of "canonically-equivalent"}
* * *
2.10, PAR 2, first bullet
"It is a prerequisite for be conservative in what you send "
{ CORRECTION
>= "It is prerequisite to being conservative in what you send."
Alternately,
>= "It is prerequisite to one's being in what is sent."
}
* * *
3.2, PAR 1, last sentence
"As an example, it could be required that text transmitted via certain protocols, or text exposed in certain APIs, is normalized."
{COMMENTS: ?? You used the indicative ("is normalized"), and not the subjunctive, which may be o.k. in the U.K. but in the U.S. the correct grammar is
"is normalized"
>= ?? "be normalized."
Also I would like some examples of the protocols here! }
* * *
3.2, last PAR, last sentence
"Such a transfer is indeed highly desirable in many cases, because to avoid generating unnormalized data is in many cases easier than to normalize such data later."
{CORRECTION/COMMENT: broken verb predicate (I think it's better to keep these together when you can):
>="Such a transfer is indeed highly desirable in many cases, because it is in many cases easier to avoid generating unnormalized data than it is to normalize such data later."
}
* * *
4.4
{ COMMENT/CORRECTION?? : I think I'd prefer
>= "sub-elements"
and
>= "sub-element"
[that is, I think this word needs a hyphen--but some people don't hyphenate--IBM, for example;
see: http://www.google.com/search?hl=fr&source=hp&q=sub-element&btnG=Recherche+Google&lr=&aq=f&oq=!] }
* * *
I'll follow with a few questions/comments on the contents shortly!
Best,
C. E. Whitehead
cewcathar@hotmail.com
> From: ishida@w3.org
> To: www-international@w3.org
> Date: Thu, 1 Oct 2009 15:38:40 +0100
> Subject: New Working Group Note: Requirements for String Identity Matching and String Indexing
>
> On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note.
>
> http://www.w3.org/TR/charreq/
>
> This document was published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication.
>
> The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing.
>
> Editor: Martin Dürst.
>
>
--_3d99457e-2f13-49b3-b6ef-78a0a2b1655f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR>I have one more proofreading comment for:<BR>
"Requirements for String Identity Matching and String Indexing"<BR>(W3C Working Group Note 15 September 2009).<BR> <BR>
3.3; Sentence 3<BR>
"It may also provide a bit more time, in that we are just defining what might happen naturally anyway instead of having to fight uphill from day one."<BR>
{ COMMENT: wordy:<BR>>= "By doing so we are defining what might happen naturally anyway . . ."<BR>
}<BR>
Best,<BR>
--C. E. Whitehead<BR>
<A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A><BR>* * *<BR> <BR>
<HR id=stopSpelling>
From: cewcathar@hotmail.com<BR>To: ishida@w3.org; www-international@w3.org<BR>Date: Mon, 5 Oct 2009 15:37:22 -0400<BR>Subject: RE: New Working Group Note: Requirements for String Identity Matching and String Indexing<BR><BR>
<STYLE>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Verdana;}
</STYLE>
Hi!<BR> <BR>My initial comments on:<BR>"Requirements for String Identity Matching and String Indexing"<BR>http://www.w3.org/TR/charreq/<BR>are on proofreading!<BR><BR>2.3 PAR 2, last sentence<BR><BR>"A process shall not assume that the interpretations of two canonical-equivalent character sequences are distinct. Additions may include some presentation forms."<BR><BR>{CORRECTION: <BR>"canonical-equivalent" <BR>>= "canonically-equivalent"<BR>See text at: <A href="http://en.wikipedia.org/wiki/Unicode_equivalence">http://en.wikipedia.org/wiki/Unicode_equivalence</A> for an example of the use of "canonically-equivalent"}<BR><BR>* * *<BR><BR>2.10, PAR 2, first bullet<BR><BR>"It is a prerequisite for be conservative in what you send "<BR>{ CORRECTION<BR>>= "It is prerequisite to being conservative in what you send."<BR><BR>Alternately,<BR><BR>>= "It is prerequisite to one's being in what is sent."<BR>}<BR><BR>* * *<BR><BR>3.2, PAR 1, last sentence<BR><BR>"As an example, it could be required that text transmitted via certain protocols, or text exposed in certain APIs, is normalized."<BR><BR>{COMMENTS: ?? You used the indicative ("is normalized"), and not the subjunctive, which may be o.k. in the U.K. but in the U.S. the correct grammar is <BR><BR>"is normalized" <BR>>= ?? "be normalized."<BR>Also I would like some examples of the protocols here! }<BR><BR>* * *<BR><BR>3.2, last PAR, last sentence<BR><BR>"Such a transfer is indeed highly desirable in many cases, because to avoid generating unnormalized data is in many cases easier than to normalize such data later."<BR>{CORRECTION/COMMENT: broken verb predicate (I think it's better to keep these together when you can): <BR>>="Such a transfer is indeed highly desirable in many cases, because it is in many cases easier to avoid generating unnormalized data than it is to normalize such data later."<BR>}<BR>* * *<BR>4.4<BR><BR>{ COMMENT/CORRECTION?? : I think I'd prefer <BR>>= "sub-elements"<BR>and <BR>>= "sub-element"<BR>[that is, I think this word needs a hyphen--but some people don't hyphenate--IBM, for example;<BR>see: <A href="http://www.google.com/search?hl=fr&source=hp&q=sub-element&btnG=Recherche+Google&lr=&aq=f&oq">http://www.google.com/search?hl=fr&source=hp&q=sub-element&btnG=Recherche+Google&lr=&aq=f&oq</A>=!] }<BR>* * *<BR><BR>I'll follow with a few questions/comments on the contents shortly!<BR><BR>Best,<BR>C. E. Whitehead<BR><A href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</A><BR><BR> <BR>> From: ishida@w3.org<BR>> To: www-international@w3.org<BR>> Date: Thu, 1 Oct 2009 15:38:40 +0100<BR>> Subject: New Working Group Note: Requirements for String Identity Matching and String Indexing<BR>> <BR>> On 15th September, the Internationalization Core Working Group published Requirements for String Identity Matching and String Indexing as a Working Group Note.<BR>> <BR>> http://www.w3.org/TR/charreq/<BR>> <BR>> This document was published as a Working Group note in order to capture and preserve historical information. It contains requirements elaborated in 1998 for aspects of the character model for W3C specifications. It was developed and extensively reviewed by the Internationalization Working Group, but never progressed beyond Working Draft status. For this publication, the wording of the 1998 version remains unchanged (except for correction of a small number of typographic errors), but the links to references have been updated prior to this publication.<BR>> <BR>> The document describes requirements for some important aspects of the character model for W3C specifications. The two aspects discussed are string identity matching and string indexing.<BR>> <BR>> Editor: Martin Dürst.<BR>> <BR>> <BR><BR> </body>
</html>
--_3d99457e-2f13-49b3-b6ef-78a0a2b1655f_--
Received on Wednesday, 7 October 2009 00:26:42 UTC