Thanks for sharing, Mark. SIL fontutils[1] has lot of handy tools.
[1] http://scripts.sil.org/cms/scripts/page.php?site_id=nrsiid=fontutils
Santhosh
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
By the way, I've just tried to use ttf2woff from fontutils to convert
Ubuntu TTF font to WOFF format for use in one of my projects.
And the resulting WOFF produced by this utility is not usable in any
Linux browsers (tried Firefox, Chrome, Opera). Don't know if it works on
Windows.
And at the
For the font repository we maintain as part of
UniversalLanguageSelector, we use Google sfntly[1] to convert fonts to
WOFF and EOT with maximum compression.
We also use MicroType express compression[2] for compressing eot to
reduce the size as possible as we can.
Fontforge has an option to export
By the way, I've just tried to use ttf2woff from fontutils to convert
Ubuntu TTF font to WOFF format for use in one of my projects.
And the resulting WOFF produced by this utility is not usable in any
Linux browsers (tried Firefox, Chrome, Opera). Don't know if it works on
Windows.
And at the
Fontforge has an option to export the fonts to WOFF format.
Thanks, Fontforge worked even better than the online converter - usable
WOFF, and the size is 50kb instead of 54kb :-)
[1] http://code.google.com/p/sfntly/
[2] http://code.google.com/p/sfntly/wiki/MicroTypeExpress
As I
On Sun, Feb 17, 2013 at 2:17 AM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
On 02/16/2013 01:50 PM, Basil George wrote:
*We have tried to address the privacy issues in obtaining IPs
here
I'd like to introduce LinqToWiki: a new library for accessing the
MediaWiki API from .Net languages (e.g. C#).
Its main advantage is that it knows the API and is strongly-typed,
which means autocompletion works on API modules, module parameters and
result properties and correctness is checked at
Petr, make sure you require users to set their *User-Agent* string. Your
library should not use any defaults.
For the examples I would recommend this *User-Agent:*
*MyCoolTool/1.1 (http://example.com/MyCoolTool/; mycoolt...@example.com)
LinqToWiki/1.0*
See
I didn't realize that was a requirement for libraries (the library
allowed setting the UserAgent, but it didn't force it until now).
I have made that change and setting the UserAgent is now required.
Petr Onderka
[[en:User:Svick]]
On Sun, Feb 17, 2013 at 7:42 PM, Yuri Astrakhan
Thanks for fixing it so fast!
In the constructor, you might want to add your lib's ID to the useragent
param:
UserAgent = useragent.Trim() + LinqWiki/1.0;
so that it would be possible not only to see that a bot is broken, but also
catch framework bugs if all bots show the same problem.
Well keep in mind it's not just the total number of editors. The
requirement would have to be that the number the editors in each
independent geographic region would have to either be zero or above a
threshold. Meaning if we did geo-analysis based on countries, any country
with at least one editor
Hi,
in the next version of the code review system, a way to classify the
type of change would be great. Maybe the trac-system would a good
inspiration. i.e. a critical bug may be more important to review soon
than a new feature.
Furthermore running stylize.php remotely might be helpful to avoid
On Sun, Feb 17, 2013 at 9:22 PM, Moritz Schubotz phy...@physikerwelt.de wrote:
Hi,
in the next version of the code review system, a way to classify the
type of change would be great.
Well, we can use topics for this. Freeform tagging would be nice,
but that's further down on the roadmap.
MediaWiki Bugzilla Report for February 11, 2013 - February 18, 2013
Status changes this week
Bugs NEW : 570
Bugs ASSIGNED : 128
Bugs REOPENED : 53
Bugs RESOLVED
On 16/02/13 07:55, Steven Walling wrote:
I didn't see it in the docs above, so thought I'd ask... Is this going
to include rollout of the CodeEditor extension, or will that be done
separately?
CodeEditor will be enabled, but with $wgCodeEditorEnableCore = false,
i.e. in the Module namespace
Le 18/02/13 03:22, Moritz Schubotz wrote:
in the next version of the code review system, a way to classify the
type of change would be great. Maybe the trac-system would a good
inspiration. i.e. a critical bug may be more important to review soon
than a new feature.
Hello,
In our homegrown
16 matches
Mail list logo
