seems that `DomDocument->createTextNode()' accepts only utf-8 string,
try encode the text before pass it to that function.
in browser side, you can view document property,
browser generally allow you to specify any encoding used to view a
page, try get familar with you browser first.
On 11/3/05,
so I decided it would be best just to convert back to the original
format so for this string:
$string="braised beef shortribs with sautéed greens, pearl
onions and horseradish cream"
I do an html_entity_decode($string);
but this still gives me an error when I add it via the DOM functions
b
try this,
if you need more entities to be included,
just refer to
`http://www.w3.org/2003/entities/iso8879/isolat1.ent' or find out its
charcode by yourself.
]>
farm lettuces with reed avocado, crème
fraîche, radish and cilantro
On 10/13/05, jonathan <[EMAIL PROTECTED]> wrote:
> I'm now get
jonathan wrote:
So I'm reading up on character encoding in XML documents as I think
this is the problem (after the many helpful suggestions on this list).
With regards to your second question; no, I'm not sure if I'm using
proper utf-8 througout the entire process. When I input from the form
So I'm reading up on character encoding in XML documents as I think
this is the problem (after the many helpful suggestions on this list).
With regards to your second question; no, I'm not sure if I'm using
proper utf-8 througout the entire process. When I input from the form
I'm converti
I've been setting the
here's some output:
Starters
soupe au pistou with amaranth and grana
breadcrumbs
farm lettuces with reed avocado,
crème fraîche, radish and cilantro
On the second item, this
jonathan wrote:
the real characters (presumably è) won't render correctly.
Are you outputting the correct character set information (UTF-8), and
are you sure that UTF-8 is being used throughout the entire process?
--
Jasper Bryant-Greene
General Manager
Album Limited
a: Freepost Album, PO B
the real characters (presumably è) won't render correctly.
it seems like there should be a set of functions for encoding this to
a different but understandable format and then another function for
decoding and display within a browser.
it makes me not want to use DOM for creating xml files.
are there php functions to change from these different formats as
&#e8; doesn't seem to render correctly in a browser. ugghhh.
-jonathan
On Oct 13, 2005, at 4:53 AM, cc wrote:
è
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
maybe i should have said: è is not an _xml_ entity.
i m not very sure.
sorry.
`è' is an html entity,
represents the letter `è' in iso-8859-1 charset,
which have ascii value of 0xe8 .
to have it recognized by libxml, there are 3 ways to do this:
1, &#e8;
2, è
3, è
1 can be saved using either utf-
On 13 Oct 2005, at 07:24, cc wrote:
both `è' and `î' are not entities in charset utf-8, use
`è' and `î' instead.
I would expect that to result in unconverted entities in the output.
If you're intending to send that content as HTML, then I guess that
would be OK. However, if yo
both `è' and `î' are not entities in charset utf-8, use
`è' and `î' instead.
On 10/13/05, jonathan <[EMAIL PROTECTED]> wrote:
> I'm now getting this error:
>
> XML Parsing Error: undefined entity
>
> with the following entity at the first ampersand:
> farm lettuces with reed avocado,
12 matches
Mail list logo
