ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: UTF-8 characters and gnuplot module
Date: Wed, 26 Mar 2008 09:05:02 +0100	[thread overview]
Message-ID: <47EA03AE.5040600@elvenkind.com> (raw)
In-Reply-To: <6faad9f00803250755o60bfa9b5i9f1341ce636d3626@mail.gmail.com>

Hi,

This thread is a bit confusing to me, so if there is an actual
question to me, someone has to rephrase it (and keep in mind
that I have not used gnuplot in 'ages').

Mojca Miklavec wrote:
> 
> set ylabel "h\dochar {233}llo"

Should this not be

   set ylabel "h\\dochar {233}llo"

because of GNUplot's own double-quoted string parsing?
Independent of expansion in \startGNUPLOTscript, I mean?

Speaking as the maintainer of Metapost, assuming 'plain.mp':
you should be able to use UTF-8 in btex ... etex under the
following (narrow) conditions:

* you have set up the verbatimtex .. etex properly so that your
   macro package nows how to handle the UTF-8 input;
* your tex engine generates DVI files
* the resulting fonts that are used in that DVI are TFM-based.

For context, that would mean mkii pdftex with \enableregime[utf],
but in that case, you are much better off using \textext.

You cannot have UTF-8 in literal metapost label strings, because
Metapost only knows about traditional TFM fonts (single byte).

Best wishes,
Taco


___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2008-03-26  8:05 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
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 [this message]
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=47EA03AE.5040600@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).