Warning: base64_decode() expects parameter 1 to be string, array given in /home/eheupel/eclecticechoes.com/wp-content/plugins/askapache-google-404/askapache-google-404.php on line 156
Comments on: Shippō http://eclecticechoes.com/2004/03/01/shippo-pattern/ Science + Art + Knitting + Photography + Parenting = Chaos Thu, 03 May 2012 23:11:41 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: eric http://eclecticechoes.com/2004/03/01/shippo-pattern/comment-page-1/#comment-71 eric Wed, 30 Nov -0001 00:00:00 +0000 http://eclecticechoes.com/2004/03/01/shipp/#comment-71 <p>Ok that’s wierd. When I first published this it had the proper encoding on “shippō” that is to say s—h—i—p—p—o-macron”. Then I unpublished the entry, added the SixApart recently updated key, then republished. Did changing the publish status change the encoding? I can’t for the life of me see why, but then it makes even less sense to think that the recently updated key (which really only activates a trackback ping?) would change the encoding. </p> <p>Oddly enough in the comment listing template it shows properly as “shippō” with the o-macron. </p> Ok that’s wierd. When I first published this it had the proper encoding on “shippō” that is to say s—h—i—p—p—o-macron”. Then I unpublished the entry, added the SixApart recently updated key, then republished. Did changing the publish status change the encoding? I can’t for the life of me see why, but then it makes even less sense to think that the recently updated key (which really only activates a trackback ping?) would change the encoding.

Oddly enough in the comment listing template it shows properly as “shippō” with the o-macron.

]]> By: eric http://eclecticechoes.com/2004/03/01/shippo-pattern/comment-page-1/#comment-72 eric Wed, 30 Nov -0001 00:00:00 +0000 http://eclecticechoes.com/2004/03/01/shipp/#comment-72 <p>Ok…<br /> So to clarify the page was for a while showing “ShippÅ” immediately followed by a box, in otherwords mangling the o-macron character into an non-valid charachter. Naturally the validator complained loudly about it, although at least IE and Mozilla would still display the page properly–save for the mangled word “shippō”. I had to go into the database itself to correct the issue. Reall pain in the arse.</p> Ok…
So to clarify the page was for a while showing “ShippÅ” immediately followed by a box, in otherwords mangling the o-macron character into an non-valid charachter. Naturally the validator complained loudly about it, although at least IE and Mozilla would still display the page properly–save for the mangled word “shippō”. I had to go into the database itself to correct the issue. Reall pain in the arse.

]]> By: Jacques Distler http://eclecticechoes.com/2004/03/01/shippo-pattern/comment-page-1/#comment-73 Jacques Distler Wed, 30 Nov -0001 00:00:00 +0000 http://eclecticechoes.com/2004/03/01/shipp/#comment-73 Since you seem to be still having the problem of invalid SGML characters, why not give up and write ō for o-macron? Since you seem to be still having the problem of invalid SGML characters, why not give up and write &#333; for o-macron?

]]> By: Eric http://eclecticechoes.com/2004/03/01/shippo-pattern/comment-page-1/#comment-74 Eric Wed, 30 Nov -0001 00:00:00 +0000 http://eclecticechoes.com/2004/03/01/shipp/#comment-74 <p>I take it you mean use the & escaped value #333 for ō? Granted that works well for this one, but… <br /> I should be able to get UTF8 input to go straight through the system just fine, yet it’s not working that way at all. Really annoying. What’s more annoying is that the ō character (input as a UTF8 character, not as escaped #333;) shows just fine in the comments every time. So it’s something I am missing in the main entry handling.</p> I take it you mean use the & escaped value #333 for ō? Granted that works well for this one, but…
I should be able to get UTF8 input to go straight through the system just fine, yet it’s not working that way at all. Really annoying. What’s more annoying is that the ō character (input as a UTF8 character, not as escaped #333;) shows just fine in the comments every time. So it’s something I am missing in the main entry handling.

]]>