ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec@guest.arnes.si>
Subject: Re: languages
Date: Fri, 25 Feb 2005 04:09:45 +0100	[thread overview]
Message-ID: <421E96F9.6020007@guest.arnes.si> (raw)
In-Reply-To: <421CBBFD.3050908@wxs.nl>


Hans Hagen wrote:
> Hi,
> 
> Attached is an xml file that describes the hyphenation pattern files. 
> I'd appreciate checking (some records are incomplete). I'd also like to 
> add (for each language) a couple of tricky hyphenatable words [for 
> testing]. Preferable in utf-8 encoding. There is room for more comments 
> as well, like: prefered input and font encodings etc.
> 
> Hans

Leon "Zlajpah should probably be changed to Leon \v{Z}lajpah (or Žlajpah
if in Unicode) (I suppose the information by itself is correct.)

(There's a comment "Use of code page 852 in patterns", which probably 
remained from the "old good DOS times".)

Default encoding? 98% use cp1250, some Linux people use latin2. (well, 
maybe there are still freaks somewhere on this planet using cp852 :)
UTF 8 should be(come) standard, but it is coming pretty slowly.
But writing UTF8 as the default encoding in ConTeXt should be OK.



How can I try it (hyphenation)? I did

\enableregime[utf]
\mainlanguage[sl]
\starttext
Železničar
\showhyphens{Železničar}
\showhyphens{zeleznicar}
\showhyphens{mojca pokrajculja}
\stoptext

It should be že-le-zni-čar (ze-le-zni-car) and moj-ca po-kraj-cu-lja (in 
latex "mojca" is hyphenated wrong anyway), but in ConTeXt the first two 
don't get hyphenated at all and the second one becomes mo-j-ca 
pokra-jcul-ja. I guess the Slovenian patterns are not loaded at all.


One more question about language specific issues: we always write
	1. first section
	2. second section
	2.1. subsection
	2.2. some other subsection
	2.2.1. some subsubsection
(with a dot before the space after every (sub)section). What is the best 
place to store the default settings to? (For all the other Slovenian 
users as well.)


Thank you,
	Mojca

  parent reply	other threads:[~2005-02-25  3:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 17:23 languages Hans Hagen
2005-02-24 11:02 ` languages Vit Zyka
2005-02-24 18:38   ` languages Willi Egger
2005-02-25  3:09 ` Mojca Miklavec [this message]
2005-02-25 10:04   ` languages Hans Hagen
2005-02-25 11:06     ` Latin5 regime luigi.scarso
2005-02-25 11:36       ` Hans Hagen
2005-02-25 12:21         ` luigi.scarso
2005-02-25 21:48 ` languages VnPenguin
2005-02-27 10:23   ` languages h h extern
  -- strict thread matches above, loose matches on Subject: below --
2021-07-18 14:39 languages Hans van der Meer
2021-07-18 19:37 ` languages Wolfgang Schuster
2002-02-06 16:34 Languages Giuseppe Bilotta
2002-02-06 18:41 ` Languages Henning Hraban Ramm
2002-02-07  0:00 ` Languages Bruce Horrocks
2002-02-07  6:34   ` Languages Dan Seracu
2002-02-07 19:52 ` Languages Alberto Nespoli
2000-05-31  8:41 Languages Dan Seracu
2000-05-31 10:01 ` Languages 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=421E96F9.6020007@guest.arnes.si \
    --to=mojca.miklavec@guest.arnes.si \
    --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).