ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Martin Kolařík" <martin.kolarik@email.cz>
Subject: Re: Problem with encoding, XML and writetolist...
Date: Mon, 3 Apr 2006 12:36:55 +0200	[thread overview]
Message-ID: <FDEFJKLKHEOCDJPCFCIJAENPDJAA.martin.kolarik@email.cz> (raw)
In-Reply-To: <4430F160.6080204@wxs.nl>

I was confused with typo (ctx=tcx :-) but I still did not succeed. I now installed last cont-tfm, I tried 8bit.tex (from the example) and nothing :-(

I am using now directly "texexec 8bit.tex", which leads to natural.tcx and english interface, without anything more. I tried to change regimes in 8bit.tex too, and the characters were changing. So regimes are OK, result not.

Texexec still reports:

chapter         : 1 ÄluŁou\char 163 c\char 237  kon\char 165  \char 250 p\char 237

which is not good. And I am not able, when not using cp1250.tcx, recode win1250 (default for win) to latin2. There I am able to write regime for myself (cp1250), but I suppose, that whenever characters will not expand to \char XXX form, cp1250.tcx still will be working and usable.

Cannot be set somewhere something badly in my local context configuration?

Thank you,

Martin

-----Original Message-----
From: Hans Hagen [mailto:pragma@wxs.nl]
Sent: Monday, April 03, 2006 11:57 AM
To: martin.kolarik@email.cz; mailing list for ConTeXt users
Subject: Re: [NTG-context] Problem with encoding, XML and writetolist...


Martin Kolařík wrote:
> Aha, here maybe will be the solution :-)
>
> I'am using standalone Win32 distribution from Pragma and I'm running texexec with --translate=cp1252cs. Typescripts use il2, which corresponds to fonts, of course. If I run the code without XML (if I transcribe XML to \chapter etc.) I get toc entry correctly too.
>
> Where should I look for more? What is natural.ctx?
>   
this is a one-to-one translation vector, and the one standard used by context; forget about all those other mappings, they can be done using regimes; you can use an il2 input regime, and any (resonable) font encoding, 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------


_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-04-03 10:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  7:24 Martin Kolařík
2006-02-28  9:15 ` Hans Hagen
2006-02-28  9:33   ` Martin Kolařík
2006-03-31  8:42     ` Martin Kolařík
2006-03-31 17:01       ` Hans Hagen
2006-04-02 21:17         ` Martin Kolařík
2006-04-03  8:36           ` Hans Hagen
2006-04-03  8:57             ` Martin Kolařík
2006-04-03  9:56               ` Hans Hagen
2006-04-03 10:36                 ` Martin Kolařík [this message]
2006-04-03 12:33                   ` Mojca Miklavec
2006-04-03 12:39                     ` Martin Kolařík
2006-04-03 11:18                 ` Vit Zyka
2006-04-03 11:45                   ` Martin Kolařík
2006-04-04 20:18                 ` Martin Kolařík
2006-04-04 20:25                 ` Martin Kolařík
2006-04-05  8:17                   ` Hans Hagen
2006-04-05  9:54                   ` Vit Zyka
2006-04-05 11:03                     ` Hans Hagen
2006-04-05 12:18                       ` Vit Zyka
2006-04-05 14:09                         ` Hans Hagen
2006-04-03 14:25 ` Mojca Miklavec
2006-04-03 14:41   ` Martin Kolařík
  -- strict thread matches above, loose matches on Subject: below --
2006-04-05 11:59 Martin Kolařík
2006-04-06  9:07 ` Hans Hagen
2006-04-02 21:20 Martin Kolařík
2006-02-27 11:58 Martin Kolařík

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=FDEFJKLKHEOCDJPCFCIJAENPDJAA.martin.kolarik@email.cz \
    --to=martin.kolarik@email.cz \
    --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).