Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-2136

Public Comment: Return of the naughty words and phrases (ODF all versions)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: ODF 1.2
    • Fix Version/s: ODF 1.2
    • Component/s: General
    • Labels:
      None
    • Proposal:
      Hide

      Replace as appropriate:

      • "special" (e.g. 18.404 refers to "a sequence of effects that are
        started when the user interactively clicks on a special element inside a
        page").
      • "particular" as meaningless padding (e.g. 18.795 "[t]he
        text:date-value attribute specifies a particular date value.") Most of
        the time this word should be deleted or replaced with something
        specific.
      • "if and only if" (e.g. 8.1.10 "the table and each distinct group may
        contain one <table:table-header-columns> element, if and only if the
        table columns contained in the <table:table-header-columns> elements are
        adjacent"). A simple "if" will do.
      • "a bit" / "a bit like" (e.g. 19.230 "turns around a bit and moves to
        the bottom-right corner of the screen").
      • "appropriate" as the sole adjective for some normative behaviour (e.g.
        18.348 "[i]f this attribute is not present, a denominator that is
        appropriate for displaying the number is used").
      • "expected to" (18.308 "[t]he form control is expected to react on
        changes in the cell range").
      • "relevant" (e.g. 18.269 "[t]he attribute is only relevant if the
        form:repeat attribute is present, and evaluates to true").
      Show
      Replace as appropriate: "special" (e.g. 18.404 refers to "a sequence of effects that are started when the user interactively clicks on a special element inside a page"). "particular" as meaningless padding (e.g. 18.795 " [t] he text:date-value attribute specifies a particular date value.") Most of the time this word should be deleted or replaced with something specific. "if and only if" (e.g. 8.1.10 "the table and each distinct group may contain one <table:table-header-columns> element, if and only if the table columns contained in the <table:table-header-columns> elements are adjacent"). A simple "if" will do. "a bit" / "a bit like" (e.g. 19.230 "turns around a bit and moves to the bottom-right corner of the screen"). "appropriate" as the sole adjective for some normative behaviour (e.g. 18.348 " [i] f this attribute is not present, a denominator that is appropriate for displaying the number is used"). "expected to" (18.308 " [t] he form control is expected to react on changes in the cell range"). "relevant" (e.g. 18.269 " [t] he attribute is only relevant if the form:repeat attribute is present, and evaluates to true").
    • Resolution:
      Hide

      I have a couple of queries pending on specific items but the soft counts of corrections are as follows:

      • "special" (e.g. 18.404 refers to "a sequence of effects that are
        started when the user interactively clicks on a special element inside a
        page").

      – replaced 10 instances

      • "particular" as meaningless padding (e.g. 18.795 "[t]he
        text:date-value attribute specifies a particular date value.") Most of
        the time this word should be deleted or replaced with something
        specific.

      --replaced 17 instances

      • "if and only if" (e.g. 8.1.10 "the table and each distinct group may
        contain one <table:table-header-columns> element, if and only if the
        table columns contained in the <table:table-header-columns> elements are
        adjacent"). A simple "if" will do.

      – replaced 5 instances, two pending questions

      • "a bit" / "a bit like" (e.g. 19.230 "turns around a bit and moves to
        the bottom-right corner of the screen").

      – replaced 3 instances

      • "appropriate" as the sole adjective for some normative behaviour (e.g.
        18.348 "[i]f this attribute is not present, a denominator that is
        appropriate for displaying the number is used").

      – only one instance might merit replacement but there, number:denominator-value, omits on critical piece of information that makes appropriate work. I added the following note:

      ****
      Note: The number:denominator-value attribute is used with number:grouping 19.350, number:min-denominator-digits 19.352, number:min-integer-digits 19.354 and number:min-numerator-digits 19.355.in defining the display a floating point number as a fraction.
      ****

      In other words, we are always starting with a floating point number and the question is how to display that number as a fraction. (I had an editorial note on this issue, see Office-1682 for that discussion.)

      • "expected to" (18.308 "[t]he form control is expected to react on
        changes in the cell range").

      – replaced one instance

      • "relevant" (e.g. 18.269 "[t]he attribute is only relevant if the
        form:repeat attribute is present, and evaluates to true").

      – replaced 5 instances

      Show
      I have a couple of queries pending on specific items but the soft counts of corrections are as follows: "special" (e.g. 18.404 refers to "a sequence of effects that are started when the user interactively clicks on a special element inside a page"). – replaced 10 instances "particular" as meaningless padding (e.g. 18.795 " [t] he text:date-value attribute specifies a particular date value.") Most of the time this word should be deleted or replaced with something specific. --replaced 17 instances "if and only if" (e.g. 8.1.10 "the table and each distinct group may contain one <table:table-header-columns> element, if and only if the table columns contained in the <table:table-header-columns> elements are adjacent"). A simple "if" will do. – replaced 5 instances, two pending questions "a bit" / "a bit like" (e.g. 19.230 "turns around a bit and moves to the bottom-right corner of the screen"). – replaced 3 instances "appropriate" as the sole adjective for some normative behaviour (e.g. 18.348 " [i] f this attribute is not present, a denominator that is appropriate for displaying the number is used"). – only one instance might merit replacement but there, number:denominator-value, omits on critical piece of information that makes appropriate work. I added the following note: **** Note: The number:denominator-value attribute is used with number:grouping 19.350, number:min-denominator-digits 19.352, number:min-integer-digits 19.354 and number:min-numerator-digits 19.355.in defining the display a floating point number as a fraction. **** In other words, we are always starting with a floating point number and the question is how to display that number as a fraction. (I had an editorial note on this issue, see Office-1682 for that discussion.) "expected to" (18.308 " [t] he form control is expected to react on changes in the cell range"). – replaced one instance "relevant" (e.g. 18.269 " [t] he attribute is only relevant if the form:repeat attribute is present, and evaluates to true"). – replaced 5 instances

      Description

      Copied from office-comment list

      Original author: "Alex Brown" <alexb@griffinbrown.co.uk>
      Original date: 13 Oct 2009 16:23:06 -0000
      Original URL: http://lists.oasis-open.org/archives/office-comment/200910/msg00049.html

        Attachments

          Activity

            People

            • Assignee:
              Patrick Patrick Durusau
              Reporter:
              rcweir Robert Weir (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: