Re: [Pkg-fonts-devel] Bug#798261: ITP: fonts-roboto-fontface -- largely geometric, friendly and open curves font
Thomas Goirand <zigo@debian.org> writes:
> On 09/08/2015 05:33 AM, Vasudev Kamath wrote:
>> Yeah, we already have couple of webfonts under pkg-fonts team, though
>> there is no strict policy yet we place them under /usr/share/fonts/type
>> where type can be ttf, otf, woff, svg eot, etc. And less/css/scss files
>> under /usr/share/fonts-package.
>
> That's what I've done in my package, indeed.
OK.
>
>> As an example you can have a look at fonts-font-awesome source, which is also
>> used by owncloud.
>
> Horizon also uses the fonts-font-awesome package, so it's nice to have
> such consistency indeed.
>
> Now, to move on, what's next action? Remove the fonts-roboto generation
> from the android fonts source? Or ... ? The thing is, I really *need*
> this webfont and the CSS, otherwise Horizon will be quite broken.
I'm not quite sure, as said earlier roboto-fontface-bower is not the
original roboto upstream so splitting it from the fonts-android doesn't
sound right.
OTOH to build fonts-roboto from actual upstream it needs a lot of work
as most of tools needed are not/not up-to-date in Debian.
May be for now it should be fine to ship fonts-roboto-fontface as not to
block the bringing of Horizon into Debian. May be once we have proper
fonts-roboto in proper shape in Debian we can generate required woff/svg
files and make roboto-fontface-bower only ship required less/css/scss
files.
Reply to: