Hi Yong Peng,

Maybe Pat knows the answer, I'll wait another day or 2 before looking
into it more myself.
Looking at the html source for satipatthana:
<B>Satipaṭṭhāna</B>
The numbers specified for the are higher than 255, meaning bigger than 8
bit number, but I don't know enough about unicode. There' s no reason
why yahoo mail server can't convert that to an 8bit unicode if it's a
well definined standard though.

Why are we not supporting html? Is blocking attachments the only reason?

I've been using other yahoogroup lists that do allow html attachments,
as well as googlegroups lists that allow html attachments, for many
years now without any virus problems. Both services scan posted messages
for viruses in attachments beforehand. Haven't had any problems. It
really make us feel handcuffed when we can't just cut and paste from
online pali tipitaka, DPR, PTR, and drop it right into the email message.

-Frank

On 1/27/2010 4:27 AM, Ong Yong Peng wrote:
>
>
>
> Dear Frank,
>
> thanks for your effort with the diagnosis. I would like to know if
> Yahoo! Group's text editing interface (which is a standard HTML
> form/textbox) is rendering certain Unicode characters illegible. I am
> only using the plain-text editor, not the rich-text editor.
>
> By the way, using the rich-text editor features for text formatting,
> i.e. bold, italic, etc., will not work because it only works when
> attachments are allowed. Correct me if I am wrong.
>
> When Nina replied to Pat's mail, the characters remained undistorted.
> She is using a traditional email client.
>
> Pat is probably using a browser-based email client, such as G-mail, if
> I am right.
>
> I have been working with HTML forms for a long while. Those on
> tipitaka.net have been Unicode-compliant for years. And, they are just
> plain-text forms, nothing fancy. But, having understood the
> complications to get technology to work at times, it may be more than
> what meets the eyes.
>
> metta,
> Yong Peng.
>
> --- In Pali@yahoogroups.com <mailto:Pali%40yahoogroups.com>, fcckuan
> wrote:
>
> The preview for rich text editor worked, sending it produced what you
> saw (not working). I'll wait for Patrick to diagnose what's going on,
> and give a ruling on whether the unicode from worldtipitaka.org was
> compliant :)
>
>



[Non-text portions of this message have been removed]