W3C home > Mailing lists > Public > www-math@w3.org > December 2000

Re: minor comments for CR-MathML2-20001113

From: David Carlisle <davidc@nag.co.uk>
Date: Thu, 14 Dec 2000 10:35:54 GMT
Message-Id: <200012141035.KAA22191@trowbridge.nag.co.uk>
To: lesch@w3.org
CC: www-math@w3.org

Once again, thanks for your detailed reading!
 

> Globally, when talking about a specific group, "Working Group" can be 
> capitalized.

done.

> People are asking for smaller W3C specs.
not done today, too close to finalising next draft, I fear.

> In April [2], when the Last Call Working Draft was proofed, image
> backgrounds came up. They are still transparent, and should probably
> be white, so that readers with user style sheets set to a dark
> background can read them. (This is a bigger job than I would volunteer
> for, but maybe the comment will help.)

Sorry, missed this. This is in fact a very easy change to make, all the
images are generated afresh (from the tex source in the alt attribute)
each time the spec is regenerated so this just amounts to removing
-transparency '#FFFFFF' from the rendereq script in the CVS sources of
the spec at the W3C.  (I've done this and will regenerate the spec later
today.  I did try forcing my browser to use yellow text on a dark blue
background, and I agree the images don't look too good then.

(This is the mathml example images, the character pngs in chapter 6 were
already white background)


> TOC - G, 3.2.2 par. 5, "Next" link in Appendix F, and heading for Appendix G
> Sample CSS Stylesheet
> Sample CSS Style Sheet

(No need to list all the occurrences, all the links are automatically
generated from the same text). Fixed


> 1.2.1 last par.
> from March 1997 to the June 1998
> from March 1997 to June 1998
fixed

> 1.2.2 par. 6
> use of the alt
> use of the alt attribute
fixed

> 1.2.3 par. 2
> on to commerce:
> on to commerce.
fixed

> 1.3.1 par. 1
> well will of necessity
> will of necessity

This is OK, I think, context is

... enough information to do  all  these  tasks  well  
will of  necessity
 
perhaps a comma after well ?


> In 1.3.2.2, you might link to [XML] the first time it is mentioned.
done.


> 2.3.3 last par.
> MathML Presentation annotation
> MathML presentation annotation

Not done, presentation isn't an adjective of annotation here, but rather
MathML Presentation is the capitalised name title of that part of MathML.

> 
> 2.4.1 par. 2
> Schema
> schema (twice)
fixed
 
> 2.4.1 last par.
> Schema
> schema
fixed
 
> 2.4.2 par. 1
> Specification
> specification
done
 
> 2.4.4 par. 3
> double quotes (") or single quotes (')
> quotation marks (") or apostrophes (')
> (see http://www.unicode.org/charts/PDF/U0000.pdf)
Grr not done the use of ' here is as a single quote
not as an apostrophe. Even though the unicode apostrope character is
used rather than one of the single quote characters.
The use of this character as the single quote character predates
the addition of specific quote characters in later encodings such as
unicode, as is recognsed in its older unicode name:
0027;APOSTROPHE;Po;0;ON;;;;;N;APOSTROPHE-QUOTE;;;;



 
> 2.4.4.3, Order of processing attributes versus style sheets
> (These could be switched to follow CSS2 cascading order and to 
> improve accessibility.)
> * From a style sheet from the reader: styles which are declared `important'
> * From a style sheet from the author: styles which are declared `important'
> 
> from the same section:
>      Note that the order of the changes derived from CSS style
>      sheets is specified by CSS itself.
> (Because CSS1 and CSS2 have different cascading orders, you might say
> which CSS Level applies.)

Not done this morning as this isn't just an editorial issue, it affects
the spec so I'll wait for comments from other WG members.
I thought we intended to follow CSS2.


> 
> 2.4.4.4 par. 5
> single or double quotes
> apostrophes or quotation marks

as above.
 
> 2.4.4.5 last par.
> Schema
> schema
done

> 
> 2.4.5 par. 1
> style-sheet
> style sheet
fixed
 
> 2.4.5 par. 2
> accept xlink:href attribute
> accept the xlink:href attribute
done
 
> 2.4.5 par. 3
> All MathML elements also accepts
> All MathML elements also accept
done
 
> 2.4.5 par. 3
> for use in parallel markup Section 5.3 [Parallel Markup].
> for use in parallel markup (Section 5.3 [Parallel Markup]).
done





> 3.1.5 last par.
> the Unicode Bidirectional Algorithm
> the Unicode bidirectional algorithm
done
 
> 3.2.1 par. 2
> MathML Characters
> (Either make each occurrence capitalized, or lowercase. I'd suggest lowercase.)

done (lowercase)
 
> 3.2.2.1 second to last par.
> an non-ASCII
> a non-ASCII
done
 
> 3.2.8.2 last par.
> `double quote'
> `quotation mark'
> also:
>      For example, <ms>double quote is"</ms> might be rendered
>      as "double quote is \"".
> becomes:
>      For example, <ms>quotation mark is"</ms> might be rendered
>      as "quotation mark is \"".
unchanged. as before, I'm resisting the assumption that "quotation marks"
are double.

 
> 3.3.1.3 par. 1
> Sub-Expressions
> Sub-expressions (not sure there)
done
 
> 3.3.6.3 par. 3
>      The lspace attribute refers to the amount of space
>      between the left edge of a bounding box and the start of
>      the rendering of its contents' bounding box actually
>      begins.
> (seems to be an incomplete sentence. Maybe:)
>      The lspace attribute refers to the amount of space
>      between the left edge of a bounding box and the start of
>      the rendering of its contents' bounding box.

done. (deleted "actually begins")
 
> 3.5.1.2, 6th to last par.
>      For example, if a table had five columns and we wanted
>      lines between the columns, but no frame, then we would
>      have to write columnlines="none solid solid solid solid
>      none". By separating the frame from the internal lines,
>      we only need to write columnlines="solid".
> (To remove first person which is hard to translate [3], could read:)
>      For example, if a table had five columns and lines but
>      no frames were desired between the columns, then
>      columnlines="none solid solid solid solid none" would be
>      necessary. If the frame is separated from the internal
>      lines, only columnlines="solid" is needed.

done, but we don't want to imply we could have frames between the
columns, so: 
For example, if a table had five columns and it was desired to have
no frame around the table but to have lines between the columns, then
<code>columnlines="none solid solid solid solid none"</code>
would be necessary. If the frame is separated from the internal
lines, only <code>columnlines="solid"</code> is needed.</p>

 
> 3.5.5.7 par. 3
> + represents
> '+' represents

Not done, it would be confusing as the syntax uses quoted forms '('
and unquoted forms: ( and it is an unquoted (unapostroped:-) +
that is being used here.

 
> '{' and '}' represent literal braces; and ( and ) are used
> '{' and '}' represent literal braces; and '(' and ')' are used

as above, the fact that the second sort of braces are not quoted
is the point of this comment.

 
> 3.5.5.9 par. 2
> a list of boolean values, each boolean
> a list of boolean values. Each boolean
The sentence as it stands is a bit long, but I think this change would
alter the meaning  so i left it as it was.



that gets to the end of C3. May do some more later

David

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp
Received on Thursday, 14 December 2000 05:36:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 20 February 2010 06:12:50 GMT