http://www.zope.org/Members/ajung/howto/Locale%20Support%20for%20Structured %20Text/
That's very good but I can't expect people to fiddle about with these sort things just for my product. Maybe the unix gurus will call me a doubleclickability-windows-geek now. But thank you anyways. If I can't figure this out I'll have to leave it and let people who can be bothered to get the ST feature based on your how-to. At the moment I'm doing a big fat search and replace(s) on the text that goes in and out of the structured_text() function. Bad for processing since this will happen quite a lot. Cheers, Peter
--On Freitag, 27. September 2002 06:41 +0100 Peter Bengtsson <mail@peterbe.com> wrote:
Consider the following example code:
from Products.PythonScripts.standard import structured_text print structured_text("Svenska *tacken*") <p>Svenska <em>tacken</em></p>
print structured_text("Svenska *täcken*") <p>Svenska *täcken*</p>
Shouldn't structured_text() be able to support these special characters? Is there a workaround except writing up a simple (but extra processing) hack?
Shall I put it in the Collector?
Regards, Peter
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
--- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 2002-09-19
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 2002-09-19