Orbeon Forms community mailing list

Character encoding in XML initial instances

Classic

List

Threaded

8 messages Options

lacco

Character encoding in XML initial instances

Hello,

I am currently POSTing XML instances to create new forms [1], but as soon as I try sending Umlauts, the resulting form doesn't display them correctly [2]. This behavior is easily reproducible with the HTML form [1] and a newly created Orbeon form.

I tried to encode my XML document, but I get the same errors like in [3]. I even exchanged the underlying Base64 as supposed in [4] which didn't help.

Am I doing something wrong, what is the best way of having UTF-8 characters in initial instances? Thx!

[1] https://gist.github.com/1200a1a55dc3d61a77b2
[2] http://img.skitch.com/20100521-1t6humkyjg34gbujkqd2tk4edg.png

[3] http://orbeon-forms-ops-users.24843.n4.nabble.com/HTML-character-encoding-td33897.html#a33897
[4] http://orbeon-forms-ops-users.24843.n4.nabble.com/Tamino-configuration-using-properties-tp26849p26856.html

Alessandro Vernet

Re: Character encoding in XML initial instances

Administrator

There must be a problem with the way you are encoding the file. Try
using the program attached to do the base64 encoding, copy the string
you get with that program in the HTML form you created, and you'll
have the accents with the correct encoding in the form. Note that the
attached XForms XML document is itself encoded in UTF-8. The fact that
the form itself is UTF-8 (vs. ISO-8859-1 or something else) doesn't
matter; what matters is that the declared encoding matches the actual
encoding of the file.

Alex

On Fri, May 21, 2010 at 2:18 AM, lacco <[hidden email]> wrote:

>
> Hello,
>
> I am currently POSTing XML instances to create new forms [1], but as soon as
> I try sending Umlauts, the resulting form doesn't display them correctly
> [2]. This behavior is easily reproducible with the HTML form [1] and a newly
> created Orbeon form.
>
> I tried to encode my XML document, but I get the same errors like in [3]. I
> even exchanged the underlying Base64 as supposed in [4] which didn't help.
>
> Am I doing something wrong, what is the best way of having UTF-8 characters
> in initial instances? Thx!
>
>
> [1] https://gist.github.com/1200a1a55dc3d61a77b2
> [2] http://img.skitch.com/20100521-1t6humkyjg34gbujkqd2tk4edg.png
>
> [3]
> http://orbeon-forms-ops-users.24843.n4.nabble.com/HTML-character-encoding-td33897.html#a33897
> [4]
> http://orbeon-forms-ops-users.24843.n4.nabble.com/Tamino-configuration-using-properties-tp26849p26856.html
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Character-encoding-in-XML-initial-instances-tp2225861p2225861.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
Orbeon Forms - Web forms, open-source, for the Enterprise -
http://www.orbeon.com/
My Twitter: http://twitter.com/avernet

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

20100521-lacco-encoding.xhtml (1K) Download Attachment

ressult-from-post.png (49K) Download Attachment

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

lacco

Re: Character encoding in XML initial instances

You have been totally right: My Base64 encoding doesn't have been correct. I used a JavaScript client library which have problems with UTF-8, so I switched to another one [1]!

Thank you very much!

[1] http://www.webtoolkit.info/javascript-base64.html

Alessandro Vernet

Re: Re: Character encoding in XML initial instances

Administrator

Excellent; I am glad you got to solve that encoding problem.

Alex

On Thu, May 27, 2010 at 2:32 AM, lacco <[hidden email]> wrote:

>
> You have been totally right: My Base64 encoding doesn't have been correct. I
> used a JavaScript client library which have problems with UTF-8, so I
> switched to another one [1]!
>
> Thank you very much!
>
> [1] http://www.webtoolkit.info/javascript-base64.html
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Character-encoding-in-XML-initial-instances-tp2225861p2232821.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

rdanner

Re: Character encoding in XML initial instances

In reply to this post by lacco

I am using the <xforms:insert tag in combination with the
xxforms:get-request-attribute('instance')

I have a DOM which I insert in to the request attribute map via java this way

I have tried this with both UTF-8 encoding and US-ASCII encoding
I have tried via w3c DOM and via STRING

consider the US-ASCII version
קשערתט

What I should see in the inspector and in my field is
קשערתט

What I do see is:
ￗﾧￗﾩￗﾢￗﾨￗﾪￗﾘ

As far as I can tell all the XML, the Browser etc everyone agrees on the encoding but it goes in the the map seeming to be right and comes out on the other side of the insert handled wrong.

rdanner

Re: Character encoding in XML initial instances

In reply to this post by lacco

I am using the <xforms:insert tag in combination with the
xxforms:get-request-attribute('instance')

I have a DOM which I insert in to the request attribute map via java this way

I have tried this with both UTF-8 encoding and US-ASCII encoding
I have tried via w3c DOM and via STRING

consider the US-ASCII version
קשער&#amp;1514;ט

What I should see in the inspector and in my field is
קשערתט

What I do see is:
ￗﾧￗﾩￗﾢￗﾨￗﾪￗﾘ

As far as I can tell all the XML, the Browser etc everyone agrees on the encoding but it goes in the the map seeming to be right and comes out on the other side of the insert handled wrong.

rdanner

Re: Character encoding in XML initial instances

ID-10-T error....

This is a *working* example
test.jsp

Alessandro Vernet

Re: Re: Character encoding in XML initial instances

Administrator

Russ,

Are you saying that the example attached works for you, but you have
another one that doesn't work? Where are we on this?

Alex

On Tue, Aug 17, 2010 at 11:20 PM, rdanner <[hidden email]> wrote:

>
> ID-10-T error....
>
> This is a *working* example
> http://orbeon-forms-ops-users.24843.n4.nabble.com/file/n2329400/test.jsp
> test.jsp
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Character-encoding-in-XML-initial-instances-tp2225861p2329400.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet