problems with ecti10.pfb

View: New views
4 Messages — Rating Filter:   Alert me  

problems with ecti10.pfb

by Massimiliano Gubinelli :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi all,
  the font file ecti10.pfb (distributed in TeXmacs-windows-fonts-1.0-
noarch.tar.gz) seems to contain an error. Any document I compose  
containing an italic "g" of size 10 display fine on my Mac (even after  
PDF export) but my printer refuses it giving an "invalidfont" error  
just while attempting to print the "g". If I use a larger size (12)  
everything is fine so I do not think it is a problem with TeXmacs code  
but rather with the font file.

Somebody can confirm this observation? (You have to be sure that  
during PS/PDF export TeXmacs will use the type1 fonts and not replace  
them with bitmaps, please inspect the generated PS to confirm this).

A sample file:


<TeXmacs|1.0.7.2>
<style|generic>
<\body>
   <em|aga>
</body>



Best, Massimiliano





_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@...
http://lists.gnu.org/mailman/listinfo/texmacs-dev

Re: problems with ecti10.pfb

by Joris van der Hoeven :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Max,

No, everything works fine on my postscript laser printer...

Best wishes, --Joris


On Mon, Sep 21, 2009 at 03:59:43PM +0200, Gubinelli Massimiliano wrote:

> Hi all,
>  the font file ecti10.pfb (distributed in TeXmacs-windows-fonts-1.0-
> noarch.tar.gz) seems to contain an error. Any document I compose  
> containing an italic "g" of size 10 display fine on my Mac (even after  
> PDF export) but my printer refuses it giving an "invalidfont" error  
> just while attempting to print the "g". If I use a larger size (12)  
> everything is fine so I do not think it is a problem with TeXmacs code  
> but rather with the font file.
>
> Somebody can confirm this observation? (You have to be sure that  
> during PS/PDF export TeXmacs will use the type1 fonts and not replace  
> them with bitmaps, please inspect the generated PS to confirm this).
>
> A sample file:
>
>
> <TeXmacs|1.0.7.2>
> <style|generic>
> <\body>
>   <em|aga>
> </body>
>
>
>
> Best, Massimiliano
>
>
>
>
>
> _______________________________________________
> Texmacs-dev mailing list
> Texmacs-dev@...
> http://lists.gnu.org/mailman/listinfo/texmacs-dev


_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@...
http://lists.gnu.org/mailman/listinfo/texmacs-dev

Re: problems with ecti10.pfb

by Massimiliano Gubinelli :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Joris,

On 24 sept. 09, at 22:34, Joris van der Hoeven wrote:

> Hi Max,
>
> No, everything works fine on my postscript laser printer...
>

Indeed it is strange since (at least before summer) I didn't have this  
problem. And the problem is present only when I print the files  
(unfortunately I do not have other printer for testing). To remove it  
I actually replaced the problematic fonts in TeXmacs/fonts/type1/ec/  
(essentially ecbi10.pfb, ecbx12.pfb and ecti10.pfb by equivalent  
version obtained by reencoding some of the Latin Modern fonts. This  
make me  think about the fact that this replacement can be pushed into  
the standard distribution since the Latin Modern version of CM have  
more compact representation than the default TeXmacs ec*.pfb fonts  
(which as far as I understand are obtained by tracing the MetaFont  
generated CM font bitmaps). Do you think this is possible in full  
generality? Latin Modern contains a lot of gliphs and my replacements  
seems to work fine.

Best
Massimiliano



> Best wishes, --Joris
>
>
> On Mon, Sep 21, 2009 at 03:59:43PM +0200, Gubinelli Massimiliano  
> wrote:
>> Hi all,
>> the font file ecti10.pfb (distributed in TeXmacs-windows-fonts-1.0-
>> noarch.tar.gz) seems to contain an error. Any document I compose
>> containing an italic "g" of size 10 display fine on my Mac (even  
>> after
>> PDF export) but my printer refuses it giving an "invalidfont" error
>> just while attempting to print the "g". If I use a larger size (12)
>> everything is fine so I do not think it is a problem with TeXmacs  
>> code
>> but rather with the font file.
>>
>> Somebody can confirm this observation? (You have to be sure that
>> during PS/PDF export TeXmacs will use the type1 fonts and not replace
>> them with bitmaps, please inspect the generated PS to confirm this).
>>
>> A sample file:
>>
>>
>> <TeXmacs|1.0.7.2>
>> <style|generic>
>> <\body>
>>  <em|aga>
>> </body>
>>
>>
>>
>> Best, Massimiliano
>>
>>
>>
>>
>>
>> _______________________________________________
>> Texmacs-dev mailing list
>> Texmacs-dev@...
>> http://lists.gnu.org/mailman/listinfo/texmacs-dev
>
>
> _______________________________________________
> Texmacs-dev mailing list
> Texmacs-dev@...
> http://lists.gnu.org/mailman/listinfo/texmacs-dev



_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@...
http://lists.gnu.org/mailman/listinfo/texmacs-dev

Re: problems with ecti10.pfb

by Joris van der Hoeven :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri, Sep 25, 2009 at 04:36:18PM +0200, Gubinelli Massimiliano wrote:

> Hi Joris,
>
> On 24 sept. 09, at 22:34, Joris van der Hoeven wrote:
>
> >Hi Max,
> >
> >No, everything works fine on my postscript laser printer...
> >
>
> Indeed it is strange since (at least before summer) I didn't have this  
> problem. And the problem is present only when I print the files  
> (unfortunately I do not have other printer for testing). To remove it  
> I actually replaced the problematic fonts in TeXmacs/fonts/type1/ec/  
> (essentially ecbi10.pfb, ecbx12.pfb and ecti10.pfb by equivalent  
> version obtained by reencoding some of the Latin Modern fonts. This  
> make me  think about the fact that this replacement can be pushed into  
> the standard distribution since the Latin Modern version of CM have  
> more compact representation than the default TeXmacs ec*.pfb fonts  
> (which as far as I understand are obtained by tracing the MetaFont  
> generated CM font bitmaps). Do you think this is possible in full  
> generality? Latin Modern contains a lot of gliphs and my replacements  
> seems to work fine.

Yes, we can consider this kind of replacement ...
when we come to the reorganization of fonts.
Let us first complete the Qt port ;^)

Best wishes, --Joris


_______________________________________________
Texmacs-dev mailing list
Texmacs-dev@...
http://lists.gnu.org/mailman/listinfo/texmacs-dev