[projectaon] Re: Highway Holocaust XML Changes
- From: Iain Smith <iainsmith@xxxxxxxxx>
- To: projectaon@xxxxxxxxxxxxx
- Date: Tue, 6 Dec 2005 00:10:39 -0800 (PST)
I'm currently hammering through the FW4 XML at the moment, that should take a
couple of
days. Once thats done I'll be able to start making global changes across all
four books,
which should reduce the need for constantly going back to make changes if I
find further
points in FW4.
I'll probably end up making a large list of global style issues as I go, this
may end up
being a useful contribution for a FW glossary of jargon/style.
Iain.
--- Jonathan Blake <blake.jon@xxxxxxxxx> wrote:
> [ ] Iain - please review changes to 01hh to ensure proper use of jargon
> [ ] Iain - update your working copy of 01hh.xml from CVS
> [ ] anyone - create Glossary of Jargon in Sanctum wiki
> <http://www.projectaon.org/en/Sanctum/Glossary>
>
> Good work on the XML. In the interest of density of communications, I
> mostly highlight problems in the following list, but want to send my
> compliments on the issues I don't highlight. I'm happy to have another
> XML worker on board.
>
> On 11/29/05, Iain Smith <iainsmith@xxxxxxxxx> wrote:
>
> > Changes from v00 to v01:
> >
> > Front Matter:
> >
> > o Game Rules - Formatted
> > - Replaced "pick a O" with "pick a 0" (errata)
>
> Is this really errata? In the Project Aon jargon, an "erratum" is an
> error from the printed editions of the books. An error introduced from
> scanning and proofreading is termed "non-erratum". This looks like a
> scanning error to me. In light of this, please review all issues
> listed to verify that we have are jargon straight (I don't have my
> hard copy handy). Anyone care to create a Glossary of Project Aon
> Jargon in the Sanctum?
>
> > o Equipment - Formatted
> > - Replaced "map of Central Texas" with "Map of Central Texas" and added
> > link
>
> Should this be an erratum since it is a change from the original books?
>
> > o Weapons - Formatted
> > - Changed weapon types to bold text
>
> The "strong" tag should be reserved for cases where an emphasis in the
> text is needed. This should be cleared up by using a table. I'm going
> to check in a version using a table (along with some other fixes that
> I noted). Please update your working copy.
>
> > sect16: Added illustration, corrected link sect201 -> sect291
> > sect18: corrected link sect320 --> sect329
> > sect28: corrected link sect04 --> sect64
> > sect31: 7.82mm --> 7.62mm
> > sect213: Added illustration, corrected link sect162 --> sect182
> > sect251: Corrected link sect120 -> sect126
> > sect257: Corrected link sect169 -> sect189
> > sect259: Corrected link sect167 -> sect187
> > sect266: Corrected link sect165 -> sect185
> > sect339: Corrected link sect296 -> sect298
>
> The scanner seemed to have a real problem with 6/9!
>
> > sect156: Added charcode for 'degrees'
> > sect270: Added charcode for 'degrees'
>
> We use named character entities. Actually, we should be using the
> "ch.deg" element. I don't think we've updated the XSL to handle this
> yet, though. Something else for me to do...
>
> > sect182: "Erath country" -> "Erath County" (errata) - This is an actual
> > place in
> Texas, so guess it was what JD intended.
> > sect270: "Comanche country" -> "Comanche County" (errata) - This is an
> > actual place
> in Texas, so guess it was what JD intended.
>
> Excellent catches.
>
> --
> Jon
>
>
__________________________________________
Yahoo! DSL ? Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
Other related posts: