ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: BPJ via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: BPJ <bpj@melroch.se>
Subject: Fonts for transliteration (was: Critical Editions?)
Date: Sun, 9 Jan 2022 17:18:06 +0100	[thread overview]
Message-ID: <CADAJKhD+RbtJ6jSAKHn7nfU0TD39z_bmvgxL8VDAiPVs8+9WxA@mail.gmail.com> (raw)
In-Reply-To: <E992603E-4733-4F6C-8A32-4FBC239B4FE7@hccnet.nl>


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

Den sön 9 jan. 2022 13:22Robert via ntg-context <ntg-context@ntg.nl> skrev:

> Dear list,
>
> I am currently working on a critical edition as well, and follow the
> discussion with interest. For the time being, I prefer Latex over Context
> for this project.
>
> In addition to Jürgen's remarks on transcription fonts, a small
> contribution:
>
> Arabists and turcologists working with transcriptions used to have similar
> problems. In the nineties I adapted existing postscript fonts with
> Fontographer. I also made sure to copy kerning information from extant
> letters (e.g. a) to new ones (e.g. ā) with the required diacritic (usually
> dots, dashes and haceks). This was in the pre-unicode era.
>
> Today there is the Brill font which is quite extended, yet I am not sure
> if it can be used freely in other publications.
>
> Adapations to extant fonts can still be made with the open source app
> FontForge. Do not hesitate to contact me offline if you need help on this.
>

The technically excellent free Google Noto Serif/Sans/Sans Mono fonts have
quite extensive coverage of Latin/Greek/Cyrillic scripts. As an
Indo-Europeanist turned programmer/editor/translator doing frequent forays
into Uralic and Afroasiatic when wearing a more general historical
linguistics hat I have found nothing missing.
(If you need a Mono Font make sure to use Noto Sans Mono which has better
coverage than Noto Mono!)

https://fonts.google.com/noto

Much the same can be said of the Charis SIL font from SIL International,
although the current release lags behind Noto when it comes to coverage.

https://software.sil.org/charis/

(Make sure to look at the downloads page for info on downloadable
customized fonts!)

There is also the Gentium SIL font with Greek and Cyrillic coverage as well
as Latin, although its design may be a bit too swashy for academic work.

If something *is* missing these are all licensed under the quite permissive
Open Font License

https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL-FAQ_web

Publishers may have their own (ideas about) fonts but for course materials,
handouts, manuscripts, databases and the like these are excellent. I do all
my work in the Vim text editor (with Noto Sans Mono) and *TeX/Pandoc.

Regards,

/Benct



> Regards,
>
> Robert
>
> info@mo-perspectief.nl
>
>
> > Op 9 jan. 2022, om 11:23 heeft hanneder--- via ntg-context <
> ntg-context@ntg.nl> het volgende geschreven:
> >
> > I was just writing a mail (below) and saw:
> >
> >> They do indic scripts and Kai made the first version of the devanagari
> code for the context fontloader code that I then optimized.
> >
> > Fascinating. Where can I learn more about that or is that
> > user-unfriendly (my technical knowledge is rather limited).
> >
> >
> > Dear Hans,
> >
> > two recurring problems are rather specifically Indological and they
> concern hyphenation and
> > font.
> >
> > 1. In Sanskrit prose it is possible to produce compounds that span a few
> lines. The concept of
> >   "word" or "word division" fails here, as are the TeX mechanisms.
> >
> >   What we need in practice would be a "hyphenation" for the language
> Sanskrit that hyphenates
> >   after all Sanskrit vowels (in transcription this would be a, ā, i, ī,
> u, ū, ṛ, ḷ, e, o, ai, au. The
> >   last two cannot be split, "au" is one vowel with one vowel sign in the
> original script). Of
> >   course, we want to improve this automatic spelling occasionally, so we
> need to be able to insert
> >   a \- without thereby disabling the hyphenation for this compound.
> >
> >   I think in critical editions the problem of the disabled hyphenation
> also arises when a variant
> >   is added inside a word. In any case hyphenation is a real nuisance in
> critical editions.
> >
> > 2. Fonts that contain all necessary diacritics have become sparse. (This
> is more a lamentation, not
> >   much one can do about it, I guess).
> >
> >   When I started TeXing people were used to writing aṭavī as
> a\d{t}av{\=\i}. Not user friendly,
> >   but it worked with many fonts. With each new font regime Sanskritists
> had to search for new
> >   fonts, invent work-arounds etc. Even the most promising attempts (I
> spent a lot of time with
> >   OmegaTeX) eventually disappeared. Now we are dependent on whether an
> otf font has the underdot
> >   characters (ṭḍṃḥ) and the vowels (āīūṛ). Within the commercial fonts,
> I found only one
> >   "Brotschrift" that worked, which is Adobe Text Pro. I really like
> Minion, for instance, but the
> >   latest otf Version has no ṭ etc.
> >
> >   Thank god, we have many TeX fonts derived from older ones that still
> work, but many entries in
> >   the TeX Font Catalogue do not!
> >
> >
> > Jürgen
> >
> >
> >
> >
> > ---
> >
> > Prof. Dr. Juergen Hanneder
> > Philipps-Universitaet Marburg
> > FG Indologie u. Tibetologie
> > Deutschhausstr.12
> > 35032 Marburg
> > Germany
> > Tel. 0049-6421-28-24930
> > hanneder@staff.uni-marburg.de
> >
> >
> ___________________________________________________________________________________
> > 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
> >
> ___________________________________________________________________________________
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 9129 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
___________________________________________________________________________________

  reply	other threads:[~2022-01-09 16:18 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  9:50 Critical Editions? hanneder--- via ntg-context
2021-12-21 10:06 ` Denis Maier via ntg-context
2021-12-21 10:51   ` Henning Hraban Ramm via ntg-context
2021-12-24 12:07 ` Hans Hagen via ntg-context
2021-12-24 16:39   ` Bruce Horrocks via ntg-context
2022-01-03  9:43     ` hanneder--- via ntg-context
2022-01-03 10:32       ` Jean-Pierre Delange via ntg-context
2022-01-03 13:37       ` Jean-Pierre Delange via ntg-context
2022-01-03 20:46         ` STIX2 font issues with freshly installed FMTX Heinrich Paeßens via ntg-context
     [not found]           ` <C24ABDC0-DB51-46B8-9D38-4136BE590017@me.com>
     [not found]             ` <3EF0489B-E388-4E1D-A14A-DE46EE607E40@me.com>
2022-01-05 14:03               ` STIX2 font issues with freshly installed LMTX Heinrich Paeßens via ntg-context
2022-01-04 12:38       ` Critical Editions? Thomas A. Schmitz via ntg-context
2022-01-04 17:54         ` Jean-Pierre Delange via ntg-context
2022-01-04 20:02           ` Thomas A. Schmitz via ntg-context
2022-01-04 23:00             ` Jean-Pierre Delange via ntg-context
2022-01-05  8:43               ` luigi scarso via ntg-context
2022-01-05  9:47                 ` Jean-Pierre Delange via ntg-context
2022-01-05 11:54                 ` Pablo Rodriguez via ntg-context
2022-01-05 12:34                   ` Jean-Pierre Delange via ntg-context
2022-01-05 13:06                     ` Jean-Pierre Delange via ntg-context
2022-01-06 16:34                     ` Pablo Rodriguez via ntg-context
2022-01-05 15:43                   ` Henning Hraban Ramm via ntg-context
2022-01-05 16:13                   ` luigi scarso via ntg-context
2022-01-05 17:28                     ` Jean-Pierre Delange via ntg-context
2022-01-05 18:38                       ` Jean-Pierre Delange via ntg-context
2022-01-05 22:15                   ` Jean-Pierre Delange via ntg-context
2022-01-04 12:42       ` Pablo Rodriguez via ntg-context
2022-01-04 11:57 ` Pablo Rodriguez via ntg-context
2022-01-05 11:52   ` hanneder--- via ntg-context
2022-01-05 12:29     ` Jean-Pierre Delange via ntg-context
2022-01-05 17:39       ` hanneder--- via ntg-context
2022-01-05 19:05         ` Aditya Mahajan via ntg-context
2022-01-06 16:31         ` Pablo Rodriguez via ntg-context
2022-01-06 16:57     ` Pablo Rodriguez via ntg-context
2022-01-06 17:47       ` Jean-Pierre Delange via ntg-context
2022-01-06 18:41         ` Hans Hagen via ntg-context
2022-01-06 19:00           ` Henning Hraban Ramm via ntg-context
2022-01-07 17:25             ` hanneder--- via ntg-context
2022-01-07 17:35               ` luigi scarso via ntg-context
2022-01-08 11:40                 ` Jean-Pierre Delange via ntg-context
2022-01-08 13:03                   ` Hans Hagen via ntg-context
2022-01-08 17:28                     ` Jean-Pierre Delange via ntg-context
2022-01-09 10:23                     ` hanneder--- via ntg-context
2022-01-09 11:50                       ` Robert via ntg-context
2022-01-09 16:18                         ` BPJ via ntg-context [this message]
2022-01-10  9:32                           ` Fonts for transliteration (was: Critical Editions?) Denis Maier via ntg-context
2022-01-10 12:28                             ` BPJ via ntg-context
2022-01-10 12:45                               ` Denis Maier via ntg-context
2022-01-09 13:06                       ` Critical Editions? Hans Hagen via ntg-context
2022-01-09 22:41                       ` Hans Hagen via ntg-context
2022-01-09 22:46                       ` Hans Hagen via ntg-context
2022-01-10 11:26                         ` Arthur Rosendahl via ntg-context
2022-01-10 13:31                           ` Jean-Pierre Delange via ntg-context
2022-01-10 14:18                             ` Arthur Rosendahl via ntg-context
2022-01-10 19:06                       ` Hans Hagen via ntg-context
2022-01-11 16:20                         ` Arthur Rosendahl via ntg-context
2022-01-08 17:52                   ` BPJ via ntg-context
2022-01-07 18:31               ` Hans Hagen via ntg-context

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=CADAJKhD+RbtJ6jSAKHn7nfU0TD39z_bmvgxL8VDAiPVs8+9WxA@mail.gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=bpj@melroch.se \
    /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).