Re: [ubl-psc] [Fwd: Re: quote in spreadsheets and schemas]

[JAVEST by Roberto Cisternino <roberto@javest.com>]

Hello,
the different "curly" quotes have been generated by MAC OS users, 
however as the UBL xsds are valid UTF-8 and even JAXB uses by default 
UTF-8 there should eb no problems.

So I suspect that while reading the xsd:documentation you made some
additional steps using another encoding.

Natively Java String objects are UTF-16 so you must pay attention when
you store UTF-8 data or you make conversions.

If you show me the code maybe I can help more.

Bye


Tim McGrath ha scritto:
> From Ken's reply it appears we will have tpo manually detect and 
> correct the 'smart quotes' that excel likes to put into the text 
> fields. So this action item is open again. Given that this is not a 
> specific PSC issue it should be disposed of when we do the proofing 
> and editing of all the models.
>
>
> ------------------------------------------------------------------------
>
> Oggetto:
> Re: quote in spreadsheets and schemas
> Da:
> "G. Ken Holman" <gkholman@CraneSoftwrights.com>
> Data:
> Wed, 16 Sep 2009 08:40:26 -0700
> A:
> Tim McGrath <tim.mcgrath@documentengineeringservices.com>
>
> A:
> Tim McGrath <tim.mcgrath@documentengineeringservices.com>
>
>
> Good morning, Tim!  I'm in the Seattle area at an ISO meeting this week.
>
> At 2009-09-15 13:01 +0200, you wrote:
>> we are working on the Issues list for UBL 2.1 and came upon
>>
>>>   I had a problem trying to generate JAXB Bindings for OASIS UBLv2 
>>> (http://www.oasis-open.org/specs/#ublv2.0) in the Netbeans IDE 
>>> (version 6.5 rc2). The problem is with some quoted strings, in some 
>>> strings the quoting is done with opening and closing double quotes 
>>> with an hexadecimal encoding of E2 80 9C and E2 80 9D, while in the 
>>> rest of the UBL documents hexa 22 is used for a straight double quote.
>>>     The three byte quotes seems to be valid UTF-8 since they are 
>>> displayed with the proper glyph in other text editors, and people 
>>> from the ubl-dev list confirmed this. But I'm getting an error 
>>> "unmappable character for encoding UTF-8" and the offending strings 
>>> are displayed as: ?VISA?, ?MasterCard?, etc. in the error output 
>>> window in Netbeans.
>
> Java is really finicky about character sets.  I'm not a Java 
> programmer, but somehow the user has to "turn on" UTF-8 encoding for 
> character strings.
>
>>>    The problem seems to appear only within CommonAggregateComponents-2,
>>> in CardAccountType and CountryType. After suggestion from a ubl-dev 
>>> list member, I tried with the runtime xsdrt in 
>>> (http://docs.oasis-open.org/ubl/os-UBL-2.0/xsdrt/) and the problem 
>>> dissappeared.
>
> Right, because the documentary bits are removed from xsdrt components.
>
>> i recall we talked about fixing the quate marks in the sreadsheets.  
>> did that get done?
>
> I guess not ... I still see smart quotes being used in NetworkID and 
> CardCodeType and Country/Name, but not anywhere else.  Perhaps these 
> were last-minute edits that were overlooked.
>
> . . . . . . . . . . . Ken
>
> -- 
> Upcoming hands-on code list, UBL, XSLT, XQuery and XSL-FO classes.
> Interested in other classes?  http://www.CraneSoftwrights.com/m/i/
> Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/m/
> Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
> Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
> Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
> G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
> Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/m/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
> ------------------------------------------------------------------------
>
>
> Nessun virus nel messaggio in arrivo.
> Controllato da AVG - www.avg.com 
> Versione: 8.5.409 / Database dei virus: 270.13.100/2374 -  Data di rilascio: 09/15/09 20:00:00
>
>