License

The lualatex-platform package is free software; it is made available under the conditions of the Expat (MIT) license, which is reprinted below:

Copyright © 2011, Philipp Stephani <st_philipp@yahoo.de>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Installation

The lualatex-platform package is hosted on GitHub; please report any errors at the issue tracker.

The whole bundle consists of a LaTeX package lualatex-platform.sty, a LuaLaTeX module lualatex-platform.lua, and the actual C extension module lltxplatform.(dll|so). The extension module should compile for recent versions of Windows (with MinGW), OS X, and Linux. The compilation process is based on the GNU build system, so you should be able to compile the module with the commands:

./configure && make

The standard C headers and the Lua headers (lua.h etc.) must be present in the include path. On Windows, the compiler needs to access the Lua import library (lua51.lib or liblua51.a), which must be located in the library search path. On Linux, the compiler needs to access the FontConfig header files (fontconfig/fontconfig.h) and library (libfontconfig.so), which must be present in the respective search paths. Run ./configure --help for more options.

After compiling, make sure that the files lualatex-platform.sty, lualatex-platform.lua, and lltxplatform.(dll|so) can be found by LuaLaTeX. On Windows, the native library must be able to find the Lua runtime library lua51.dll.

Usage

In a LaTeX document or package, load the lualatex-platform package with:

\usepackage{lualatex-platform}

(or \RequirePackage, of course). The document should be compiled with the LuaTeX engine, and the luatexbase module has to be installed.

You can also load the Lua module directly:

\RequireLuaModule{lualatex-platform}

or, from Lua:

luatexbase.require_module("lualatex-platform")

After the module has been loaded, the table lualatex.platform contains the functions described below.

Note that on OS X, loading extension modules currently requires a custom-build LuaTeX binary.

Querying system fonts

The module table lualatex.platform contains two parameterless functions related to operating system font listing:

• get_installed_fonts() returns either nil (in the case of an error), or an array of tables each of which represents one font known to the operating system and contains an arbitrary combination of the following items:

  • An item with key name: The value of this item is a string containing the name of the font as reported by the operating system. This name is platform-dependent and largely arbitrary; there is no guarantee that the name is present or meaningful, and the names are not guaranteed to be unique within the fonts array. On Windows and OS X, the string is encoded in UTF-8; on Linux, the encoding depends on the configuration of the operating system. If the font name cannot be obtained, this field is nil.
  • An item with key path: The value of this item is a string containing the file path where the font is located. There is no guarantee that a file with this name exists and contains a valid font, and the paths are not guaranteed to be unique within the fonts array. On Windows, relative path names are assumed to be relative to the operating system font directory. There is no guarantee about whether the path is relative or which path syntax is used. On Windows, the string is encoded in the legacy 8-bit file system encoding (“ANSI code page”) because the standard C library functions in the Microsoft runtime don’t accept Unicode strings; if the file name cannot be represented in the legacy encoding, this field is nil. On OS X and Linux, the string is encoded in the current file system encoding. If the path cannot be obtained, this field is nil.

  The array is in arbitrary order, and duplicates are possible.

• get_inactive_fonts() returns either nil (in the case of an error), or an array of strings each of which represents one font treated as inactive by the operating system. The concept of inactive fonts exists only on Windows 7 and upwards; the inactive fonts are still present and usable, but are hidden in standard UI elements. The array of inactive fonts is in arbitrary order and the font names are not necessarily unique. There is no guarantee that the names returned by get_inactive_fonts() correspond to actual fonts installed in the system, or to the font names returned by get_installed_fonts(). The font names are encoded in UTF-8.