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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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


Subject: Status of Committee Specification Draft 02 -- earlier (Re: [office] Agenda for ODF TC Teleconference Monday, 17 August 2020)


Hi Patrick, Hi Francis,

I have two unanswered questions myself, I might have asked before:
  1. Is our "ISO Keyword" highlighting by character style mandatory or optional to become an ISO standard?
    You sent me an ISO reference:Â
    https://isotc.iso.org/livelink/livelink?func=ll&objid=4230450&objAction=browse&sort=name&viewType=1
    There are 150MB of 84 files with additional referencesÂto other sites.
    I fullyÂtrust you, Patrick and Francis, as our ISO experts to clarify this issue. :-)

    We surely do not want to create later an ODF 1.3 corrigenda on ISO level to solve such a problem.
    I only wrote a very tiny ISO corrigendum for ODF once for Sun, it took me a full week of stubborn copy & paste: stating every erroneous occurrence by page number with before and after state.Â
    If there is any doubt that the styling is optional, we need to fix this before submitting ODF 1.3 to ISO.
  2. How are all the informative parts identified in ODF 1.3?Â
    Is the following covering all informative parts?
    1. Every informative chapterÂisÂcontaining a substring: "(Non normative)"
    2. In addition, within a chapter may occur informative parts - as explained in Terminology:
      "Text with a gray background color which is contained in boxes is informative."
In any case, all "ISO Keyword" changes should be done (semi-)automated from the XML side and not by reading and manual editing.Â
The latter is obviously too error-prone and time consuming.

Your question I have answered below, Patrick.

Am Mo., 17. Aug. 2020 um 03:17ÂUhr schrieb Patrick Durusau <patrick@durusau.net>:
....

4. Status of Committee Specification Draft 02? It isn't clear who has the editing token. We need a final version for voting.


Status of Committee Specification Draft 02. There are only editorial changes on, which might be readily integratedÂat the start of our call.

The latest reviewed state of ODF 1.3 CS02 deliverables are within our TC GitHub repository:
Ongoing/pending reviews:
My general editorial ToDo list:
As you might notice from the checkboxes, I was not able to work as I hoped I could at the weekend.
Until our call, I am in possession of the "virtual editor token(s)" - created for each unmergable ODT documents - please tell me if you need one or a fix.ÂÂ

Talk to you soon,
Svante
Â
...


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