[OASIS Issue Tracker] Commented: (OFFICE-3263) ODF 1.0 Errata CD05changes font in Errata Part 1 section 2.1.1 instruction

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20146#action_20146 ] 

Dennis Hamilton commented on OFFICE-3263:
-----------------------------------------

I became curious around how this defect came into existence.

The OASIS Approved ODF 1.0 Errata 01 does not have the defect: Everything in the Errata item for section 2.1.1 is in a single font style.

The ODF 1.0 Errata CD04 Revision 7 has the element name in a monospace serif style (Courier New).

So does the version of that shows tracked changes between ODF 1.0 Errata CD04 and CD04 Revision 7.  But it doesn't show as being a change.

Where in my process did this come into existence?  I put on my surgical gloves and grabbed my forensic pathologist rotary saw, and this is what I found:

Because my available document comparison tool for .ODT files doesn't find difference internal to tables (it treats the one table as a mass replacement for another), I used a secret forensic trick to create the changed-tracked ODF 1.0 Errat CD04 Revision 7 and then the version with changes accepted that is balloting to become CD05 at this time.

I exported both ODF 1.0 Errata CD04 and ODF 1.0 Errata CD04-rev06 (ther one Svante prepared) as Microsoft Word 97/2000/XP (.doc) format from OO.o 3.2.0.

KEY POINT: 

Both .doc files have the defect - they show the element name in Courier New.  The .ODT files do not show that when viewed and the PDF prepared from the ODT file does not show that.  But the export to .DOC shows that.   This explains how that appeared as no difference in making the Tracked-Change DIFF in Microsoft Office Word and then returning the resulting .doc to OO.o to make an ODT. 

 It is also the case that, whatever happened in the change from ODT to DOC, the change is retained when the comparison-made DOC is converted back to ODT. 

Also, when the Word .doc files are brought back into OO.o exactly as they were exported, they return with the Courier New font showing, not the Arial.

I have no idea what happened here.



> ODF 1.0 Errata CD05 changes font in Errata Part 1 section 2.1.1 instruction
> ---------------------------------------------------------------------------
>
>                 Key: OFFICE-3263
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3263
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.0 Errata CD 5
>         Environment: This actually applies to ODF 1.0 Errata CD04-rev07 but we are letting it go to CD05 (unless the vote fails).
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>            Priority: Trivial
>             Fix For: ODF 1.0 Errata CD 6
>
>
> There is a disagreement between OASIS Approved ODF 1.0 Errata and the repetition of that Errata in Part 1 of ODF 1.0 Errata CD04-rev07
> In OASIS Approved ODF 1.0 Errata, the instruction for the only change in section 2.1.1 has replacement text 
> "All four subdocument root elements together contain the same information as an <office:document> element that contains the same subdocument root elements.
> The text is in the single normal-text font (Arial).  [There is no closing " in the instructions.]  
> In ODF 1.0 Errata CD04-rev07 (CD05) Part 1, the instruction is identical *except* that "<office:document>" is now in a monospace (Courier New) font style.
> Because we want to have Part 1 be identical to the OASIS Approved ODF 1.0 Errata table, we should remove that change.
> [Side Note: The Approved IS 26300:2006/COR1 does not have the change of font style in the instruction.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira