FW: FrameMaker/ePublisher issue
Sorry for my late reply as I was not able to review any responses until this afternoon, but I would like to thank all who replied to my post. We choose to avoid the pesky issues with symbol display in HTML by replacing the symbol bullets with graphic images of those bullets in our paragraph tags. They display quite nicely in the resulting HTML. Mark E. From: Eichelberger, Mark Sent: Monday, January 05, 2009 10:09 AM To: 'framers at lists.frameusers.com' Subject: FrameMaker/ePublisher issue Folks, I honestly do not know if this is a FrameMaker or ePublisher issue, but I thought I would first ask here first. We are currently using FrameMaker version 7 and have just upgraded to ePublisher version 2008.3. We also use a 3rd Party plugin for FM called AutoText to define tables or graphic items for selection via a pull down menu in FM. What we have noticed in the HTML and PDF output of our FM source files generated by the 2008.3 version of ePublisher is that symbols within the FM AutoText tables, such as the Monotype Sorts "Pointing Finger" or the Wingdings "Warning Bell", are being substituted by other symbols in the resulting HTML and PDF output. For example, the warning bell symbol displays as a percentage symbol in the pdf output. We noticed these issues after upgrading to the 2008.3 version of ePublisher. All symbols appear correctly in the html and pdf output when generating via our earlier version of ePublisher. Has anyone else run into an issue such as this? If so, is it a FM issue or an ePublisher issue? Thanks in advance, Mark Eichelberger Senior Technical Writer Fiserv CU7 Mark.Eichelberger at Aftech.Fiserv.com
Re: FrameMaker/ePublisher issue
I'd say neither; it's probably a system/font problem. For example, the % sign is showing up because your system (or Acrobat Distiller) can't find the Wingdings font and is substituting another font. I'd check the Distiller settings to make sure that the Font Location is correct and maps all the fonts on the system. And, do you have the Adobe printer instance set as the system default printer? It's possible your Autotext string may munged up and isn't inserting the correct font info, but that should show up in Frame -- if it's correct in FM, the problem is happening in another program. Art Art Campbell art.campb...@gmail.com ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 On Mon, Jan 5, 2009 at 10:08 AM, Eichelberger, Mark mark.eichelber...@aftech.fiserv.com wrote: Folks, I honestly do not know if this is a FrameMaker or ePublisher issue, but I thought I would first ask here first. We are currently using FrameMaker version 7 and have just upgraded to ePublisher version 2008.3. We also use a 3rd Party plugin for FM called AutoText to define tables or graphic items for selection via a pull down menu in FM. What we have noticed in the HTML and PDF output of our FM source files generated by the 2008.3 version of ePublisher is that symbols within the FM AutoText tables, such as the Monotype Sorts Pointing Finger or the Wingdings Warning Bell, are being substituted by other symbols in the resulting HTML and PDF output. For example, the warning bell symbol displays as a percentage symbol in the pdf output. We noticed these issues after upgrading to the 2008.3 version of ePublisher. All symbols appear correctly in the html and pdf output when generating via our earlier version of ePublisher. Has anyone else run into an issue such as this? If so, is it a FM issue or an ePublisher issue? Thanks in advance, Mark Eichelberger Senior Technical Writer Fiserv CU7 mark.eichelber...@aftech.fiserv.com ___ You are currently subscribed to Framers as art.campb...@gmail.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
RE: FrameMaker/ePublisher issue
Mark, This is an ePublisher issue. I have run into it. You can search characters on the ePublisher support page: Wingdings characters present a particular challenge when working with HTML-based content. Since Wingdings (as well as a few other symbol fonts) conflicts with the Unicode character map, many browsers simply don't support it. Internet Explorer skirts the issue and displays these characters correctly. A solution is to use the character map to do a translation from one character to another. To modify the ePublisher character map, you'll need to perform a simple overide of a file called 'mapentrysets.xml', which is located by default in the ePublisher Pro installation directory: ePublisher Pro\Formats\Shared\html For information on performing target overrides, please see their online knowledge base article here: http://www.webworks.com/technotes/articles/ePublisherPro/EX_ePub_Project_Format_Overrides.36.1.aspx Mary -Original Message- From: framers-boun...@lists.frameusers.com [mailto:framers- boun...@lists.frameusers.com] On Behalf Of Eichelberger, Mark Sent: Monday, January 05, 2009 7:09 AM To: framers@lists.frameusers.com Subject: FrameMaker/ePublisher issue Folks, I honestly do not know if this is a FrameMaker or ePublisher issue, but I thought I would first ask here first. We are currently using FrameMaker version 7 and have just upgraded to ePublisher version 2008.3. We also use a 3rd Party plugin for FM called AutoText to define tables or graphic items for selection via a pull down menu in FM. What we have noticed in the HTML and PDF output of our FM source files generated by the 2008.3 version of ePublisher is that symbols within the FM AutoText tables, such as the Monotype Sorts Pointing Finger or the Wingdings Warning Bell, are being substituted by other symbols in the resulting HTML and PDF output. For example, the warning bell symbol displays as a percentage symbol in the pdf output. We noticed these issues after upgrading to the 2008.3 version of ePublisher. All symbols appear correctly in the html and pdf output when generating via our earlier version of ePublisher. Has anyone else run into an issue such as this? If so, is it a FM issue or an ePublisher issue? Thanks in advance, Mark Eichelberger Senior Technical Writer Fiserv CU7 mark.eichelber...@aftech.fiserv.com ___ You are currently subscribed to Framers as manth...@palantirtech.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/manthony%40palantir tech.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker/ePublisher issue
On Mon, 5 Jan 2009 13:50:50 -0800, Mary Anthony manth...@palantirtech.com wrote: This is an ePublisher issue. I have run into it. You can search characters on the ePublisher support page: Wingdings characters present a particular challenge when working with HTML-based content. Since Wingdings (as well as a few other symbol fonts) conflicts with the Unicode character map, many browsers simply don't support it. Internet Explorer skirts the issue and displays these characters correctly. Yes, there is a browser issue here, but it is tractable. Mif2Go handles it automatically for almost all Wingdings and Symbol chars, and provides a simple way to map any others. From the User's Guide: ~~~ 20.5.6 Mapping characters in a special font Characters in special fonts such as Wingdings or Webdings might not be rendered correctly by non-Microsoft browsers; see ยง20.6.5, Accommodating browser font-rendering differences. However, you can direct Mif2Go to replace a character in any font with its Unicode equivalent, or with an image, or with any HTML code, by providing a macro section for that font in your configuration file. The following Web site suggests mappings from Symbol and Wingdings characters to the closest Unicode code points: http://www.alanwood.net With the kind permission of Alan Wood, we have incorporated these mappings as defaults for all Mif2Go HTML conversions. The defaults should handle all Symbol characters (except for one, the radical extender) and the majority of Wingdings characters. You can override the defaults, or set mappings for any characters that have no equivalent Unicode representation. ~~ We suggest that other vendors may want to do the same; Alan Wood's mappings are free for the asking, and the programming task is simple. WRT the OP's question, the Alan Wood site has mappings for your Wingdings, but not for your Monotype Sorts. You can, however, scan through the Unicode tables Wood references to find Unicode equivalents, which *all* browsers should support. HTH! HTH! -- Jeremy H. Griffith, at Omni Systems Inc. jer...@omsys.com http://www.omsys.com/ ___ You are currently subscribed to Framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
FrameMaker/ePublisher issue
Folks, I honestly do not know if this is a FrameMaker or ePublisher issue, but I thought I would first ask here first. We are currently using FrameMaker version 7 and have just upgraded to ePublisher version 2008.3. We also use a 3rd Party plugin for FM called AutoText to define tables or graphic items for selection via a pull down menu in FM. What we have noticed in the HTML and PDF output of our FM source files generated by the 2008.3 version of ePublisher is that symbols within the FM AutoText tables, such as the Monotype Sorts "Pointing Finger" or the Wingdings "Warning Bell", are being substituted by other symbols in the resulting HTML and PDF output. For example, the warning bell symbol displays as a percentage symbol in the pdf output. We noticed these issues after upgrading to the 2008.3 version of ePublisher. All symbols appear correctly in the html and pdf output when generating via our earlier version of ePublisher. Has anyone else run into an issue such as this? If so, is it a FM issue or an ePublisher issue? Thanks in advance, Mark Eichelberger Senior Technical Writer Fiserv CU7 Mark.Eichelberger at Aftech.Fiserv.com
FrameMaker/ePublisher issue
I'd say neither; it's probably a system/font problem. For example, the % sign is showing up because your system (or Acrobat Distiller) can't find the Wingdings font and is substituting another font. I'd check the Distiller settings to make sure that the Font Location is correct and maps all the fonts on the system. And, do you have the Adobe printer instance set as the system default printer? It's possible your Autotext string may munged up and isn't inserting the correct font info, but that should show up in Frame -- if it's correct in FM, the problem is happening in another program. Art Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358 On Mon, Jan 5, 2009 at 10:08 AM, Eichelberger, Mark wrote: > Folks, I honestly do not know if this is a FrameMaker or ePublisher > issue, but I thought I would first ask here first. > > > > We are currently using FrameMaker version 7 and have just upgraded to > ePublisher version 2008.3. We also use a 3rd Party plugin for FM called > AutoText to define tables or graphic items for selection via a pull down > menu in FM. What we have noticed in the HTML and PDF output of our FM > source files generated by the 2008.3 version of ePublisher is that > symbols within the FM AutoText tables, such as the Monotype Sorts > "Pointing Finger" or the Wingdings "Warning Bell", are being substituted > by other symbols in the resulting HTML and PDF output. For example, the > warning bell symbol displays as a percentage symbol in the pdf output. > We noticed these issues after upgrading to the 2008.3 version of > ePublisher. All symbols appear correctly in the html and pdf output > when generating via our earlier version of ePublisher. > > > > Has anyone else run into an issue such as this? If so, is it a FM issue > or an ePublisher issue? > > > > Thanks in advance, > > > > Mark Eichelberger > > Senior Technical Writer > > Fiserv CU7 > > Mark.Eichelberger at Aftech.Fiserv.com > > > > > > ___ > > > You are currently subscribed to Framers as art.campbell at gmail.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/art.campbell%40gmail.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. >
FrameMaker/ePublisher issue
Mark, My .02 cents. ? I am assuming that you are outputting to HTML. If this is the case, it is an HTML issue. ? Unless the basic font you are using contains the special character symbols, the HTML will interpret the character code for the symbol in the base font. We ran into this when using a Star (Zaph Dingbats capital H). In Frame it was fine. In the HTML it was an 'H', the base font equivalent.. --- On Mon, 1/5/09, Eichelberger, Mark wrote: From: Eichelberger, Mark <mark.eichelber...@aftech.fiserv.com> Subject: FrameMaker/ePublisher issue To: framers at lists.frameusers.com Date: Monday, January 5, 2009, 9:08 AM Folks, I honestly do not know if this is a FrameMaker or ePublisher issue, but I thought I would first ask here first. We are currently using FrameMaker version 7 and have just upgraded to ePublisher version 2008.3. We also use a 3rd Party plugin for FM called AutoText to define tables or graphic items for selection via a pull down menu in FM. What we have noticed in the HTML and PDF output of our FM source files generated by the 2008.3 version of ePublisher is that symbols within the FM AutoText tables, such as the Monotype Sorts "Pointing Finger" or the Wingdings "Warning Bell", are being substituted by other symbols in the resulting HTML and PDF output. For example, the warning bell symbol displays as a percentage symbol in the pdf output. We noticed these issues after upgrading to the 2008.3 version of ePublisher. All symbols appear correctly in the html and pdf output when generating via our earlier version of ePublisher. Has anyone else run into an issue such as this? If so, is it a FM issue or an ePublisher issue? Thanks in advance, Mark Eichelberger Senior Technical Writer Fiserv CU7 Mark.Eichelberger at Aftech.Fiserv.com ___ You are currently subscribed to Framers as dspreadb at yahoo.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/dspreadb%40yahoo.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
FrameMaker/ePublisher issue
Mark, This is an ePublisher issue. I have run into it. You can search characters on the ePublisher support page: "Wingdings characters present a particular challenge when working with HTML-based content. Since Wingdings (as well as a few other "symbol" fonts) conflicts with the Unicode character map, many browsers simply don't support it. Internet Explorer skirts the issue and displays these characters correctly." A solution is to use the character map to do a translation from one character to another. "To modify the ePublisher character map, you'll need to perform a simple overide of a file called 'mapentrysets.xml', which is located by default in the ePublisher Pro installation directory: ePublisher Pro\Formats\Shared\html For information on performing target overrides, please see their online knowledge base article here: http://www.webworks.com/technotes/articles/ePublisherPro/EX_ePub_Project_Format_Overrides.36.1.aspx Mary > -Original Message- > From: framers-bounces at lists.frameusers.com [mailto:framers- > bounces at lists.frameusers.com] On Behalf Of Eichelberger, Mark > Sent: Monday, January 05, 2009 7:09 AM > To: framers at lists.frameusers.com > Subject: FrameMaker/ePublisher issue > > Folks, I honestly do not know if this is a FrameMaker or ePublisher > issue, but I thought I would first ask here first. > > > > We are currently using FrameMaker version 7 and have just upgraded to > ePublisher version 2008.3. We also use a 3rd Party plugin for FM > called > AutoText to define tables or graphic items for selection via a pull > down > menu in FM. What we have noticed in the HTML and PDF output of our FM > source files generated by the 2008.3 version of ePublisher is that > symbols within the FM AutoText tables, such as the Monotype Sorts > "Pointing Finger" or the Wingdings "Warning Bell", are being > substituted > by other symbols in the resulting HTML and PDF output. For example, > the > warning bell symbol displays as a percentage symbol in the pdf output. > We noticed these issues after upgrading to the 2008.3 version of > ePublisher. All symbols appear correctly in the html and pdf output > when generating via our earlier version of ePublisher. > > > > Has anyone else run into an issue such as this? If so, is it a FM > issue > or an ePublisher issue? > > > > Thanks in advance, > > > > Mark Eichelberger > > Senior Technical Writer > > Fiserv CU7 > > Mark.Eichelberger at Aftech.Fiserv.com > > > > > > ___ > > > You are currently subscribed to Framers as manthony at palantirtech.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/manthony%40palantir > tech.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info.
FrameMaker/ePublisher issue
On Mon, 5 Jan 2009 13:50:50 -0800, Mary Anthony wrote: >This is an ePublisher issue. I have run into it. You can search >characters on the ePublisher support page: > >"Wingdings characters present a particular challenge when working >with HTML-based content. Since Wingdings (as well as a few other >"symbol" fonts) conflicts with the Unicode character map, many >browsers simply don't support it. Internet Explorer skirts the >issue and displays these characters correctly." Yes, there is a browser issue here, but it is tractable. Mif2Go handles it automatically for almost all Wingdings and Symbol chars, and provides a simple way to map any others. From the User's Guide: ~~~ 20.5.6 Mapping characters in a special font Characters in special fonts such as Wingdings or Webdings might not be rendered correctly by non-Microsoft browsers; see ?20.6.5, "Accommodating browser font-rendering differences." However, you can direct Mif2Go to replace a character in any font with its Unicode equivalent, or with an image, or with any HTML code, by providing a macro section for that font in your configuration file. The following Web site suggests mappings from Symbol and Wingdings characters to the closest Unicode code points: http://www.alanwood.net With the kind permission of Alan Wood, we have incorporated these mappings as defaults for all Mif2Go HTML conversions. The defaults should handle all Symbol characters (except for one, the radical extender) and the majority of Wingdings characters. You can override the defaults, or set mappings for any characters that have no equivalent Unicode representation. ~~ We suggest that other vendors may want to do the same; Alan Wood's mappings are free for the asking, and the programming task is simple. WRT the OP's question, the Alan Wood site has mappings for your Wingdings, but not for your Monotype Sorts. You can, however, scan through the Unicode tables Wood references to find Unicode equivalents, which *all* browsers should support. HTH! HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
