[Padma] Fwd: How to manually transform a page by Padma?

[V S Rawat]

On 5/13/2007 07:17 PM India Time, _Nagarjuna Venna_ wrote:

> On 5/12/07, V S Rawat <vsrawat at gmail.com> wrote:
>> However, I couldn't understand what is the merit of keeping padma
>> working only on non-unicode character encoding, and keeping it not
>> working on unicode encoding.
> 
> Padma converts proprietary formats to Unicode: if the text is Unicode
> encoded there is *nothing* to do, it is already Unicode.

But haven't we just seen that the above assumption doesn't hold good.

page encoding doesn't have any strict relation with what charaters/ 
fonts are there in the page. can't I put Shusha, Ankit, Shrilipi, Kriti 
font text in the same page with mangal and make the page encoding unicode?

> 
> There might be value in making the user aware of it - doing that
> within the confines of a browser is rather difficult. It has to be
> balanced against usage where user selects both unicode and non-unicode
> text for transform at the same time. No one wants to see an error
> message in the latter case.

I struggled with padma for a long time due to lack of error (or should I 
say guidance) messages.

anyway. when the page text is really in unicode, why should the error 
message be shown? By checking the code of the character, we can find out 
that it is in unicode code range, hence no error message needs to be 
displayed. But if there is enough text in non unicode range and the 
encoding is unicode, then the message can be displayed.

thanks
-- 
Rawat