setup-en.pdf

setup-en.pdf

[Wolfgang Werners-Lucchini]

Hallo!

I searched some of the first (p. 8-9) commands used in 'the details'
in setup-en.pdf.

But I didn't found

\showgridboxes
\setlayer
\definelayer
\layoutcolumnoffset
...

Shouldn't be ALL the commands listet in setup-en.pdf?
How is this document created?

Wolfgang

Re: setup-en.pdf

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 1150 bytes --]

2006/10/10, Wolfgang Werners-Lucchini <wwl@musensturm.de>:
>
> Hallo!
>
> I searched some of the first (p. 8-9) commands used in 'the details'
> in setup-en.pdf.
>
> But I didn't found
>
> \showgridboxes
> \setlayer
> \definelayer
> \layoutcolumnoffset
> ...
>
> Shouldn't be ALL the commands listet in setup-en.pdf?
> How is this document created?
>
> Wolfgang



Hi Wolfgang,

all setup-xx.pdf document created with the x-set-12 module and
the current interface language. A short guirt to create the command
index is avaliable in the Tip-Trick manual.

The data for the manuals stored in the cont-xx.xml files and processed
with the x-set-11 module.

If you want to show the setup commands in one of your documents you
need only the x-set-11 module, if you want create a command index
you need the x-set-12 module which reads the x-set-11 module itself.

To show the commads listed above from you, you can on first create
a new xml-file with the settings from the command or to write the command
with the options in verbatim mode.

The easiest way to find out how Hans did it in the details manual is to look
into the source by yourself.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1696 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

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

Re: setup-en.pdf

[Patrick Gundlach]

Hi,

> I searched some of the first (p. 8-9) commands used in 'the details'
> in setup-en.pdf.
>
> But I didn't found
>
> \showgridboxes
> \setlayer
> \definelayer
> \layoutcolumnoffset
> ...
>
> Shouldn't be ALL the commands listet in setup-en.pdf?

Well, all user commands at least. Please also take a look at 
http://wiki.contextgarden.net/Command_Syntax/Missing
and if you have some time, please edit this.

Patrick
-- 
ConTeXt wiki and more: http://contextgarden.net

an encoding for turkish

[R. Ermers]

Hi,

I am preparing a document in xml docbook. The general output  with 
Context is fine.

However, in my main text (Dutch) I use some Turkish as well. Next to the 
xml-editor, I use Textpad, whose unicode support is not optimal, so  for 
the time being I save the file in iso 8859-9. This encoding is identical 
to latin-1, but with the 6 symbols ETH, eth, THORN, thorn, Yacute, 
yacute replaced by Gbreve, gbreve, Scedilla, scedilla, Idotabove, 
dotlessi (see e.g. http://www.gar.no/home/mats/8859-9.htm).

Now I can't figure out which encoding to use in my Context document (I 
also considered using a code in the xml, but that is not a very 
attractive idea). Do we need to set up a separate coding for Turkish 
(like for Polish, Slowak and Romanian)?

The next step will be to

Regards,

Robert

Re: an encoding for turkish

[Mojca Miklavec]

On 10/11/06, R. Ermers wrote:
> Hi,
>
> I am preparing a document in xml docbook. The general output  with
> Context is fine.
>
> However, in my main text (Dutch) I use some Turkish as well. Next to the
> xml-editor, I use Textpad, whose unicode support is not optimal, so  for
> the time being I save the file in iso 8859-9. This encoding is identical
> to latin-1, but with the 6 symbols ETH, eth, THORN, thorn, Yacute,
> yacute replaced by Gbreve, gbreve, Scedilla, scedilla, Idotabove,
> dotlessi (see e.g. http://www.gar.no/home/mats/8859-9.htm).

In "usual .tex" document \enableregime[iso-8859-1] or simply
\enableregime[latin5] or "il5" should work. I don't use xml docbook,
so I have no idea how to set it there, but I assume that you'll find a
way to create your own conversion.

> Now I can't figure out which encoding to use in my Context document (I
> also considered using a code in the xml, but that is not a very
> attractive idea). Do we need to set up a separate coding for Turkish
> (like for Polish, Slowak and Romanian)?

ec should be fine apart from the fact that in some fonts (lmodern)
there is "scommaaccent" and in others (iwona) "scedilla" on the same
slot. If you have bad luck (if you want to use a font which has
scommaaccent instead of scedilla):
- you can redefine scedilla to be composed from s and cedilla, but
then you loose proper hyphenation of words containing scedilla
- you can use another font or hack a bit (try whether it works if you
replace scommaaccent with scedilla in ec-lm.map files)
- you can wait for the new version of pdfTeX

> The next step will be to

... to finish the sentence perhaps? ;) No, just joking.

Mojca

Re: an encoding for turkish

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 1153 bytes --]

2006/10/11, R. Ermers <r.ermers@hccnet.nl>:
>
> Hi,
>
> I am preparing a document in xml docbook. The general output  with
> Context is fine.
>
> However, in my main text (Dutch) I use some Turkish as well. Next to the
> xml-editor, I use Textpad, whose unicode support is not optimal, so  for
> the time being I save the file in iso 8859-9. This encoding is identical
> to latin-1, but with the 6 symbols ETH, eth, THORN, thorn, Yacute,
> yacute replaced by Gbreve, gbreve, Scedilla, scedilla, Idotabove,
> dotlessi (see e.g. http://www.gar.no/home/mats/8859-9.htm).
>
> Now I can't figure out which encoding to use in my Context document (I
> also considered using a code in the xml, but that is not a very
> attractive idea). Do we need to set up a separate coding for Turkish
> (like for Polish, Slowak and Romanian)?
>
> The next step will be to
>
> Regards,
>
> Robert



Hi Robert,

se easiest way would be to save your document in unicode-encoding
and process it with \enableregime[utf] in ConTeXt.

I use Textpad sometimes by myslf, but I prefer emeditor because it support
more encodings and has built-in syntax hyghligting for TeX.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1647 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

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

Re: an encoding for turkish

[Hans Hagen]

R. Ermers wrote:
> Hi,
>
> I am preparing a document in xml docbook. The general output  with 
> Context is fine.
>
> However, in my main text (Dutch) I use some Turkish as well. Next to the 
> xml-editor, I use Textpad, whose unicode support is not optimal, so  for 
> the time being I save the file in iso 8859-9. This encoding is identical 
> to latin-1, but with the 6 symbols ETH, eth, THORN, thorn, Yacute, 
> yacute replaced by Gbreve, gbreve, Scedilla, scedilla, Idotabove, 
> dotlessi (see e.g. http://www.gar.no/home/mats/8859-9.htm).
>
> Now I can't figure out which encoding to use in my Context document (I 
> also considered using a code in the xml, but that is not a very 
> attractive idea). Do we need to set up a separate coding for Turkish 
> (like for Polish, Slowak and Romanian)?
>   
use utf8 

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

Re: setup-en.pdf

[Jano Kula]

> 
> Well, all user commands at least. Please also take a look at 
> http://wiki.contextgarden.net/Command_Syntax/Missing
> and if you have some time, please edit this.
> 

Hi,

so there is

http://wiki.contextgarden.net/Command_Syntax/Missing

and

http://wiki.contextgarden.net/Bugs_and_workarounds
(Missing items in texshow web)

Do they relate together?

Jano

Re: setup-en.pdf

[Patrick Gundlach]

Hi,

> so there is
>
> http://wiki.contextgarden.net/Command_Syntax/Missing
>
> and
>
> http://wiki.contextgarden.net/Bugs_and_workarounds
> (Missing items in texshow web)
>
> Do they relate together?

I've put the contents from the Bugs_and_workarounds page to the
Command_Syntax/Missing and made a link.

Patrick
-- 
ConTeXt wiki and more: http://contextgarden.net