ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Jean-Philippe Rey <jean-philippe.rey@centralesupelec.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX and addplot table
Date: Sat, 12 Dec 2020 17:01:02 +0100	[thread overview]
Message-ID: <4e53ae24-fcaa-9348-c3f2-254964edb3f0@xs4all.nl> (raw)
In-Reply-To: <15F67B25-2C61-47FD-B228-809CCC3FAE81@centralesupelec.fr>

On 12/12/2020 3:35 PM, Jean-Philippe Rey wrote:

> By default, pgfplotstable breaks lines at white space (tab or space 
> according to the pgfplotstable manual). I used tabs as column separators 
> in my demo file. With MKiV, the columns are correctly split but with 
> LMTX, pgfplotstable sees a single column.
> 
> I explicitly stated that the columns are separated with tabs:
> 
> \addplot table [x=t, y=E, col sep=tab] {mfe-addplot.dat};
> 
> and it works. I tried to change the columns separator to a space, 
> instead of a tab and it also works.
> 
> I don't know what pgfplotstable uses to split columns, but the 
> conclusion is that with MkIV 'col sep=space' means space or tab, whereas 
> with LMTX it means strictly a space character.
> 
> Thank you very much for your help.
I think I have it running now but you have to wait for an update (one of 
those curious border cases where tex bends a rule by turning tabs into 
spaces (the alternative is to let the tab token flagged as spacer travel 
around which would permits round trip). Makes me wonder I should have 
that as option in luametatex (but as I'm now in metapost mode I delay 
that pondering.)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-12-12 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12  9:36 Jean-Philippe Rey
2020-12-12 10:58 ` Hans Hagen
     [not found]   ` <EB02BBB4-B1B6-45B9-BAA1-0729B3651B32@centralesupelec.fr>
2020-12-12 12:20     ` Hans Hagen
2020-12-12 12:28       ` Wolfgang Schuster
2020-12-12 14:35       ` Jean-Philippe Rey
2020-12-12 16:01         ` Hans Hagen [this message]
2020-12-12 16:03         ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4e53ae24-fcaa-9348-c3f2-254964edb3f0@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=jean-philippe.rey@centralesupelec.fr \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).