Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Resolved: (XERCESJ-1255) Unresolved variables in Italian localization of

Resolved: (XERCESJ-1255) Unresolved variables in Italian localization of

2007-06-13       - By Michael Glavassevich (JIRA)


    [ https://issues.apache.org/jira/browse/XERCESJ-1255?page=com.atlassian
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Glavassevich resolved XERCESJ-1255.
-------------------------------------------

   Resolution: Invalid

Xerces-J's distribution doesn't come with any translated messages.  If you look
inside the xercesImpl.jar of any release from Apache you'll find that there are
only English messages in there.  You must have been using XML4J (though I can't
seem to reproduce this problem with it).  At any rate there's nothing that can
be done in Apache to address this.

> Unresolved variables in Italian localization of error messages into
XMLSchemaMessages properties file.
> -----------------------------------------------------------------------------
-------------------------
>
>                 Key: XERCESJ-1255
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1255
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 2.6.2
>         Environment: Italian localization
>            Reporter: monica pontrelli
>
> A lot of messages into XMLSchemaMessages_it.properties file are not properly
written.
> Following there are 2 of these messages as examples :
>         cvc-complex-type.2.4.a = cvc-complex-type.2.4.a: \u00c8 stato
rilevato un avvio contenuto non valido con l''''elemento ''{0}''. \u00c8
previsto uno di ''{1}''.
>         cvc-complex-type.2.4.b = cvc-complex-type.2.4.b: Il contenuto dell'''
'elemento ''{0}'' non \u00e8 completo. \u00c8 previsto uno di ''{1}''.
> They do not properly apply the rule into the starting section of the file
that I'm reporting here:
> # If you are using the IBMJDK11 markup table or are a developer working
> # with this file in a text editor, use the following rules for
> # apostrophe characters:
> #  a) If there are inserts in the message, for example "{0}", then
> #     type two apostrophe characters, that is "''".
> #  b) If there are no inserts, then just type a single apostrophe.
> # Examples:
> #  a) message.xml.parserError.prefix=UDUT0036E: Erreur de l''analyseur
syntaxique : {0}
> #  b) error.getAuthInfoFailed=UDUT0078E: Impossible d'obtenir authinfo.
> They use 4 apostrophes instead of 2 and this prevent the the inserts to be
properly resolved.
> As example this is the behaviour of the error message dispalayed by the
application in the italian localization:
> "cvc-complex-type.2.4.a: E stato rilevato un avvio contenuto non valido con l
'elemento '{0}'. E' previsto uno di '{1}'."
> where the inserts {0} and {1} are unresolved.
> while the french one look like this:
> "cvc-complex-type.2.4.a : Contenu non valide commen?ant par l'?l?ment 'jsdl
:candidateOperatingSystems'. Contenu de '{WC[##other:"http://www.ibm.com/xmlns
/prod/scheduling/1.0/jsdl"], "http://www.ibm.com/xmlns/prod/scheduling/1.0/jsdl"
:operatingSystem}' attendu."
> where the inserts {0} and {1} are properly resolved.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)