From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: DocBookInContext & multi-languages (newbie)
Date: Fri, 29 Nov 2002 20:18:40 +0100 [thread overview]
Message-ID: <20021129191840.GB909@scaprea> (raw)
In-Reply-To: <20021129072039.GA7792@mail.inet.hr>
On Fri, Nov 29, 2002 at 08:20:39AM +0100, Gour wrote:
> Hello list!
>
> Since I need to write in DocBook, I was thrilled to find DocBookInContext
> package which enables to map from DocBook to ConTeXt.
>
> I prepared a small article in DocBook and converted it to PDF by:
> texexec --pdf file (I'm running SuSE 8.0 & teTeX).
>
> The problem is that I wanted to include some Croatian national characters in
> the DocBook file, but they are not shown in generated file.
>
> What should I do to be able to have both English & Croatian language in
> ConTeXt?
>
> (In LyX, I would simply use latin-2 encoding and write English & Croatian.)
>
> Usually documents in DocBook have Unicode encoding (UTF-8).
>
> What encoding has to be defined so that conversion DocBook -> ConTeXt will
> work properly?
>
> I also run texexec --make --language=hr,en hr
I would like to know that too :-) I have not yet found the time to
find out how Context deals with encodings. I only have a note that
says that one should do \useXMLfilter [utf], and that I should have a
look at the xtag-utf (which is input by the above command) or enco
files.
I would hope that context develops generic input encoding support, so
that I only have to scan the encoding value in the XML declaration,
and input the appropriate encoding file.
Regards, Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
next prev parent reply other threads:[~2002-11-29 19:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 7:20 Gour
2002-11-29 19:18 ` Simon Pepping [this message]
2002-11-30 20:15 ` Gour
2002-11-30 20:55 ` Bruce D'Arcus
2002-12-01 6:40 ` Gour
2002-12-02 19:46 ` Simon Pepping
2002-12-02 20:30 ` Tobias Burnus
2002-12-02 21:54 ` Hans Hagen
[not found] ` <Pine.LNX.4.44.0212022106550.2205-100000@tom.physik.fu-berl in.de>
2002-12-02 21:59 ` Hans Hagen
2002-12-03 12:48 ` Tobias Burnus
2002-12-03 13:59 ` Willi Egger
[not found] ` <Pine.LNX.4.44.0212031306170.23965-100000@warp9.physik.fu-b erlin.de>
2002-12-03 13:45 ` Hans Hagen
2002-12-02 12:28 ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-02 13:59 ` Gour
2002-12-02 14:43 ` Hans Hagen
2002-12-02 16:36 ` Taco Hoekwater
2002-12-02 17:40 ` Gour
2002-12-02 20:16 ` Simon Pepping
2002-12-02 21:57 ` Hans Hagen
2002-12-03 20:03 ` Simon Pepping
2002-12-03 23:31 ` Hans Hagen
2002-12-04 14:10 ` Gour
2002-12-04 16:31 ` Hans Hagen
2002-12-04 20:08 ` Gour
2002-12-05 0:10 ` multi-languages [UTF-8 Roman and UTF-8 Nagari test files] Richard Mahoney
2002-12-05 11:58 ` DocBookInContext & multi-languages (newbie) / utf Hans Hagen
2002-12-05 12:22 ` Taco Hoekwater
2002-12-05 13:25 ` Hans Hagen
2002-12-05 14:03 ` Tobias Burnus
2002-12-05 19:09 ` Create Type 1 fonts with Indological diacritics and UTF-8 TTF Richard Mahoney
2002-12-06 14:10 ` Hans Hagen
2002-12-06 15:22 ` Docu set Michael Hallgren
2002-12-07 14:12 ` Patrick Gundlach
2002-12-07 17:37 ` Michael Hallgren
2002-12-06 15:36 ` Re: Create Type 1 fonts with Indological diacritics and UTF-8 TTF Gour
2002-12-06 16:47 ` Hans Hagen
2002-12-03 19:14 ` DocBookInContext ... [CSX+, UTF-8 Roman, and Nagari Codings] Richard Mahoney
2002-12-04 14:16 ` Gour
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=20021129191840.GB909@scaprea \
--to=spepping@scaprea.hobby.nl \
--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).