Uploaded image for project: 'XalanC'
  1. XalanC
  2. XALANC-432

Minor spelling problems in XalanMsg_en_US.xlf

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.8
    • Fix Version/s: None
    • Component/s: XalanC
    • Labels:
      None
    • Environment:
      Operating System: Other
      Platform: All
    • Bugzilla Id:
      30750

      Description

      I had a look at the messagefile, because I thought of adding a translation to
      de_DE. This is much more difficult than I expected, because of the XSLT specific
      terms. I can't think of the translation of "match expression" for example, so
      that everybody reading the translation would know what it means (anybody know
      about translations of the XSLT standard?).

      Here are my (minor) comments to the en_US message file (sorry for non native
      speakers mistakes):

      InvalidNumberOfArgsWasDetected_3Param:
      An invalid number of arguments for op code '

      {0}' was detected. The required
      number of arguments is '{1}', but '{2}' arguments(s) were supplied.
      => argument(s)

      ExpectedDoubleQuote:
      The literal expression is not terminated. An double quote is missing.
      => A double quote????

      ExpectedSingleQuote:
      The literal expression is not terminated. An single quote is missing.
      => A single quote????

      NotFoundWhatExpected_2Param:
      Expected token is '{0}

      ', but found the '

      {1}

      ' token
      => Dot missing in target.

      AttributesCannotBeAdded:
      Attributes cannot be added after a child has been added. The attribute(s) will
      not be added.
      => doubled space between the two sentences

      XslSortHasUnlnownDataType:
      => Spelling of the key wrong. Used by ElemForEach.cpp. Maybe use the message
      UnknownDataType.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              floerke@doctronic.de Holger Floerke
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: