With the introduction of the langpack plugin for yum, we've managed to
remove most of the manually-maintained group metadata for i18n/l10n.
However, one spot we still have a problem is for fonts.
We *could* for any language that's requested, do an install of
font(:lang=<whatever>), but that doesn't give us a useful mechanism to
prioritize the proper default font.
Would it be worth it for the default fonts for a particular locale to
Provide: default-font(lang=<foo>)? Maintaining this could be problematic,
but we would only need to do this for locales that aren't handled by dejavu
or similar latin/greek/etc. fonts.
Hi Pravin and list,
at sunzi project, we strive to consume external components from
their repositories and other native locations. To make it easily
possible also with Liberation fonts, I went through the existing
Makefile with the aim to add support for exporting into common web
formats, making some other changes on my way.
In fact, the change I desire is concentrated in the last patch, but
I hope the previous ones (split into more patches for easier review)
also make sense. The compatibility with releasing workflow as well
as with the job of system packagers should be guaranteed.
If there is something wrong with the patchset, feel free to bug me
on. Otherwise I would be grateful for applying it.
P.S. I can go ahead and file a bug (referring to this thread) if it is
a preferred channel.
Jan Pokorný (6):
Makefile: do not remove file we do not create
Fix duplicate README (nested as link to root one)
Makefile: add .PHONY target
Makefile: add check target using fontlint
Makefile: restructure for usability and modularity
Makefile: now support other common export formats
source/.gitignore | 8 +++
source/Makefile | 125 ++++++++++++++++++++++++++++++-----------
source/README | 83 +---------------------------
source/scripts/fontexport.pe | 22 +++++++
4 files changed, 122 insertions(+), 116 deletions(-)
create mode 100644 source/.gitignore
mode change 100644 => 120000 source/README
create mode 100644 source/scripts/fontexport.pe
Announcing the Lohit fonts 2.5.1 release. Following are the highlights.
- Support for Characters added in Unicode 6.0 in Devanagari, Bengali,
Malayalam and Oriya scripts and Devanagari Extended.
- Release of Lohit Marathi and Nepali with language specific shapes.
Please note here Lohit Devanagari has localize characters for Marathi
and Nepali with locl feature of Open Type fonts and one can access it
with specific LANG.
Still we have released these fonts since some rendering engine (qt,
icu) still not supporting locl feature and second is user using en_US
locale can not access language specific characters from Lohit Devanagari.
- Releasing lohit-ttf tarball consisting all lohit fonts ttf
This is for easy installation of all lohit fonts together. One can now
download it and simply copy all ttf fonts in required folder.
- Major bugfixes in Telugu, Kannada, Assamese, Punjabi.
For further details see Changelog released with each language.
I am working on Lohit Tamil fonts will release it soon with Lohit
Tamil Classical font.
Behdad Esfahbod (behdad.esfahbod(a)gmail.com) said:
> So, if i understand it correctly, you're asking for a way to get the
> default font for a language. Right?
Right. Given a language (zh, pa, pt_BR), I want to be able to grab the
default font, so we don't have to have the language support groups.
> That sure sounds like something Fontconfig shall be able to answer,
> but it's tricky. Do you need this on the server or client? Cause
> FcMatch and friends only return fonts that are installed. What you
> want can be done by processing the ":lang=foo" pattern by Fc
> Sybstitute calls, then taking the resulting family list and pickin the
> first one that supports the lang in question.
> After you answer my question re which side you need this on I can
> hopefully provide more concrete advice.
On the client, which may have no font packages installed. I thought about
having the plugin read the fontconfig configuration for preferred fonts, but
given that that operates based on the configuration files in the font
packages themselves, I don't have the information there that I would need.
Released Liberation fonts 1.07.2 [minor release]
- removed hint instruction from LiberationMono-Italic cent sing,
- adeed U+0472, U+0473 in Sans and SansNarrow, rhbz #751566
- added cyrillic italics for U+043F, rhbz #708330
Few hinting bugs are pending, will try to resolve them in next release.
See TODO list for remaining tasks.
Great news! The author of the Code2000 pan-Unicode font has recently
switched the font to being licensed under the GNU GPLv3. During the
discussions where I attempted to verify the license and get commit
access to the project, James granted dual licensing under the GPLv3+FE
and the SIL OFL. Unfortunately he wants to keep the code2000.sf.net
project as a historic and no-longer developed project and have us fork
the project, hosting it elsewhere.
My initial plans for the project are:
* pick a name for the fork, C2K was suggested during the
* pick a site for hosting the fork, add Thierry, myself and anyone
else who wants to join the project
* setup a git repository and import the current binary TTF release
* convert the binary TTF files into UFO format, which seems to be
a more cross-vendor format than SFD, commit that to git.
According to the current release, "All fonts are created from
scratch natively in TTF format inside FontCreator 6.0".
* cleanup and add documentation about the licensing
* package it for Debian and encourage other distros to package it
* blog about the freeing of the font and get that on LWN/etc
* look for contributors and watch for bug reports