ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Tomáš Pustelník" <xPustelnikT@seznam.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: czech sorting in MiIV
Date: Sat, 15 May 2010 21:57:02 +0200	[thread overview]
Message-ID: <0989CC2344704AE5A8E8169631832C3D@PustaPC> (raw)
In-Reply-To: <4BEEF932.4020100@wxs.nl>

--------------------------------------------------
From: "Hans Hagen" <pragma@wxs.nl>
Sent: Saturday, May 15, 2010 9:42 PM
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: "Tomáš Pustelník" <xPustelnikT@seznam.cz>
Subject: Re: [NTG-context] czech sorting in MiIV

> On 15-5-2010 8:14, Tomáš Pustelník wrote:
>> Also I have question. In my bachelor thesis I'm describe language
>> support for ConTeXt and when I tried add some experimental language into
>> ConTeXt (I define system constants and add \loadcorefile{lang-exp} to
>> context.mkii and context.mkiv) and when generating format for MkII
>> everything was ok but for MkIV ConTeXt complained he can't find file
>> lang-exp.tex (I paste it in base folder to other source codes). Any idea
>> whats wrong? In MkIV must I change something else as well?
>
> Ah .. you look in the wrong spot. There's a file:
>
>   mult-def.lua
>
> and interfaces are defined there. I generate the mult-* files using
>
>   mtxrun interface --context
>
> Now, if you just want to experiment, you need to patch mult-def.lua.
>
> You can make a mult-def-mine.lua:
>
>   local t = require "mult-def.lua"
>
>   t.commands.framed.xx = "frmd"
>
>   -- print(table.serialize(t.commands.framed))
>
>   return t
>
> I patched mtx-interface.lua so that you can say;
>
>   mtxrun interface --context mult-def-mine.lua
>
> There is also --messages for the message files.
>
> Of course you have to make a cont-xx.tex file as well.
>
> Hans

Thank you, this will be handy (actually I was planing to ask about user 
interface as well). But what I had in mind was new language definition (like 
lang-sla, lang-ger and so on), perhaps I could be more precise.

But anyway, thanks. As I said, I will use this as well.

Tomas P. 

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-05-15 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15 12:49 Tomáš Pustelník
2010-05-15 14:36 ` Hans Hagen
     [not found]   ` <C2085EAC0564469697D403B18588D367@PustaPC>
     [not found]     ` <4BEECACA.3080000@wxs.nl>
     [not found]       ` <EEB1DCB3F8F9454AB4CBAA3DF6DBFA3F@PustaPC>
     [not found]         ` <4BEED963.9030104@wxs.nl>
2010-05-15 18:14           ` Tomáš Pustelník
2010-05-15 19:42             ` Hans Hagen
2010-05-15 19:57               ` Tomáš Pustelník [this message]
2010-05-16  3:08             ` Aditya Mahajan
2010-05-16  8:51               ` Tomáš Pustelní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=0989CC2344704AE5A8E8169631832C3D@PustaPC \
    --to=xpustelnikt@seznam.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).