I'm asking a couple of things -- is TT_NAME_ID_SAMPLE_TEXT specified
anywhere? I'd expect it to contain something like "How quickly daft
jumping zebras vex" but I wanted to check that was indeed the kind of
thing it might show.
The seconds is really asking why so few fonts actually use this
metadata item :) Would it be possible to add these in at package build
time, as showing something like "Sample text" using Lohit-Punjabi.ttf
doesn't make sense at all.
I'm also needing a much shorter text string for the icon (e.g. "Aa")
but I guess keying on 'lang' is the best way to do this.
On 10 March 2014 14:46, Paul Flo Williams <paul(a)frixxon.co.uk> wrote:
>> Is there any precedent here? Like a Punjabi version of "How quickly
>> daft jumping zebras vex" that shows off the majority of the glyphs?
Yes, I saw that, but it doesn't seem to map the locale to the string,
just some languages. I figured (hoped) there'd be some kind of wiki
page with locale -> example text.
If you recall we had earlier discussion regarding changing name of
Lohit Oriya to Lohit Odia. 
We had a chance to do it with lohit2 project with number of
improvements as we done for Lohit Gurmukhi. Still i think we are already
late for doing this change considering feeling from Odia community around.
So without doing any further delay this is the release specifically
for renaming Lohit Oriya to Odia. I have updated lohit fedorahosted 
page for download details.
Let me know if anything more needed in this regards.
I'm adding a feature to enable/disable the fontconfig configuration files from packages for users and per-users in fonts-tweak-tool and almost has already been implemented in git. I believe this feature allows more customization around fonts.
One problem on this is, it is quite hard to see what it is for from those filenames. those might contains multiple rulesets too.
So I'd like to propose adding the description in the certain syntax to the files and the template. and according to this change I'd encourage packagers to have a separate rulesets if it's useful to do so.
In last six month we have completed Devanagari (Marathi and Nepali),
Gujarati, Gurmukhi and Malayalam under lohit2 project . We have done
significant improvement in these fonts not only from technical
perspective but also from standards perspective. I am confident enough
to say Lohit follows all standards around fonts and Indian languages and
I attended typoday.in  conference in last weekend and talked with
people around on lohit2. Happy to see number of people in fonts industry
are aware regarding Lohit fonts. Few people even used Lohit fonts during
the workshop to demonstrate some points. Few people proposed enhancement
by adding more ligature. So we all are going good :)
This is time to do improvements in Lohit Assamese and Bengali.
Followings are improvements we are looking for..
* Removing not required ligatures.
* Rewriting efficient open type tables.
* Support to the "beng" and "bng2" open type script tags.
* Building fonts through feature file (.fea)
* Following AGL specification syntax.
* Testing on Harfbuzz NG, Uniscribe(W8).
* Automated Testing Tool utilization
One of the important task prior to development is to identify
guidelines, specifications for Assamese and Bengali script. We do have
TDIL documents available and will see if there is any other. With these
improvements i am sure Lohit Assamese and Bengali can become standard
reference font for upcoming Bengali fonts project.
Need help from Assamese and Bengali language expert. I know few
already and will ping them for more input during the developments.
Development activity is going to happen in lohit2  git. Feel free to
report bug and propose enhancements.