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: [OASIS Issue Tracker] Commented: (OFFICE-1381) Public Comment:Naughty words and phrases (ODF all versions)



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

Patrick Durusau commented on OFFICE-1381:
-----------------------------------------

Commenting here to track my changes:

MB: "usually" appears only within notes, which seems to be okay

PLD: Yes, usually is only in non-normative text. 

MB: "typically" does not appear 

PLD: I corrected all of these in an earlier pass.

MB: "in general"/"generally" appears two or three times. I don't consider these occurrences to be problematic. 

PLD: The term "generally" occurs once and then in normative text of 7.1 speaking of indexes, thus: "An index generally contains a sorted list of all items of a certain types, where the sorting  and the type of items are determined by the specific type of index."

The issue is that it is normative text and we should be simply stating what indexes contain as a matter of fact, not in general. Therefore:

"An index contains a sorted list of all items of certain types, where the sorting  and the type of items are determined by the specific type of index."

The phrase "in general" has two cases: 

18.214 - "In general, if r is the radius of the polygon, and s is the sharpness, the inner corners a located on a ellipse that's radius is r(100-s)/100." Same issue as before, should simply state the facts, thus:

"If r is the radius of the polygon, and s is the sharpness, the inner corners a located on a ellipse that's radius is r(100-s)/100."

Second case:

19.257 - "In general such a drawing object is allowed to leave its layout environment in the other (non text flow) directions." Same issue as before, suggest:

"A drawing object is allowed to leave its layout environment in the other (non text flow) directions."

MB: "similar to" appears one time. I don't consider that occurrences to be problematic. 

PLD: 18.137, made the paragraph in question a note so non-normative. 

MB: "most" still occurs a few times. I don't consider these occurrences to be problematic. 

PLD: Most non-normative but,

6.1 "most commonly" -> commonly - most doesn't really add anything

6.4.13 I think is defensive construction.

6.6.7 "most recently used" -> the last used table

6.7.12 "most recent data" -> "last data"

9.3.16, I have a question about "Most drawing objects have four standard glue points at the four edges of the object." But of most drawing objects, only draw:rect reliably has four edges. Yes? 

9.4.1, "...with the first child element being the most preferred." -> "with the first child element being preferred." (Still leaves an issue with what do we mean by preferred but does fix the original issue.)

18.190, the four glue points comes up again: "The ids 0 to 3 are reserved for the 4 standard glue points that most drawing objects have." 

The rest of "most" seems to be descriptive, the "most superior level," etc. so clear from context. 


MB: "may only" needs some clean-up, but must not simply be replaced by "shall not". 

PLD: So you are going to do "may only"?

MB: "even" still occurs a few times. While most usages appear to be okay, there may be a few where "even" can be omitted.

PLD: 

6.5.9 "The <text:meta-field> element may contain any paragraph content, even another <text:meta-field> element." -> "including another"

18.591: "A differentiation between absolute and relative addresses is not possible, that is, the addresses are interpreted as absolute addresses even if they contain dollar signs." 

Just say it: "A differentiation between absolute and relative addresses is not possible, that is, the addresses are interpreted as absolute addresses."

(full stop, what is unclear about that?)

18.795: "If no value is specified, the current date is assumed, even if the field is marked fixed." 

Suggest: "If no value is specified, whether the field is marked as fixed or not, the current date is assumed."

18.798 "converts even system specific" -> "converts system specific"

18.818 "If true, the given heading will not be numbered, even if an explicit list-style is given" -> In listing values I need to consider how to say this. 

18.883 " If no value is specified, the current time is assumed, even if the field is marked fixed." Replace with: " If no value is specified, whether the field is marked as fixed or not, the current time is assumed."

MB: "then": I don't understand that issue with "then". 

For example: "If a child node's smil:begin attribute has the value indefinite, then the execution is stalled until the user advances the slideshow by a mouse or key interaction."

Rather than the more declarative: "If a child node's smil:begin attribute has the value indefinite, execution is stalled until the user advances the slideshow by a mouse or key interaction."

Note the deletion of the "then the."

PLD: I will start here tomorrow (7August2009)

MB:  "might" still occurs. It could be replaced with "may", except in the legal disclaimer that is provided by OASIS and must not be changed. 

MB: "must" still occurs. Most occurrences can be replaced with "shall", but some need to be changed differently. 

MB:  "possible" still occurs. Most occurrences seem to be okay, but some may be changed. 

MB: "in terms of" still occurs, and me be replaced with "as" or something similar.


> Public Comment: Naughty words and phrases (ODF all versions)
> ------------------------------------------------------------
>
>                 Key: OFFICE-1381
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1381
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: General
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Patrick Durusau
>            Priority: Minor
>             Fix For: ODF 1.2
>
>
> Copied from office-comment list
> Original author: "Alex Brown" <alexb@griffinbrown.co.uk> 
> Original date: 12 Mar 2009 11:16:53 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200903/msg00105.html

-- 
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

        


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