On Mon, Jul 16, 2012 at 9:18 PM, Jaldhar H. Vyas wrote:
> On Sat, 14 Jul 2012, Vasudev Kamath wrote:
>
>> As I said above it should always been in this way from beginning but I
>> don't know why ttf-indic-fonts was created by mixing all fonts
>> together during that time.
>>
>
> Because there wasn
On Sat, 14 Jul 2012, Vasudev Kamath wrote:
As I said above it should always been in this way from beginning but I
don't know why ttf-indic-fonts was created by mixing all fonts
together during that time.
Because there wasn't any specific policy then and I assumed separation by
language would
On 18:51 Sat 14 Jul , G Karunakar wrote:
> I am out of touch with font package naming rules.. but wondering why
> have separate font- , couldn't it go in fonts-gujr-extra ?
When it is upstream what is the meaning of adding it in
fonts-gujr-extra? Basically fonts-gujr-extra is fonts with
On Thu, Jul 12, 2012 at 11:49 PM, Christian PERRIER wrote:
> Quoting Kartik Mistry (kar...@debian.org):
>> Package: wnpp
>> Severity: wishlist
>> Owner: Debian-IN Team
>>
>> * Package name: font-kalapi
>
> Should be fontS-kalapi (yeah, only if there is only one font in the package)
>
>> Ver
Quoting Kartik Mistry (kar...@debian.org):
> Package: wnpp
> Severity: wishlist
> Owner: Debian-IN Team
>
> * Package name: font-kalapi
Should be fontS-kalapi (yeah, only if there is only one font in the package)
> Version : 0.1
> Upstream Author : GujaratiLexicon Team
> * URL
Package: wnpp
Severity: wishlist
Owner: Debian-IN Team
* Package name: font-kalapi
Version : 0.1
Upstream Author : GujaratiLexicon Team
* URL : https://github.com/gujaratilexicon/font-kalapi
* License : OFL-1.1
Programming Lang: N/A
Description : Kalap
6 matches
Mail list logo
