From: Marc Trius <derpayatz@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Change hyphenation mark
Date: Tue, 26 May 2020 16:30:52 -0500 [thread overview]
Message-ID: <CAKOz1Uf2Getqkz1bJ=3mgrg+87vEug=-V2Lna1aNOKARjaK7VA@mail.gmail.com> (raw)
In-Reply-To: <a34b93ad-c5ee-d0a9-f845-f05c6bc5824d@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2172 bytes --]
Thank you! It makes a big difference. I distinctly remember reading
somewhere that the hyphen character can't be replaced... But it was last
year so I couldn't tell you where.
I have an environment that provides the first ten Hebrew numerals, which I
am using for the front matter:
\def\hebrewnumber#1%
{\ifcase#1 \or א
\or ב
\or ג
\or ד
\or ה
\or ו
\or ז
\or ח
\or ט
\or י
\else -\fi}
\defineconversion[hebrewnumerals][\hebrewnumber]
I assume that the right way to do it, that would allow for more numbers, is
in Lua, the way that Roman numerals are done. Unfortunately I couldn't
quite figure out how to do it. Right now I don't have more than ten pages
of front matter, but if you are willing to help with implementation, I can
explain how Hebrew numerals work.
Thank you,
Marc Trius
On Tue, May 26, 2020 at 3:51 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 5/26/2020 10:17 PM, Marc Trius wrote:
>
> > I would like to use a different hyphenation mark (־, U+05be) in Yiddish,
> > as it is the standard in that language. It's my understanding from
> > reading the wiki that this is currently impossible—I am wondering if
> > there is a hack that could accomplish this.
> It would be pretty bad if we couldn't do that ... but you need to define
> yiddish first (maybe more needs to be setup ... but that's up to you
> tolet us know, labels, what patterns and such).
>
> \installlanguage
> [yiddish]
> [righthyphenchar="05BE,
> righthyphenchar=`*, % for testing
> default=en]
>
> \starttext
>
> \input tufte
>
> \language[yiddish]
>
> \input tufte
>
> \stoptext
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 3074 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-05-26 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 20:17 Marc Trius
2020-05-26 20:51 ` Hans Hagen
2020-05-26 21:30 ` Marc Trius [this message]
2020-05-27 7:59 ` 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='CAKOz1Uf2Getqkz1bJ=3mgrg+87vEug=-V2Lna1aNOKARjaK7VA@mail.gmail.com' \
--to=derpayatz@gmail.com \
--cc=j.hagen@xs4all.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).