[prev in list] [next in list] [prev in thread] [next in thread]
List: xml-cocoon-users
Subject: 2.1.13 sqltransformer entities
From: "Lochschmied, Alexander" <Alexander.Lochschmied () vishay ! com>
Date: 2017-01-30 8:16:57
Message-ID: 852DD8A9FDDF734C809AC3CFCFDE8695015C1349F6 () WSMV115 ! corp ! vishayint ! com
[Download RAW message or body]
We upgraded recently from 2.1.11 to some 2.1.13 version from SVN (as we upg=
raded machines to Java 8).
Now entities in our MySQL DB seem to be treated differently. So for example=
we see ® in our resulting HTML pages now instead of the corresponding=
"registered trademark" symbol. A workaround seems to be having the DB cont=
ent start with an (empty) XML comment for example.
Is there a way to get back the old behaviour so we won't have to apply this=
workaround to all our data?
Thanks,
Alexander
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">We upgraded recently from 2.1.11 to some 2.1.13 version from SVN \
(as we upgraded machines to Java 8).<o:p></o:p></p> <p class="MsoNormal">Now entities \
in our MySQL DB seem to be treated differently. So for example we see &#174; in \
our resulting HTML pages now instead of the corresponding “registered \
trademark” symbol. A workaround seems to be having the DB content start with \
an (empty) XML comment for example.<o:p></o:p></p> <p \
class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Is there a way to get \
back the old behaviour so we won’t have to apply this workaround to all our \
data?<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Alexander<o:p></o:p></p>
</div>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic