controlling character encoding when converting instance into HTML

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

controlling character encoding when converting instance into HTML

Alexander Žaťko
I constructed a form that contains a couple of text areas. The users  
populate these mostly by copying text from Word. This text includes  
all kinds of high ASCII chars like bullets, curly quotes and such.  
These chars do not show correctly on a html page that I build from  
the instance using an XSLT processor.

For example a bullet shows as
  (see attachment if not shown in-line). I think I will have to set  
proper encodings somewhere and was hoping that somebody on this list  
might shed some light at this for me.
Just placing:

<xhtml:meta http-equiv="Content-Type" content="text/html;  
charset=utf-8"/>

...into the <head> html element does not help.

Thanks

A.

--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

bullet.png (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: controlling character encoding when converting instance into HTML

Jay Klehr
You should look into using the FCKEditor, it has a "paste from word" option that usually takes care of a lot of those special html entities and other word peculiarities.
 
Jay

________________________________

From: Alexander Zatko [mailto:[hidden email]]
Sent: Wed 8/30/2006 1:17 PM
To: [hidden email]
Subject: [ops-users] controlling character encoding when converting instance into HTML



I constructed a form that contains a couple of text areas. The users
populate these mostly by copying text from Word. This text includes
all kinds of high ASCII chars like bullets, curly quotes and such.
These chars do not show correctly on a html page that I build from
the instance using an XSLT processor.

For example a bullet shows as



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

winmail.dat (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: controlling character encoding when converting instance into HTML

Erik Bruchez
Administrator
Note that the FCKEditor is enabled in OPS when you use
xforms:textarea/mediatype="text/html".

But Alex's issue may be related to something else. OPS is meant to
handle Unicode encodings, typically UTF-8, end to end, so his issue is a
little surprising.

-Erik

Jay Klehr wrote:

> You should look into using the FCKEditor, it has a "paste from word" option that usually takes care of a lot of those special html entities and other word peculiarities.
>  
> Jay
>
> ________________________________
>
> From: Alexander Zatko [mailto:[hidden email]]
> Sent: Wed 8/30/2006 1:17 PM
> To: [hidden email]
> Subject: [ops-users] controlling character encoding when converting instance into HTML
>
>
>
> I constructed a form that contains a couple of text areas. The users
> populate these mostly by copying text from Word. This text includes
> all kinds of high ASCII chars like bullets, curly quotes and such.
> These chars do not show correctly on a html page that I build from
> the instance using an XSLT processor.
>
> For example a bullet shows as
--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: controlling character encoding when converting instance into HTML

Alexander Žaťko
I figured out what was the problem. I did not set the proper encoding  
on the <part> element so the mail processor used the default  
iso-8859-1. A clear case of the RTFM :-)

thanks

A.

On Aug 30, 2006, at 3:46 PM, Erik Bruchez wrote:

> Note that the FCKEditor is enabled in OPS when you use  
> xforms:textarea/mediatype="text/html".
>
> But Alex's issue may be related to something else. OPS is meant to  
> handle Unicode encodings, typically UTF-8, end to end, so his issue  
> is a little surprising.
>
> -Erik
>
> Jay Klehr wrote:
>> You should look into using the FCKEditor, it has a "paste from  
>> word" option that usually takes care of a lot of those special  
>> html entities and other word peculiarities.
>>  Jay
>> ________________________________
>> From: Alexander Zatko [mailto:[hidden email]]
>> Sent: Wed 8/30/2006 1:17 PM
>> To: [hidden email]
>> Subject: [ops-users] controlling character encoding when  
>> converting instance into HTML
>> I constructed a form that contains a couple of text areas. The  
>> users populate these mostly by copying text from Word. This text  
>> includes all kinds of high ASCII chars like bullets, curly quotes  
>> and such. These chars do not show correctly on a html page that I  
>> build from the instance using an XSLT processor.
>> For example a bullet shows as
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>
> --
> You receive this message as a subscriber of the ops-
> [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/ 
> wws



--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws