ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Giuseppe Bilotta" <oblomov@freemail.it>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: TeXshow
Date: Thu, 8 Feb 2001 14:05:19 +0100	[thread overview]
Message-ID: <005901c09217$96dc58a0$a3ccfea9@nuovo> (raw)
In-Reply-To: <3.0.6.32.20010208111209.019e95d0@server-1>

> >
> >I think Hans has a perl script that creates the tws files from the
> >same setup files that define the commands in the manual (setupb & 
> >mult-con/mult-com).
> 
> No. Just the undocumented crap file setup.d.tex (attached). Run it with 
> 
>   texexec --interface=.. setupd 
> 

Done. Works.

Well, except that whatever interface I choose I always get
cont-en.tws (even if the contents are the correct ones; I just need
to rename it to cont-[interface].tws).

Btw, playing with TeXShow I found a bug related to commands having
the same names in all languages: the first language with that command
is selected! An example:

\mar is \mar in de, nl, en, it but \okr in cz

If I'm browsing the italian interface and select \mar I get the
correct description; but if I then want to change interface
(e.g. to know how "\mar" is called in english) I end up
in the german interface, which I don't want.

Also, if I run "texshow mar it" I end up in cont-de again
(I assume that the same routine is causing the error)

And one more: I created cont-it.tws, it works fine, but it still says
"command", "dimension" etc instead of the italian forms; which file should
I localize? [and btw, Hans, did you receive my mail with the localizations
bug fixes for italian?]

Giuseppe Bilotta

Using Microsoft products is like 
having sex without condoms---but
much less pleasurable


  reply	other threads:[~2001-02-08 13:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Hans Hagen's message of "Thu, 08 Feb 2001 11:12:09 +0100">
2001-02-07 14:11 ` TeXshow Giuseppe Bilotta
2001-02-08  8:01   ` TeXshow Taco Hoekwater
2001-02-08 10:12     ` TeXshow Hans Hagen
2001-02-08 13:05       ` Giuseppe Bilotta [this message]
2001-02-08 14:29       ` TeXshow Ed L Cashin
2001-02-08 15:24         ` TeXshow Hans Hagen
2001-02-08 10:05   ` TeXshow Hans Hagen
2001-02-08 12:45     ` TeXshow Giuseppe Bilotta
2001-02-09  8:37       ` TeXshow / status context Hans Hagen
2001-02-11  1:39         ` TeXCalc Taco Hoekwater
2001-02-11  9:48           ` TeXCalc Frans Goddijn
2001-02-11 12:41             ` TeXCalc Taco Hoekwater
2001-02-11 12:58               ` TeXCalc Frans Goddijn
     [not found] <mailman.879.1259942388.22155.ntg-context@ntg.nl>
2009-12-04 23:29 ` texshow Wolfgang Werners-Lucchini
     [not found] <mailman.3.1259924403.8230.ntg-context@ntg.nl>
2009-12-04 15:57 ` texshow Wolfgang Werners-Lucchini
2009-12-04 16:02   ` texshow Wolfgang Schuster
     [not found] <mailman.860.1259862604.22155.ntg-context@ntg.nl>
2009-12-03 22:02 ` texshow Wolfgang Werners-Lucchini
2009-12-03 22:16   ` texshow Wolfgang Schuster
2009-12-04 23:39     ` texshow luigi scarso
2009-12-05  9:25       ` texshow Hans Hagen
2009-12-02 10:18 texshow Wolfgang Werners-Lucchini
2009-12-03 17:24 ` texshow Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2003-10-04  7:42 texshow (was: keywords) Steffen Wolfrum
2003-10-05 19:41 ` texshow Henning Hraban Ramm
2000-11-23 16:22 texshow 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='005901c09217$96dc58a0$a3ccfea9@nuovo' \
    --to=oblomov@freemail.it \
    --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).