LTinker68 wrote:It should be single quotes, not double quotes, around multi-word font names. I have NO problems with this font family in Visio, Word, and the Adobe CS6 suite. The converted to TTF fonts works in all my other applications (that use fonts). Proxima Nova is our brand standard, I need my documentation to use this font family. "CSS: D:\Flare_Projects\UserGuide\Content\Copyrights.htm: CSS: Invalid line-height: Nova" What is it doing? If I attempt to change the font in the Styles edit under "body", Flare adds "Nova" to the "line-height" property. I don't understand why Flare is making this error.ĥ. css here:įont: calibri Please ensure that you have met "īut that isn't even the correct name for the font family! That is a specific font within the family.
I just examined my output and found that Flare is still not using the Proxima Nova font!įor planning purposes (knowing that we were still working out our branding for a new company), I was careful to minimize the number of times that I specify the font name.īasically, it is defined in the. This is frustrating because the translation from OTF to TTF is NOT lossless! So far, I haven't noticed any issues but I think I might, once I go to press. net foundation are the MadCap products using? Certainly the foundation has supported OTF (with outlines) since v3.5 and that was over five years ago!
#Dot vs otf vs ttf software#
net excuses aside, it is simply mind boggling that the MadCap products are almost exclusively the only software incompatible with OTF.
#Dot vs otf vs ttf iso#
OTF has been an ISO standard font format and Windows compatible since the days of Windows XP! I'm going to argue that decision since one of the minimum standards for any Windows application is to see the all the installed/compatible Windows fonts. I submitted a bug report but it was changed to a feature request #83112.
Why do you think we have to deal with the crusty NTFS from three decades ago while there are plenty of much better journaled file systems out there that do not have restrictions from the DOS days. Not saying that a fix isn't welcome, but with the rampant presence of the "not invented here"-syndrome at Microsoft I doubt a fix will come anytime soon.
Other Windows apps might have no problem because they are not running on top of. If one settles on a runtime then the runtime's flaws and weaknesses get inherited. RamonS wrote:It is not a Windows limitation, but a.
0 kommentar(er)
