From oinos@gmx.es Tue Feb 9 11:36:45 2016 From: Pablo Rodriguez To: ntg-context@ntg.nl Subject: [NTG-context] wrong xml char handling Date: Tue, 09 Feb 2016 11:36:31 +0100 Message-ID: <56B9C12F.8070205@gmx.es> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6937683354199019836==" --===============6937683354199019836== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Dear list, I’m afraid there may be a bug in betas from February (including the latest one from 2016.02.08 15:35): \startbuffer[demo]

Link: http://a.b/c#d

 \stopbuffer \starttext \startxmlsetups xml:initialize \xmlsetsetup{#1}{p|doc|a}{xml:*} \xmlsetsetup{\xmldocument}{span[@label]}{xml:logo} \stopxmlsetups \xmlregistersetup{xml:initialize} \startxmlsetups xml:doc \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:p \xmlflush{#1}\par \stopxmlsetups \startxmlsetups xml:a \mypersonalurl{\xmlflush{#1}} \stopxmlsetups \def\mypersonalurl#1{\bgroup\tt\goto{% \hyphenatedurl{#1}}[url(#1)]\egroup}% \unexpanded\def\href#1#2{\goto{#2} [url(#1)]} \xmlprocessbuffer{main}{demo}{} \stoptext Output with latest beta: Link: http://a.b/c\Ux {23}d Output with beta from 2016.01.14 09:55; Link: http://a.b/c#d I guess this is a bug. Could anyone else confirm this? Many thanks for your help, Pablo -- http://www.ousia.tk --===============6937683354199019836==-- From pragma@wxs.nl Tue Feb 9 18:03:09 2016 From: Hans Hagen To: ntg-context@ntg.nl Subject: Re: [NTG-context] wrong xml char handling Date: Tue, 09 Feb 2016 18:02:53 +0100 Message-ID: <56BA1BBD.1070103@wxs.nl> In-Reply-To: <56B9C12F.8070205@gmx.es> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3628959834829099281==" --===============3628959834829099281== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On 2/9/2016 11:36 AM, Pablo Rodriguez wrote: > Dear list, > > I’m afraid there may be a bug in betas from February (including the > latest one from 2016.02.08 15:35): > > \startbuffer[demo] > >

Link: http://a.b/c#d

> > \stopbuffer > > \starttext > > \startxmlsetups xml:initialize > \xmlsetsetup{#1}{p|doc|a}{xml:*} > \xmlsetsetup{\xmldocument}{span[@label]}{xml:logo} > \stopxmlsetups > > \xmlregistersetup{xml:initialize} > > \startxmlsetups xml:doc > \xmlflush{#1} > \stopxmlsetups > > \startxmlsetups xml:p > \xmlflush{#1}\par > \stopxmlsetups > > \startxmlsetups xml:a > \mypersonalurl{\xmlflush{#1}} > \stopxmlsetups > > \def\mypersonalurl#1{\bgroup\tt\goto{% > \hyphenatedurl{#1}}[url(#1)]\egroup}% > \unexpanded\def\href#1#2{\goto{#2} [url(#1)]} > > \xmlprocessbuffer{main}{demo}{} > > \stoptext > > Output with latest beta: > > Link: http://a.b/c\Ux {23}d > > Output with beta from 2016.01.14 09:55; > > Link: http://a.b/c#d > > I guess this is a bug. Could anyone else confirm this? fixed in next beta ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- --===============3628959834829099281==-- From oinos@gmx.es Wed Feb 10 12:20:10 2016 From: Pablo Rodriguez To: ntg-context@ntg.nl Subject: Re: [NTG-context] wrong xml char handling Date: Wed, 10 Feb 2016 12:19:53 +0100 Message-ID: <56BB1CD9.5030105@gmx.es> In-Reply-To: <56BA1BBD.1070103@wxs.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0538454474442272033==" --===============0538454474442272033== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 02/09/2016 06:02 PM, Hans Hagen wrote: > On 2/9/2016 11:36 AM, Pablo Rodriguez wrote: >> [...] >> Output with latest beta: >> >> Link: http://a.b/c\Ux {23}d >> >> Output with beta from 2016.01.14 09:55; >> >> Link: http://a.b/c#d >> >> I guess this is a bug. Could anyone else confirm this? > > fixed in next beta Many thanks for the fix. Hans. Sorry for sounding impatient, but since next beta may take longer to be released (because of columnsets), would it be possible to have a patch to use latest released beta? Many thanks for your help, Pablo -- http://www.ousia.tk --===============0538454474442272033==-- From pragma@wxs.nl Wed Feb 10 13:51:43 2016 From: Hans Hagen To: ntg-context@ntg.nl Subject: Re: [NTG-context] wrong xml char handling Date: Wed, 10 Feb 2016 13:51:30 +0100 Message-ID: <56BB3252.2040405@wxs.nl> In-Reply-To: <56BB1CD9.5030105@gmx.es> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4849325587931949787==" --===============4849325587931949787== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit On 2/10/2016 12:19 PM, Pablo Rodriguez wrote: > On 02/09/2016 06:02 PM, Hans Hagen wrote: >> On 2/9/2016 11:36 AM, Pablo Rodriguez wrote: >>> [...] >>> Output with latest beta: >>> >>> Link: http://a.b/c\Ux {23}d >>> >>> Output with beta from 2016.01.14 09:55; >>> >>> Link: http://a.b/c#d >>> >>> I guess this is a bug. Could anyone else confirm this? >> >> fixed in next beta > > Many thanks for the fix. Hans. > > Sorry for sounding impatient, but since next beta may take longer to be > released (because of columnsets), would it be possible to have a patch > to use latest released beta? patch involves more than one line in a few files fwiw: here we never used the latest beta in critical workflows unless tested beforehand (so we always lag a few betas behind) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- --===============4849325587931949787==-- From oinos@gmx.es Wed Feb 10 15:38:31 2016 From: Pablo Rodriguez To: ntg-context@ntg.nl Subject: Re: [NTG-context] wrong xml char handling Date: Wed, 10 Feb 2016 15:38:15 +0100 Message-ID: <56BB4B57.5020100@gmx.es> In-Reply-To: <56BB3252.2040405@wxs.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4794114808508793076==" --===============4794114808508793076== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On 02/10/2016 01:51 PM, Hans Hagen wrote: > On 2/10/2016 12:19 PM, Pablo Rodriguez wrote: >> [...] >> Sorry for sounding impatient, but since next beta may take longer to be >> released (because of columnsets), would it be possible to have a patch >> to use latest released beta? > > patch involves more than one line in a few files OK, this is fine for me. I only asked because I thought it was a simple replacement. > fwiw: here we never used the latest beta in critical workflows unless > tested beforehand (so we always lag a few betas behind) Many thanks for the advice. My workflow isn’t really critical. Sorry, but I’m afraid I don’t earn a living (or even make money) with ConTeXt. I think it makes sense that I work with latest beta. This is the only way I can reasonably test it, so I may report issues that will benefit every ConTeXt user (including myself :-)). But, please, let me know whehter my previous assumption is wrong. Many thanks for your help, Pablo -- http://www.ousia.tk --===============4794114808508793076==-- From pragma@wxs.nl Wed Feb 10 16:33:37 2016 From: Hans Hagen To: ntg-context@ntg.nl Subject: Re: [NTG-context] wrong xml char handling Date: Wed, 10 Feb 2016 16:33:23 +0100 Message-ID: <56BB5843.1050902@wxs.nl> In-Reply-To: <56BB4B57.5020100@gmx.es> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8434036960900876332==" --===============8434036960900876332== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 2/10/2016 3:38 PM, Pablo Rodriguez wrote: > On 02/10/2016 01:51 PM, Hans Hagen wrote: >> On 2/10/2016 12:19 PM, Pablo Rodriguez wrote: >>> [...] >>> Sorry for sounding impatient, but since next beta may take longer to be >>> released (because of columnsets), would it be possible to have a patch >>> to use latest released beta? >> >> patch involves more than one line in a few files > > OK, this is fine for me. I only asked because I thought it was a simple > replacement. > >> fwiw: here we never used the latest beta in critical workflows unless >> tested beforehand (so we always lag a few betas behind) > > Many thanks for the advice. > > My workflow isn=E2=80=99t really critical. Sorry, but I=E2=80=99m afraid I = don=E2=80=99t earn a > living (or even make money) with ConTeXt. > > I think it makes sense that I work with latest beta. This is the only > way I can reasonably test it, so I may report issues that will benefit > every ConTeXt user (including myself :-)). > > But, please, let me know whehter my previous assumption is wrong. sounds ok to me but then you have to wait till i update (one of these days) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- --===============8434036960900876332==--