Project

Profile

Help

Bug #3491 ยป Bug #10362 - 2017-10-18T08_32_30Z.eml

Community Admin, 2017-10-18 10:32

 
Return-Path: <support@saxonica.com>
Received: from mi031.mc1.hosteurope.de ([80.237.138.224]) by wp245.webpack.hosteurope.de running ExIM with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1e4jlz-0006Uz-J0; Wed, 18 Oct 2017 10:32:19 +0200
Received: from uk1mail2513-b.mymailbank.co.uk ([217.69.43.196]) by mx0.webpack.hosteurope.de (mi031.mc1.hosteurope.de) with esmtp id 1e4jlw-0003J9-A2 for inbox+saxonica+f38e+saxon@plan.io; Wed, 18 Oct 2017 10:32:19 +0200
Received: from [10.0.0.5] (UnknownHost [82.152.109.221]) by uk1mail2513-d.mymailbank.co.uk with SMTP (version=Tls cipher=Aes256 bits=256); Wed, 18 Oct 2017 09:31:54 +0100
Date: Wed, 18 Oct 2017 09:32:08 +0100
From: "support@saxonica.com" <support@saxonica.com>
To: Saxonica Developer Community <inbox+saxonica+f38e+saxon@plan.io>
Message-ID: <514DB843-696D-40C5-A3AF-C32D161A17A3@saxonica.com>
In-Reply-To: <redmine.issue-3491.20171018063938.2ee918d26dc83d6f@plan.io>
References: <redmine.issue-3491.20171018063938@plan.io>
<redmine.issue-3491.20171018063938.2ee918d26dc83d6f@plan.io>
Subject: Re: [Saxon - Bug #3491] (New) In error messages Japanese characters
are displayed as \uXXXX
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="Apple-Mail=_96581FD4-1B5A-489A-B5D6-B74B6A2715DC"
Content-Transfer-Encoding: 7bit
Delivery-date: Wed, 18 Oct 2017 10:32:19 +0200
X-Mailer: Apple Mail (2.2104)
X-HE-Virus-Scanned: Yes
X-HE-Spam-Level: /
X-HE-Spam-Score: 0.1
X-HE-Spam-Report: Content analysis details: (0.1 points) pts rule name
description ---- ----------------------
-------------------------------------------------- 0.1 HTML_MESSAGE BODY: HTML
included in message
Envelope-to: inbox+saxonica+f38e+saxon@plan.io


--Apple-Mail=_96581FD4-1B5A-489A-B5D6-B74B6A2715DC
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

Tricky one. There are two reasons for this:

(a) on many systems, console output doesn't display the characters correc=
tly. It's probably capable of displaying them if configured correctly, bu=
t we have no control over that

(b) errors like this are often caused by using a character that is visual=
ly similar to the required character

Perhaps the right answer is to display it with the real characters follow=
ed by the hex in parentheses.

The other issue is that we are formatting it like this even when the mess=
age is written to an XML validation report. Really we should emit validat=
ion messages with structural markup and then render the markup according =
to the output destination.
> =

> =



> On 18 Oct 2017, at 07:39, Saxonica Developer Community <notifications@p=
lan.io> wrote:
> =

> --- In your reply, please do not write below this line ---
> =

> Issue #3491 <https://saxonica.plan.io/issues/3491?pn=3D1> has been repo=
rted by Gerben Abbink.
> Bug #3491: In error messages Japanese characters are displayed as \uXXX=
X <https://saxonica.plan.io/issues/3491?pn=3D1>
> Author: Gerben Abbink
> Status: New
> Priority: Low
> Assignee:
> Category:
> Sprint/Milestone:
> Legacy ID:
> Applies to branch:
> Fix Committed on Branch:
> Fixed in Maintenance Release:
> I run this demo stylesheet on the command line:
> =

> =

> <xsl:stylesheet version=3D"3.0" xmlns:xsl=3D"http://www.w3.org/1999/XSL=
/Transform">
> <xsl:template match=3D"/" =C3=A9l=C3=A8ve=3D"" =E6=97=A5=E6=9C=AC=3D"">=

> </xsl:template>
> </xsl:stylesheet>
> =

> Saxon reports two errors:
> =

> Attribute =C3=A9l=C3=A8ve is not allowed on element <xsl:template>.
> Attribute \u65e5\u672c is not allowed on element <xsl:template>.
> =

> Why does the second error contain Unicode escape sequences (\uXXXX)? I =
bet Japanese users would like to see Japanese characters in error message=
s, and so do I.
> =

> You have received this notification because you have either subscribed =
to or are involved in a project on Saxonica Developer Community site.
> To change your notification preferences, please click here: https://sax=
onica.plan.io/my/account?tour=3Dmail_preferences <https://saxonica.plan.i=
o/my/account?tour=3Dmail_preferences> =

> =

> This notification was cheerfully delivered by <https://plan.io/> =

> <https://plan.io/>

--Apple-Mail=_96581FD4-1B5A-489A-B5D6-B74B6A2715DC
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html charse=
t=3Dutf-8"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode=
: space; -webkit-line-break: after-white-space;" class=3D""><div class=3D=
"">Tricky one. There are two reasons for this:</div><div class=3D""><br c=
lass=3D""></div><div class=3D"">(a) on many systems, console output doesn=
't display the characters correctly. It's probably capable of displaying =
them if configured correctly, but we have no control over that</div><div =
class=3D""><br class=3D""></div><div class=3D"">(b) errors like this are =
often caused by using a character that is visually similar to the require=
d character</div><div class=3D""><br class=3D""></div><div class=3D"">Per=
haps the right answer is to display it with the real characters followed =
by the hex in parentheses.</div><div class=3D""><br class=3D""></div><div=
class=3D"">The other issue is that we are formatting it like this even w=
hen the message is written to an XML validation report. Really we should =
emit validation messages with structural markup and then render the marku=
p according to the output destination.</div><blockquote type=3D"cite" cla=
ss=3D""><div class=3D"" style=3D"font-family: ProximaNova-Regular, Helvet=
ica, Arial, sans-serif; font-size: 14px; line-height: 1.4em; color: rgb(5=
1, 52, 52);"><table width=3D"100%" cellspacing=3D"0" cellpadding=3D"0" cl=
ass=3D"" style=3D"border-spacing: 0px; border-collapse: collapse; width: =
951px;"><tbody class=3D""><tr class=3D""><td class=3D""><div class=3D""><=
br class=3D""></div></td></tr></tbody></table></div></blockquote><div cla=
ss=3D""><br class=3D""></div><br class=3D""><div><blockquote type=3D"cite=
" class=3D""><div class=3D"">On 18 Oct 2017, at 07:39, Saxonica Developer=
Community &lt;<a href=3D"mailto:notifications@plan.io" class=3D"">notifi=
cations@plan.io</a>&gt; wrote:</div><br class=3D"Apple-interchange-newlin=
e"><div class=3D"">


<!--[if !mso]><!-- -->
<link href=3D"https://assets.plan.io/stylesheets/fonts.css" rel=3D"styles=
heet" type=3D"text/css" class=3D"">
<!--<![endif]-->

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8" =
class=3D""><style class=3D"">a:link{color:#0088b7}
a:visited{color:#0088b7}
a:hover{color:#0088b7}
a:active{color:#0088b7}</style>
<div style=3D"font-family:&quot;ProximaNova-Regular&quot;, Helvetica, Ari=
al, sans-serif;font-size:14px;line-height:1.4em;color:#333434" class=3D""=
>
<table width=3D"100%" cellspacing=3D"0" cellpadding=3D"0" style=3D"border=
-spacing:0;border-collapse:collapse;width:100%" class=3D"">
<tbody class=3D""><tr class=3D""><td class=3D"header" style=3D"text-align=
:center;width:100%;font-family:MarketWeb, Helvetica, Arial, sans-serif;fo=
nt-size:0.8em;color:#D7D7D7"><p class=3D"">--- In your reply, please do n=
ot write below this line ---</p></td></tr>
<tr class=3D""><td class=3D"">Issue <a href=3D"https://saxonica.plan.io/i=
ssues/3491?pn=3D1" style=3D"color:#0088b7" class=3D"">#3491</a> has been =
reported by Gerben Abbink.
<hr style=3D"width:100%;height:1px;background:#ccc;border:0;margin:1.2em =
0" class=3D"">
<h1 style=3D"font-family:&quot;ProximaNova-Bold&quot;, Helvetica, Arial, =
sans-serif;font-weight:normal;margin:0px;font-size:1.3em;line-height:1.4e=
m" class=3D""><a href=3D"https://saxonica.plan.io/issues/3491?pn=3D1" sty=
le=3D"color:#0088b7;text-decoration:none" class=3D"">Bug #3491: In error =
messages Japanese characters are displayed as \uXXXX</a></h1>

<ul class=3D""><li class=3D"">Author: Gerben Abbink</li>
<li class=3D"">Status: New</li>
<li class=3D"">Priority: Low</li>
<li class=3D"">Assignee: </li>
<li class=3D"">Category: </li>
<li class=3D"">Sprint/Milestone: </li>
<li class=3D"">Legacy ID: </li>
<li class=3D"">Applies to branch: </li>
<li class=3D"">Fix Committed on Branch: </li>
<li class=3D"">Fixed in Maintenance Release: </li></ul><p class=3D"">I ru=
n this demo stylesheet on the command line:</p><p class=3D""><!--?xml ver=
sion=3D"1.0" encoding=3D"utf-8"?--><br class=3D"">&lt;xsl:stylesheet vers=
ion=3D"3.0" xmlns:xsl=3D"<a href=3D"http://www.w3.org/1999/XSL/Transform"=
class=3D"">http://www.w3.org/1999/XSL/Transform</a>"&gt;<br class=3D""> =
&lt;xsl:template match=3D"/" =C3=A9l=C3=A8ve=3D"" =E6=97=A5=E6=9C=AC=3D=
""&gt;<br class=3D""> &lt;/xsl:template&gt;<br class=3D"">&lt;/xsl:sty=
lesheet&gt;</p><p class=3D"">Saxon reports two errors:</p><p class=3D"">A=
ttribute <code style=3D"font-family:Hack, Consolas, Menlo, &quot;Liberati=
on Mono&quot;, Courier, monospace;font-size:85%;background-color:#ececec;=
word-wrap:break-word;border-radius:3px;padding:0.2em;margin:0" class=3D""=
>=C3=A9l=C3=A8ve is not allowed on element &lt;xsl:template&gt;.<br class=
=3D"">Attribute </code>\u65e5\u672c is not allowed on element &lt;xsl:tem=
plate&gt;.</p><p class=3D"">Why does the second error contain Unicode esc=
ape sequences (\uXXXX)? I bet Japanese users would like to see Japanese =
characters in error messages, and so do I.</p>


<div itemscope=3D"itemscope" itemtype=3D"http://schema.org/EmailMessage" =
class=3D""><div itemscope=3D"itemscope" itemprop=3D"action" itemtype=3D"h=
ttp://schema.org/ViewAction" class=3D""><link itemprop=3D"url" href=3D"ht=
tps://saxonica.plan.io/issues/3491?pn=3D1" class=3D""><meta itemprop=3D"n=
ame" content=3D"View Issue" class=3D""></div><meta itemprop=3D"descriptio=
n" content=3D"View this issue update on Planio" class=3D""></div>

</td></tr>
<tr class=3D""><td class=3D"footer" style=3D"font-size:0.8em;width:100%">=
<hr style=3D"width:100%;height:1px;background:#ccc;border:0;margin:1.2em =
0" class=3D""><p class=3D"">You have received this notification because y=
ou have either subscribed to or are involved in a project on Saxonica Dev=
eloper Community site.<br class=3D"">To change your notification preferen=
ces, please click here: <a class=3D"external" href=3D"https://saxonica.pl=
an.io/my/account?tour=3Dmail_preferences" style=3D"color:#0088b7">https:/=
/saxonica.plan.io/my/account?tour=3Dmail_preferences</a></p></td><td clas=
s=3D""></td></tr>
<tr class=3D""><td class=3D"planio_footer" style=3D"text-align:center;wid=
th:100%;font-family:MarketWeb, Helvetica, Arial, sans-serif;font-size:1.2=
em;color:#D7D7D7"><br class=3D""><div class=3D""><a href=3D"https://plan.=
io/" style=3D"color:#0088b7;color:#D7D7D7;text-decoration:none" class=3D"=
">This notification was cheerfully delivered by</a></div></td><td class=3D=
""></td></tr>
<tr class=3D""><td class=3D"planio_footer_logo" style=3D"text-align:cente=
r;width:100%"><a href=3D"https://plan.io/" title=3D"Planio" style=3D"colo=
r:#0088b7" class=3D""><img src=3D"https://assets.plan.io/images/planio_lo=
go_gray_204x50.png" height=3D"25" width=3D"102" border=3D"0" alt=3D"Plani=
o" style=3D"vertical-align:middle;border:none" class=3D""></a></td></tr>
</tbody></table>
</div>

</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_96581FD4-1B5A-489A-B5D6-B74B6A2715DC--
    (1-1/1)