Ok...
Multilingual characters can be passed via the API, but they must be encoded
first. The problem is that XML::Parser does not handle multilingual
characters properly (I hope some dev person can help me out on the details
here).
You *can* get these characters into the system, but they cannot be sent via
the API in raw format, they must be encoded (I think it's the &XXX; format)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: Jose Luis Moya [mailto:joseluis@alsur.es]
> Sent: January 9, 2002 2:09 PM
> To: Charles Daminato; discuss-list@opensrs.org
> Cc: Horacio
> Subject: Re: "Invalid XML or unsupported high-end ASCII" problem
>
>
> Our own domain (nombremania.com) contains extended characters (Díaz on
> address or Málaga on city) and I am allowed to change and add extended
> characters under manage.
>
> I am not 100% that I got this clear but If this is has never been possible
> in the registration process (alltough we are only recieving
> errors since the
> latest API revision), how can it be avialable afterwards on manage?
>
> An more important what are we suppose to tell clients to write now on the
> new domain registration requests if their surnames is "Madroño"
> or they live
> in the city of "La Coruña"?
>
> How can we have technology to perform multilingual domains but not
> multilingual contact details for domains?
>
> If OpenSRS really considers an internationa approach you better start
> keeping this "simple" things in mind. Let's face it, there are
> probably even
> more spanish speakers in the States now than even in Spain, not to mention
> all of south america. Lots and lots of them happen to be named on
> non-ASCII
> characters.
>
> Thanks.
>
>
>
> Jose Luis Moya
> nombremania.com
>
>
> > From: "Charles Daminato" <chuck@tucows.com>
> > Date: Wed, 9 Jan 2002 13:15:30 -0500
> > To: "Jose Luis Moya" <joseluis@alsur.es>, <discuss-list@opensrs.org>
> > Subject: RE: "Invalid XML or unsupported high-end ASCII" problem
> >
> > The systems have been returned to the same functionality they
> were at prior
> > to the co-location move, as far as multilingual characters are
> concerned.
> > AFAIK these characters would not have been allowed previously.
> If you can
> > provide me with a registration that was made previously with these
> > characters, I can re-escalate.
> >
> > Charles Daminato
> > OpenSRS Product Manager
> > Tucows Inc. - chuck@tucows.com
> >
> >> -----Original Message-----
> >> From: Jose Luis Moya [mailto:joseluis@alsur.es]
> >> Sent: January 9, 2002 1:14 PM
> >> To: Charles Daminato; discuss-list@opensrs.org
> >> Subject: Re: "Invalid XML or unsupported high-end ASCII" problem
> >>
> >>
> >> I thought this problem was now "solved":
> >>
> >> REQUESTING (extended characters in address):
> >>
> >> owner_first_name Marta
> >> owner_last_name Lagarta Juancho
> >> owner_org_name particular
> >> owner_address1 Avda. del Caño,11
> >> owner_address2
> >> owner_address3
> >> owner_city Almería
> >> owner_state Almería
> >> owner_country ES
> >> owner_postal_code 23001
> >> ...
> >>
> >> REPLY:
> >>
> >> array(9) {
> >> ["is_success"]=>
> >> bool(false)
> >> ["protocol"]=>
> >> string(3) "XCP"
> >> ["object"]=>
> >> string(11) "SW_REGISTER"
> >> ["attributes"]=>
> >> array(1) {
> >> ["error"]=>
> >> string(448) "
> >> Non-ASCII character Ã- not permitted in owner state.
> >> Non-ASCII character ñ not permitted in owner address1.
> >> Non-ASCII character Ã- not permitted in owner city.
> >>
> >> "
> >> }
> >> ["response_text"]=>
> >> ...
> >>
> >> Thanks.
> >>
> >>
> >> Jose Luis Moya
> >> nombremania.com
> >>
> >>
> >>
> >>
> >>
> >>> From: Charles Daminato <chuck@tucows.com>
> >>> Date: Tue, 8 Jan 2002 18:24:35 -0500 (EST)
> >>> To: discuss-list@opensrs.org
> >>> Subject: "Invalid XML or unsupported high-end ASCII" problem
> >>>
> >>> This has been solved successfully.
> >>>
> >>> We sincerely apologize for the length of this problem; it was
> >> certainly a
> >>> tricky one to track down. You should no longer be experiencing this
> >>> problem with new registrations, and management of existing
> registrations
> >>> that were affected by this problem.
> >>>
> >>> I thank everyone affected by this problem for their patience and
> >>> assistance in tracking things down.
> >>>
> >>> Charles Daminato
> >>> TUCOWS Product Manager
> >>> chuck@tucows.com
> >>>
> >>>
> >>>
> >>
> >
> >
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:36:58 EDT