Re: Japanese in manila
Posted
Last Modified
In Response To
2/24/2002; 1:57 PM by Emmanuel. M. DecarieLast Modified
In Response To
2/24/2002; 1:57 PM by Emmanuel. M. Decarie
Japanese in manila (#16184)
Reply To This Message [Edit]
Hello Daniel,
Thanks for the great input. Its nice to see where Manila run well and
where it choke.
>Read on the web at http://community.scriptmeridian.org/16184
>----------------------------------
>
>Hello Jonathan, Emmanuel and others.
>
>Have followed Emmanuel. M. Decarie's Simplified Chinese (GB2312) in Manila
> with great interest. I've been looking for a way to run a manila
>site in japanese for some time.
>
>Please excuse my rather non technical writing, I am not at all
>familiar with frontier scripting or programming in general, nor the
>differing flavours of ascii
>
>Following Emmanuel's example
>http://community.scriptmeridian.org/discussionThread$msgNum=16120
>replaced his <meta http-equiv="Content-Type" content="text/html;
>charset=gb2312">
>with <META HTTP-EQUIV="content-type" CONTENT="text/html; charset=Shift_JIS">
>I chose Shift_JIS as it gave the most reliable results when I tried
>to get radio and japanese working earlier today.
>
>Have found that news, discussion, shortcuts and stories survive
>editing in japanese / manila as do changes in the prefs and the few
>macros i tried, printfriendlypage includemessage.
>The exception is the <navigator> which returns garbled text. Did not
>test membership.
>
>Other places where the japanese is returned as a garbled mess are
>the email notifications of changes and using plugins, tested on
>Filer and Metadata both return frontier webpage
>mainresponder.respond errors.
>
>The japanese text stored in the gdb looks the same unreadable
>rubbish, whether its a glossary item, discussion message or stored
>in plugins.data The difference is that the text in plugins.data
>returns the mainresponder.respond error page.
>
>Tested on OSX 8.0b48 desktop, and my "live site"
>http://nihongo.nelson.co.nz/ is on
>OS9 and 7.01
>
>Also tried out with radio http://radio.weblogs.com/0100090/
>But not much joy, Its odd that manila works but radio does not, I
>had assumed that both were now in sync with each other.
My guess is that Radio should work, but there is a mix up somewhere
between MacRoman and ISO-8859-1.
>I am ecstatic ! that I can run a basic manila site in japanese,
>thanks to both Emmanuel, Jonathan and the others for believing that
>its not impossible and showing the way :) I wouldn't have tried
>otherwise.
>
>I would be happy to help anyone in a non programming way to progress this.
Thanks and you already did help with your tests.
Cheers
-Emmanuel
--
______________________________________________________________________
Emmanuel Décarie / Programmation pour le Web - Programming for the Web
Frontier - Perl - Javascript - XML <http://scriptdigital.com/>
Thanks for the great input. Its nice to see where Manila run well and
where it choke.
>Read on the web at http://community.scriptmeridian.org/16184
>----------------------------------
>
>Hello Jonathan, Emmanuel and others.
>
>Have followed Emmanuel. M. Decarie's Simplified Chinese (GB2312) in Manila
> with great interest. I've been looking for a way to run a manila
>site in japanese for some time.
>
>Please excuse my rather non technical writing, I am not at all
>familiar with frontier scripting or programming in general, nor the
>differing flavours of ascii
>
>Following Emmanuel's example
>http://community.scriptmeridian.org/discussionThread$msgNum=16120
>replaced his <meta http-equiv="Content-Type" content="text/html;
>charset=gb2312">
>with <META HTTP-EQUIV="content-type" CONTENT="text/html; charset=Shift_JIS">
>I chose Shift_JIS as it gave the most reliable results when I tried
>to get radio and japanese working earlier today.
>
>Have found that news, discussion, shortcuts and stories survive
>editing in japanese / manila as do changes in the prefs and the few
>macros i tried, printfriendlypage includemessage.
>The exception is the <navigator> which returns garbled text. Did not
>test membership.
>
>Other places where the japanese is returned as a garbled mess are
>the email notifications of changes and using plugins, tested on
>Filer and Metadata both return frontier webpage
>mainresponder.respond errors.
>
>The japanese text stored in the gdb looks the same unreadable
>rubbish, whether its a glossary item, discussion message or stored
>in plugins.data The difference is that the text in plugins.data
>returns the mainresponder.respond error page.
>
>Tested on OSX 8.0b48 desktop, and my "live site"
>http://nihongo.nelson.co.nz/ is on
>OS9 and 7.01
>
>Also tried out with radio http://radio.weblogs.com/0100090/
>But not much joy, Its odd that manila works but radio does not, I
>had assumed that both were now in sync with each other.
My guess is that Radio should work, but there is a mix up somewhere
between MacRoman and ISO-8859-1.
>I am ecstatic ! that I can run a basic manila site in japanese,
>thanks to both Emmanuel, Jonathan and the others for believing that
>its not impossible and showing the way :) I wouldn't have tried
>otherwise.
>
>I would be happy to help anyone in a non programming way to progress this.
Thanks and you already did help with your tests.
Cheers
-Emmanuel
--
______________________________________________________________________
Emmanuel Décarie / Programmation pour le Web - Programming for the Web
Frontier - Perl - Javascript - XML <http://scriptdigital.com/>
Enclosures
None.
Replies
Re: Japanese in manila
2/24/2002 by daniel springett
Thanks for the kind words Would love to have Metadata and Filer plugins work with Japanese along with the <navigator>, Will
2/24/2002 by daniel springett