All my product documentation uses it, and slowly, more and more people are coming to me and asking where they can find my template for their documents, having seen what their colleagues have produced. Until I joined, there was no such thing as a corporate template for technical documents, so I set one up, and passed it round to anyone who asked for it. Also, I work for a small company, and have a lot more leeway over my document styles and less corporate policy to implement. So Flare actually won hands down over Word for me, and I was left with a minor niggle, not a major rant. To redo the front pages, headers, footers, fonts, colours etc took me about an hour in Flare for all the documents I'd ported to Flare so far, and took me an hour each for the Word documents (and I did the minimum change I could get away with, since one day these will be in Flare too). However, I had a large number of number of Word documents to rebrand as well as the Flare ones. I discovered about Flare's lack of support for OTF a couple of days before you did. I hope you understand my dilemma and why I am so darn annoyed with MadCap right now.Ĭoincidentally, my company did a rebranding exercise recently, and, like your company, selected an OTF for the company branding. so when I receive Adobe source, it is looking for the OTF versions of the same fonts. If you are wondering why I don't just use the TTF fonts, I can't because our graphics designer is only using the OTF fonts. All I know is that I cannot have the same TTF and OTF fonts installed simultaneously.
Otf vs ttf does it matter windows#
do I uninstall Flare and reinstall it in a special VM Windows environment, loaded with TTF fonts OR do I uninstall the TTF fonts and re-install the OTF fonts whenever I need to work in the Adobe Suite? Then re-load the TTF fonts when I need to work in Flare again. I'm going to be their biggest PITN ever over this issue.īTW, I have a decision to make. Holiday cheer aside, I'm going to make it my mission to bug MadCap until this is fixed. Who is with me? Please post a comment here with your agreement or argument for/against.ĬhoccieMuffin wrote:If anyone else agrees, use the link in my signature to post a bug report. Support for Open Type (OTF), Embedded Open Type (EOT), and Web Open Font format (WOFF) are all becoming increasingly supported.Īnyhow, I am arguing with MadCap that this is an important bug (not a feature request) that must be addressed soon.Ī MadCap CS agenda has filed a bug report number 83249 about this issue BUT it may be rejected as a bug and thrown back to a feature request that may continue to be ignored for many more years. Wrong (well unless you really don't care). I suppose if you only use Flare to produce Web content, OTF is not relevant. MadCap products stand alone and this isn't a compliment! It is nearly impossible to find another (relevant) Windows product that is incompatible with OTF. All Adobe products have exclusively used OTF fonts going back almost that long ago. Microsoft, Adobe ratified and embraced this font specification about 11 years ago. Print publication text may often look better with an OTF font. Most or all commercial fonts default to OTF. Because OTF is a vast improvement over the old TTF standard.
about this long (over 5 years) occurring failure of MadCap product's inability to use the ISO/Windows standard OTF font. Newly-installed font not appearing in Font Family Picker Installed font not showing up in Font Family PickerĪdding a new font family to Flare 9.x huh? Many of you may have seen my recent rants:
0 kommentar(er)
