From: SourceForge.net <no...@so...> - 2003-06-25 20:52:30
|
Bugs item #760764, was opened at 2003-06-25 20:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Nobody/Anonymous (nobody) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-06-26 06:52:33
|
Bugs item #760764, was opened at 2003-06-25 22:52 Message generated for change (Comment added) made by wobsta You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) >Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: André Wobst (wobsta) Date: 2003-06-26 08:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-06-26 08:31:24
|
Bugs item #760764, was opened at 2003-06-25 22:52 Message generated for change (Comment added) made by joergl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: Jörg Lehmann (joergl) Date: 2003-06-26 10:31 Message: Logged In: YES user_id=390410 Please check whether the changes made in the CVS head fix this problem. Jörg ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 08:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-06-26 08:43:09
|
Bugs item #760764, was opened at 2003-06-25 22:52 Message generated for change (Comment added) made by wobsta You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: André Wobst (wobsta) Date: 2003-06-26 10:43 Message: Logged In: YES user_id=405853 Fix looks fine to me. I can get marvosym running by that (which didn't work previously due to the same bug). Consider this minimal example: from pyx import * text.set(mode="latex") text.preamble("\usepackage{marvosym}") c = canvas.canvas() c.text(0, 0, "\EUR") c.writetofile("test") Unfortunately you have to do two things for getting this working: 1. You have to copy marvosym.pfb to fmvr8x.pfb (the name used intenally) 2. You have to modify the PostScript output test.eps, namely you have to change the selectfont from /FMVR8X 9.962640 selectfont to /Martin_Vogels_Symbole 9.962640 selectfont The information can be found in marvosym.map To be implemented ... ?! ---------------------------------------------------------------------- Comment By: Jörg Lehmann (joergl) Date: 2003-06-26 10:31 Message: Logged In: YES user_id=390410 Please check whether the changes made in the CVS head fix this problem. Jörg ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 08:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-06-27 19:13:09
|
Bugs item #760764, was opened at 2003-06-25 20:52 Message generated for change (Comment added) made by gertingold You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: Gert Ingold (gertingold) Date: 2003-06-27 19:04 Message: Logged In: YES user_id=809523 The changes to text.py fixed the original problem. However, there is still a problem (basically already described by André in his message of June 26). Apparently, the map-files are not evaluated so that replacement fonts are used. This behavior can already be obtained with the standard TeX fonts and \usepackage[T1]{fontenc}. The solution suggested by André is not very practical so that the question mark in "To be implemented ... ?!" should be replaced by (at least two) exclamation marks. ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 08:43 Message: Logged In: YES user_id=405853 Fix looks fine to me. I can get marvosym running by that (which didn't work previously due to the same bug). Consider this minimal example: from pyx import * text.set(mode="latex") text.preamble("\usepackage{marvosym}") c = canvas.canvas() c.text(0, 0, "\EUR") c.writetofile("test") Unfortunately you have to do two things for getting this working: 1. You have to copy marvosym.pfb to fmvr8x.pfb (the name used intenally) 2. You have to modify the PostScript output test.eps, namely you have to change the selectfont from /FMVR8X 9.962640 selectfont to /Martin_Vogels_Symbole 9.962640 selectfont The information can be found in marvosym.map To be implemented ... ?! ---------------------------------------------------------------------- Comment By: Jörg Lehmann (joergl) Date: 2003-06-26 08:31 Message: Logged In: YES user_id=390410 Please check whether the changes made in the CVS head fix this problem. Jörg ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 06:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-06-27 20:04:24
|
Bugs item #760764, was opened at 2003-06-25 20:52 Message generated for change (Comment added) made by gertingold You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: Gert Ingold (gertingold) Date: 2003-06-27 20:04 Message: Logged In: YES user_id=809523 One more comment concerning the workaround proposed by André: Things become of course more complicated if reencoding takes place (e.g. when the map file contains the statement "TeXBase1Encoding ReEncodeFont"). What was meant to be a ß (germandbls), i.e. character 255 in EC, will turn out as ydieresis in TeXBase1. In order to obtain a ß, one would have to ask for a \SS=Germandbls=character 223. If this is not done, the glyph is not even extracted from the pfb-file so that changing the eps-file would not be an option anymore. ---------------------------------------------------------------------- Comment By: Gert Ingold (gertingold) Date: 2003-06-27 19:04 Message: Logged In: YES user_id=809523 The changes to text.py fixed the original problem. However, there is still a problem (basically already described by André in his message of June 26). Apparently, the map-files are not evaluated so that replacement fonts are used. This behavior can already be obtained with the standard TeX fonts and \usepackage[T1]{fontenc}. The solution suggested by André is not very practical so that the question mark in "To be implemented ... ?!" should be replaced by (at least two) exclamation marks. ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 08:43 Message: Logged In: YES user_id=405853 Fix looks fine to me. I can get marvosym running by that (which didn't work previously due to the same bug). Consider this minimal example: from pyx import * text.set(mode="latex") text.preamble("\usepackage{marvosym}") c = canvas.canvas() c.text(0, 0, "\EUR") c.writetofile("test") Unfortunately you have to do two things for getting this working: 1. You have to copy marvosym.pfb to fmvr8x.pfb (the name used intenally) 2. You have to modify the PostScript output test.eps, namely you have to change the selectfont from /FMVR8X 9.962640 selectfont to /Martin_Vogels_Symbole 9.962640 selectfont The information can be found in marvosym.map To be implemented ... ?! ---------------------------------------------------------------------- Comment By: Jörg Lehmann (joergl) Date: 2003-06-26 08:31 Message: Logged In: YES user_id=390410 Please check whether the changes made in the CVS head fix this problem. Jörg ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 06:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |
From: SourceForge.net <no...@so...> - 2003-08-26 11:41:10
|
Bugs item #760764, was opened at 2003-06-25 22:52 Message generated for change (Comment added) made by joergl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Gert Ingold (gertingold) Assigned to: Jörg Lehmann (joergl) Summary: TFMError "width_index should not be zero" Initial Comment: Hello, I am trying to use a commercial font (Garamond Standard from Softmaker) with PyX 0.3.1. Unfortunately, a TFMError "width_index should not be zero" is raised. A closer look at the TFM files shows indeed that CHARWD is zero for certain characters, namely "17x in the T1 encoding (8t) and "17x and "1Fx in the TS1 encoding (8c). Character "17x is defined as /compoundwordmark while "1Fx is /ffl. The font tables in CTAN:fonts/utilities/fontinst-prerelease/doc/talks/et99-font-tables.pdf don't show glyphs for compoundwordmark in the T1 and TS1 encodings and for the ffl ligature in the TS1 encoding (of course, the ffl ligature is present in the T1 encoding). The same problem arises if I use the package mathptmx while the use of the palatino package leads to: After parsing this message, the following was left: *(/usr/TeX/texmf/tex/latex/psnfss/ot1phv.fd) If the described effect is caused by PyX checking the CHARWD's of all characters, this should, in my opinion, be considered a bug. Best regards, Gert ---------------------------------------------------------------------- >Comment By: Jörg Lehmann (joergl) Date: 2003-08-26 13:39 Message: Logged In: YES user_id=390410 This problem should be fixed in PyX 0.4. Thanks, Jörg ---------------------------------------------------------------------- Comment By: Gert Ingold (gertingold) Date: 2003-06-27 22:04 Message: Logged In: YES user_id=809523 One more comment concerning the workaround proposed by André: Things become of course more complicated if reencoding takes place (e.g. when the map file contains the statement "TeXBase1Encoding ReEncodeFont"). What was meant to be a ß (germandbls), i.e. character 255 in EC, will turn out as ydieresis in TeXBase1. In order to obtain a ß, one would have to ask for a \SS=Germandbls=character 223. If this is not done, the glyph is not even extracted from the pfb-file so that changing the eps-file would not be an option anymore. ---------------------------------------------------------------------- Comment By: Gert Ingold (gertingold) Date: 2003-06-27 21:04 Message: Logged In: YES user_id=809523 The changes to text.py fixed the original problem. However, there is still a problem (basically already described by André in his message of June 26). Apparently, the map-files are not evaluated so that replacement fonts are used. This behavior can already be obtained with the standard TeX fonts and \usepackage[T1]{fontenc}. The solution suggested by André is not very practical so that the question mark in "To be implemented ... ?!" should be replaced by (at least two) exclamation marks. ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 10:43 Message: Logged In: YES user_id=405853 Fix looks fine to me. I can get marvosym running by that (which didn't work previously due to the same bug). Consider this minimal example: from pyx import * text.set(mode="latex") text.preamble("\usepackage{marvosym}") c = canvas.canvas() c.text(0, 0, "\EUR") c.writetofile("test") Unfortunately you have to do two things for getting this working: 1. You have to copy marvosym.pfb to fmvr8x.pfb (the name used intenally) 2. You have to modify the PostScript output test.eps, namely you have to change the selectfont from /FMVR8X 9.962640 selectfont to /Martin_Vogels_Symbole 9.962640 selectfont The information can be found in marvosym.map To be implemented ... ?! ---------------------------------------------------------------------- Comment By: Jörg Lehmann (joergl) Date: 2003-06-26 10:31 Message: Logged In: YES user_id=390410 Please check whether the changes made in the CVS head fix this problem. Jörg ---------------------------------------------------------------------- Comment By: André Wobst (wobsta) Date: 2003-06-26 08:52 Message: Logged In: YES user_id=405853 I'm just considering the problem of loading fd-files triggered by TeX when processing some expressions. By default, those messages are errors in PyX 0.3.1. I've just checked in a special handler for font description file loading, enabled by default via texmessagedefaultrun. Thus fd-file loading is not considered to be an error anymore. Beside that, your report about tfm-file handling is still open. PyX might be just to strict in that sence. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=442886&aid=760764&group_id=45430 |