From: Philipp Gesang <Philipp.Gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [luatex-fonts] non-ascii filenames in font cache
Date: Sun, 28 Apr 2013 13:17:49 +0200 [thread overview]
Message-ID: <20130428111749.GB8049@phlegethon> (raw)
In-Reply-To: <517D0059.2060206@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 651 bytes --]
···<date: 2013-04-28, Sunday>···<from: Hans Hagen>···
> On 4/28/2013 12:04 PM, Philipp Gesang wrote:
>
> >the font cache currently drops non-ascii bytes when creating file
> >names by means of containers.cleanname(). Dohyun Kim sent a fix
> >for data-con.lua (see below). My own test with the unicode
> >library leads to some odd results.
>
> strange that it wasn't noticed before as it's rather old code
Personally I would rename the files instead of reporting it.
> function containers.cleanname(name)
> return (gsub(lower(name),"[^%w\128-\255]+","-"))
> end
>
> is good enough i guess
Of course, thanks!
Philipp
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-28 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 10:04 Philipp Gesang
2013-04-28 10:56 ` Hans Hagen
2013-04-28 11:17 ` Philipp Gesang [this message]
2013-04-28 12:08 ` Khaled Hosny
2013-04-28 12:15 ` Wolfgang Schuster
2013-04-28 13:08 ` 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=20130428111749.GB8049@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--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).