From: Philipp Gesang <philipp.gesang@alumni.uni-heidelberg.de>
To: ConTeXt ML <ntg-context@ntg.nl>
Subject: [luatex-fonts] non-ascii filenames in font cache
Date: Sun, 28 Apr 2013 12:04:02 +0200 [thread overview]
Message-ID: <20130428100402.GA7185@phlegethon> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]
Hi Hans,
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.
Also I noticed that as a pattern, [^%w%d] is a bit redundant
since %d is a subset of %w in both string and unicode.utf8.
Regards
Philipp
#!/usr/bin/env texlua
local non_ascii_names = {
[[华文仿宋.ttf]], [[华文细黑.ttf]], [[华文黑体.ttf]],
}
--- [a]: current data-con
--- [b]: include non-ascii (proposed by Dohyun Kim)
--- [c]: with selene unicode
for i = 1, #non_ascii_names do
local name = non_ascii_names[i]
print""
print("[a]", name, string.gsub(string.lower(name), "[^%w%d]+","-"))
print("[b]", name, string.gsub(string.lower(name), "[^%w%d\128-\255]+","-"))
print("[c]", name, unicode.utf8.gsub(unicode.utf8.lower(name), "[^%w%d]+","-"))
end
[-- 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 reply other threads:[~2013-04-28 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 10:04 Philipp Gesang [this message]
2013-04-28 10:56 ` Hans Hagen
2013-04-28 11:17 ` Philipp Gesang
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=20130428100402.GA7185@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).