OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (MQTT-499) Changes made by TC Admin in CSD01

    [ https://issues.oasis-open.org/browse/MQTT-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67141#comment-67141 ] 

Ken Borgendale commented on MQTT-499:

For the next review we will create a document with exactly the change indicators we want to go out for review in the document, even if this means putting out two documents for the TC to review.

The subsection of Appendix C did not have a number, but I have changed this to make it section c.1

The arrow characters used in section 2.1.1 were from the Unicode wingding range (\uF0Ex) and in Arial font.  These characters are not in the Arial font but most viewing environments extend the font.  I have replaced them with characters from the Unicode Arrows range (\u219x).which are in most large character set fonts.  

I was unable to see the problem with the hyperlink references in chapter 5 when I converted to html. 

My conversion to html does not show any broken links using the w3.org validator, but this is after cross references were changed to hyperlinks.

The problem of broken links giving "Error! Reference source not found" was noted in MQTT-493.  For me these only showed up in the PDF conversion.  In any case, I also converted all of the word cross references to hyperlinks and found a few more broken references in the process.

Whether the CJK Extension B character \u2A6D4 displays correctly depends on your font environment.  I see this in the html in all of my browsers, but it depends on what fonts you have installed.  I do not see the character in the Adobe PDF viewer but see it in other PDF viewers.  I assume from this that any non base plain character is likely to have this problem, but this is exactly what the example is trying to show. 

> Changes made by TC Admin in CSD01
> ---------------------------------
>                 Key: MQTT-499
>                 URL: https://issues.oasis-open.org/browse/MQTT-499
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Task
>          Components: edits
>    Affects Versions: 5, wd16
>            Reporter: Ken Borgendale
>            Assignee: Ken Borgendale
>            Priority: Minor
>             Fix For: 5, wd16
> A number of changes were made to the document by Oasis TC Admin when creating CSD01 from wd15.  Preserve these changes.
> - Changes to the preface text and notices
> - Change to number lines starting with section 1
> - Remove the title and TOC from the TOC
> - Add section 1.0
> - Add and remove blank lines for consistency
> This issue is a record of the reason for the change to the working draft.  These changes are made without change flags as they do not represent any change between CSD01 and wd16.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]