ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "Ethan Merritt" <merritt@u.washington.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Peter Hedwig <peter@affenbande.org>
Subject: Re: UTF-8 characters and gnuplot module
Date: Mon, 24 Mar 2008 21:14:15 +0100	[thread overview]
Message-ID: <6faad9f00803241314m467aeec8hc590f2c0f8ef86b1@mail.gmail.com> (raw)
In-Reply-To: <200803241152.20110.merritt@u.washington.edu>

On Mon, Mar 24, 2008 at 7:52 PM, Ethan Merritt <merritt@u.washington.edu> wrote:
> On Monday 24 March 2008 08:53, Mojca Miklavec wrote:


>  > PS: I'm CC-ing to Ethan in case he has some proposal about what could
>  > be done with metapost terminal to support UTF-8 (one of the best thing
>  > to do would be to remove cmr, but more is needed), and I'm CC-ing to
>  > the developer of the new TikZ terminal (for no specific reason).
>
>  Gnuplot's metapost terminal correctly passes through UTF-8 characters
>  to the output.

That's right.

>  Metapost itself then mangles them.

That's also right. Actually, "btex label etex" which calls TeX (in an
extremely inefficient way, among other things) is the one that doesn't
know how to handle them. It would be nice if someone from this mailing
list had at least some idea if that is solvable or not.

Maybe harcoding utf-8 it into mptopdf could help, but that's far from
being a nice solution, and has other undesired side-effects, so it's
probably not really desired.

Yet another solution would be to add some more commands to verbatimtex
... etex, but I don't see how to do that in some portable way. For
example, metapost terminal already tries to be clever in some cases,
and then loads obsolete (not to say
not-existing-any-more-on-my-computer) fonts.

>  If there is some
>  additional keyword or command that gnuplot could emit that would allow
>  metapost to do better, please let me know.

OK, I will let you know if someone will come up with some idea.

>  Otherwise I think this
>  problem must be resolved by using a different toolchain, one that is
>  UTF-8 aware.
>
>  Mojca:
>
>   If the context terminal allows UTF-8 strings to be properly handled
>  by TeX, for me that's a strong argument in favor of including it in the
>  next gnuplot release.  Does it?

Of course. "Anything" that ConTeXt suports can be supported in those
labels now, including UTF-8. UTF-8 was one of the main reasons why
PostScript terminal was almost out of question for me.
Two years ago Hans and Taco "could not sleep" because of my requests &
complaints, and they have made some major (great) improvements in
ConTeXt and metapost code: labels processing became more reliable and
about 100 times faster, and will improve even more with TeX Live 2008
and mplib.

Those improvements are also the main reason why terminal didn't work
in teTeX (but should work without problems in TeX Live 2007, which
should become part of most Linux distributions by now).


If you are willing to consider inclusion of the context terminal - may
I ask you for your opinion about this terminal as well:
     http://peter.affenbande.org/gnuplot/

We're having some conversation with Peter about the possibilities to
make his Lua-based TikZ terminal portable across plain
TeX/LaTeX/ConTeXt formats, while TikZ itself is portable across
dvips/pdfTeX (LuaTeX)/XeTeX engines. His terminal is much more popular
than mine (there are more LaTeX users around than there are ConTeXt
users), but the terminal has a dependency on Lua.

However, any further conversation about this should better be moved
off-list or to gnuplot-beta.

Thanks a lot,
     Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-03-24 20:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 14:38 Morgan Brassel
2008-03-24 15:53 ` Mojca Miklavec
2008-03-24 16:03   ` Mojca Miklavec
2008-03-24 16:35   ` Morgan Brassel
2008-03-24 17:21     ` Mojca Miklavec
2008-03-24 18:52   ` Ethan Merritt
2008-03-24 20:14     ` Mojca Miklavec [this message]
2008-03-24 22:02       ` Hans Hagen
2008-03-24 22:21         ` Mojca Miklavec
2008-03-24 22:43           ` Hans Hagen
2008-03-25 14:28             ` Morgan Brassel
2008-03-25 14:55               ` Mojca Miklavec
2008-03-25 15:57                 ` Morgan Brassel
2008-03-25 17:11                   ` Mojca Miklavec
2008-03-25 20:24                     ` Henning Hraban Ramm
2008-03-26  8:05                 ` Taco Hoekwater
2008-03-26  9:28                   ` Mojca Miklavec
2008-03-24 19:24 ` Mojca Miklavec

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=6faad9f00803241314m467aeec8hc590f2c0f8ef86b1@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=merritt@u.washington.edu \
    --cc=ntg-context@ntg.nl \
    --cc=peter@affenbande.org \
    /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).