4 Nov
2007
4 Nov
'07
7:16 p.m.
WAKom stop.
WAKomEncoded startOn: 8080
So maybe all the Pier packages don't use the same UTF/WideStrings
default ?
I am always using WAKom, this means the model will contain UTF-8
Strings only. If you use one of the other Kom servers your model will
contain strings with a different encoding.
Pier does not care how the strings are encoded in its model, it only
has to be consistent. Also some web servers have (well known) problems
when the encoding is incompatible.
Cheers,
Lukas
On 04/11/2007, Damien Pollet
<damien.pollet(a)gmail.com> wrote:
--
Lukas Renggli
http://www.lukas-renggli.ch
Hi,
I have two Pier images that give partial HTML an a particular page in
Pier. Safari just displays a few lines of uninterpreted, unfinished
HTML. The HTML ends repetedly at the same place:
- in one image it's in the middle of a string (html text: 'in the
middle of this string')
- in the second image it's just after the first occurence of a
continuation argument in a URL (this image is squeak-dev 7145 +
latest
pier-blog from universes)
I tried debugging, but the HTML generation goes further than what
Safari gets, so the bug must be later when seaside sends the page to
the browser… any idea how to proceed ?
--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org
--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org
_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki