Textile plugin: Encoding failing, their options inoperative

  • Arla

    (@arla)


    16 years, 3 months ago

    With the plugin enabled, all entries show miscoded signs. They are probably unicode (utf-8) signs being treated as western (iso-8859-1) – they look like: Ã¥, ä, ö. I figured changing the input and output encoding options to iso-8859-1 and utf-8 respectively would be fine, but there was no difference, and neither did swapping them around.

    Peeked in the plugin file but couldn’t figure where to change anything and how.

Viewing 2 replies - 1 through 2 (of 2 total)
  • jaireaux

    (@jaireaux)

    16 years, 3 months ago

    I have the same problem. When I leave the option set to “Brad Choate” style I get things like this:

    Sarcasm Mark: <sub>¡<sub>

    When I set it to purist it converts my javascript that was entered as this:

    var s1 = new SWFObject(“/backporchbeer/flvplayer.swf”,”single”,”480″,”280″,”7″);

    to this:

    var s1 = new SWFObject(”/backporchbeer/flvplayer.swf”,“single”,“480”,“280”,“7”);

    ack! Is there another Textile plugin that works?

    (do a view source…it looks fine here, but it converted my quotes into escape/ampersand codes.)

    Thread Starter Arla

    (@arla)

    16 years, 2 months ago

    The Textiler plugin works much better (i.e. correctly). It’s a bit simpler, but provides the ability to set whether Textile should be applied to *all posts, *between {{{ and }}} or *no posts, for entries as well as comments.

    I tested every Textile function in Textiler and it works well, except left aligning (for example “p<.“), since the editor seems to automatically add a space: “p< .“. Fortunately, left aligning is not very common.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Textile plugin: Encoding failing, their options inoperative’ is closed to new replies.