On Di, 09 Okt 2012, Fabian Greffrath wrote:
> Looks good, no more naggin'. ;)
O . surprise ;-)
Thanks for checking, if every suggestion/bug report would come together
with a reporter that competent and helpful, I would be so happy!
Best wishes
Norbert
---
Am 09.10.2012 10:17, schrieb Norbert Preining:
Usual place for tex-gyre_2.004.1-5~3_amd64.changes.
As usual, comments welcome.
Looks good, no more naggin'. ;)
- Fabian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
On Di, 09 Okt 2012, Fabian Greffrath wrote:
> We should inform users in the package description for fonts-texgyre that
> the fonts get registered as alternatives for the 35 core Postscript fonts
Done in 5~3, also deleted most of the duplicated information and referred
to the pakage fonts-texgyre
Am 09.10.2012 02:21, schrieb Norbert Preining:
Still the same, the second paragraph is different.
We should inform users in the package description for fonts-texgyre
that the fonts get registered as alternatives for the 35 core
Postscript fonts in fontconfig. This might -- but shouldn't -- le
Hi Fabian,
On Mo, 08 Okt 2012, Fabian Greffrath wrote:
> The names of the fontconfig files could get adjusted to the new package
> name: tex-gyre --> fonts-texgyre .
Done.
> The documentation in /usr/share/doc/texmf/fonts/tex-gyre should get
> moved to the fonts-texgyre package, the documenta
On Mo, 08 Okt 2012, Fabian Greffrath wrote:
> The names of the fontconfig files could get adjusted to the new package
> name: tex-gyre --> fonts-texgyre .
I was half-way on the way, but not convinced ... ;-)
> The documentation in /usr/share/doc/texmf/fonts/tex-gyre should get
> moved to the f
Am 08.10.2012 10:12, schrieb Norbert Preining:
Preliminary packages at
deb http://people.debian.org/~preining/TeX/ unstable/
deb-src http://people.debian.org/~preining/TeX/ unstable/
(there are also the new texlive-base packages I have uploaded).
Cool, thanks. I was just about t
On So, 07 Okt 2012, Norbert Preining wrote:
> In this case I would not add the gust and stay with fonts-texgyre.
Preliminary packages at
deb http://people.debian.org/~preining/TeX/ unstable/
deb-src http://people.debian.org/~preining/TeX/ unstable/
(there are also the new texlive-b
> In this case both fonts-gust-{texgyre,lmodern} and
> fonts-{texgyre,lmodern} seem acceptable, so adding "gust" should be
> done only if "needed" by the above vague rule.
In this case I would not add the gust and stay with fonts-texgyre.
Now, if someone can propose a patch based on the current
Quoting Fabian Greffrath (fab...@greffrath.com):
> Am Freitag, den 05.10.2012, 18:22 +0200 schrieb Christian PERRIER:
> > I'm balanced about the value added by including the foundry name in
> > the package name. The current practice is more to use one when the
> > foundry is really something that c
Am Freitag, den 05.10.2012, 18:22 +0200 schrieb Christian PERRIER:
> I'm balanced about the value added by including the foundry name in
> the package name. The current practice is more to use one when the
> foundry is really something that can be called this way.
So you'd say "fonts-gust-{texgyre
Quoting Khaled Hosny (khaledho...@eglug.org):
> Right, and I checked other fonts-* package and there is indeed large
> inconsistency and I can’t tell what is the rule for including or
> omitting foundry name, it seems random.
(dropping individuals from CC list, I guess all are subscribed to one
o
On Fri, Oct 05, 2012 at 03:17:17PM +0200, Fabian Greffrath wrote:
> Am 05.10.2012 15:06, schrieb Khaled Hosny:
> >But that is not what the previous discussions suggest, nor the current
> >practice; almost all font names are unique, yet many packages includes a
> >foundry name or even invent one if
Am 05.10.2012 15:06, schrieb Khaled Hosny:
But that is not what the previous discussions suggest, nor the current
practice; almost all font names are unique, yet many packages includes a
foundry name or even invent one if it does not exist e.g.
fonts-hosny-amiri and fonts-hosny-thabit; there is n
On Fri, Oct 05, 2012 at 01:25:57PM +0200, Fabian Greffrath wrote:
> Am 05.10.2012 13:11, schrieb Norbert Preining:
> >- fonts-gust-texgyre for the OTF fonts
>
> If it's not necessary to distinguish the font from another one with
> a similar name, I would avoid mentioning the foundry. In this case
Am 05.10.2012 13:11, schrieb Norbert Preining:
- fonts-gust-texgyre for the OTF fonts
If it's not necessary to distinguish the font from another one with a
similar name, I would avoid mentioning the foundry. In this case it's
simply redundant.
- tex-gyre for the current TeX package and typ
On Fr, 05 Okt 2012, Fabian Greffrath wrote:
> have you thought about splitting the Opentype fonts off of the package?
Yes, I was thinking to go that way:
- fonts-gust-texgyre for the OTF fonts
- tex-gyre for the current TeX package and type 1 fonts
What do you think?
Best wishes
Norbert
Am 05.10.2012 11:49, schrieb Norbert Preining:
Ok, activated.
Thanks.
Should I make an upload to experimental of the current status or wait
for after wheezy? Is there a hurry for that?
No, not necessarily.
have you thought about splitting the Opentype fonts off of the package?
- Fabian
On Do, 04 Okt 2012, Fabian Greffrath wrote:
> Erm, please install the fontconfig file. We need a better looking
> alternative for the 35 Postscript core fonts than the Type 1 files
> provided by gsfonts.
Ok, activated.
Should I make an upload to experimental of the current status or wait
for
Am 25.09.2012 09:28, schrieb Fabian Greffrath:
Well, fair enough. The 35 Postscript core fonts are generally expected
in Type 1 format and the alias.conf file will map them to the Tex-Gyre
fonts in Opentype format. However, I think for fontconfig-using
applications this shouldn't be a big deal an
20 matches
Mail list logo
