static int lua_kpathsea_expand_var(lua_State * L)
{
kpathsea *kp = (kpathsea *) luaL_checkudata(L, 1, KPATHSEA_METATABLE);
const char *st = luaL_checkstring(L, 2);
lua_pushstring(L, kpathsea_var_expand(*kp, st));
return 1;
}
string
kpse_var_expand (const_string src)
{
return kpathsea_var_expand (kpse_def,src);
}
string
kpathsea_make_tex (kpathsea kpse, kpse_file_format_type format,
const_string base)
{
kpse_format_info_type spec; /* some compilers lack struct initialization */
string ret = NULL;
spec = kpse->format_info[format];
if (!spec.type) { /* Not initialized yet? */
kpathsea_init_format (kpse, format);
spec = kpse->format_info[format];
}
if (spec.program && spec.program_enabled_p) {
/* See the documentation for the envvars we're dealing with here. */
/* Number of arguments is spec.argc + 1, plus the trailing NULL. */
string *args = XTALLOC (spec.argc + 2, string);
/* Helpers */
int argnum;
int i;
/* FIXME
* Check whether the name we were given is likely to be a problem.
* Right now we err on the side of strictness:
* - may not start with a hyphen (fixable in the scripts).
* - allowed are: alphanumeric, underscore, hyphen, period, plus
* ? also allowed DIRSEP, as we can be fed that when creating pk fonts
* No doubt some possibilities were overlooked.
*/
if (base[0] == '-' /* || IS_DIR_SEP(base[0]) */) {
fprintf(stderr, "kpathsea:make_tex: Invalid filename `%s', starts with '%c'\n",
base, base[0]);
return NULL;
}
for (i = 0; base[i]; i++) {
if (!ISALNUM(base[i])
&& base[i] != '-'
&& base[i] != '+'
&& base[i] != '_'
&& base[i] != '.'
&& !IS_DIR_SEP(base[i]))
{
fprintf(stderr, "kpathsea:make_tex: Invalid filename `%s', contains '%c'\n",
base, base[i]);
return NULL;
}
}
if (format == kpse_gf_format
|| format == kpse_pk_format
|| format == kpse_any_glyph_format)
set_maketex_mag (kpse);
/* Here's an awful kludge: if the mode is `/', mktexpk recognizes
it as a special case. `kpse_prog_init' sets it to this in the
first place when no mode is otherwise specified; this is so
when the user defines a resolution, they don't also have to
specify a mode; instead, mktexpk's guesses will take over.
They use / for the value because then when it is expanded as
part of the PKFONTS et al. path values, we'll wind up searching
all the pk directories. We put $MAKETEX_MODE in the path
values in the first place so that sites with two different
devices with the same resolution can find the right fonts; but
such sites are uncommon, so they shouldn't make things harder
for everyone else. */
for (argnum = 0; argnum < spec.argc; argnum++) {
args[argnum] = kpathsea_var_expand (kpse, spec.argv[argnum]);
}
args[argnum++] = xstrdup(base);
args[argnum] = NULL;
ret = maketex (kpse, format, args);
for (argnum = 0; args[argnum] != NULL; argnum++)
free (args[argnum]);
free (args);
}
return ret;
}
