It might be because my Adobe suite is a bit old now, CS2, but considering it's a font I made, it's probably my fault. But since I created it in order to use it in InDesign, it is a bit problematic. FontForge has support for many macintosh font formats. It works fine in Word and other places I tried, just InDesign (And Illustrator). FontForge- An outline font editor that lets you create your own postscript, truetype, opentype, cid-keyed, multi-master, cff, svg and bitmap (bdf, FON, NFNT) fonts, or edit existing ones.Also lets you convert one format to another. I figured it might be linked to the design itself, so I copy-pasted the apostrophe of a "real" font, but it won't display either. I ran back "Find Problems.", but it can't see anything wrong with it. This is where I encountered a problem: The apostrophe won't display in InDesign, I only get the little square. ![]() I followed the steps here: to troubleshoot it, fixed all the issues (and there were a lot, since it is the very first font I've designed), then exported it to test it out. Should be sufficient to escape them.I just finished designing a font with FontForge. Similar already existing surrogates for ASCII " (hex 22) are available, although I assume that they seldom appear in translated phrases. No need to misuse quotation marks, which semantically have a different purpose. The first is ASCII, the second is U 02BC MODIFIER LETTER APOSTROPHE (Block "Spacing Modifier Letters"), also present in the Liberation font, and the third is U 055AĚRMENIAN APOSTROPHE. You don't need to invent "fake" apostrophs because, at least in DejaVu Sans/Sans Mono/Serif, you can choose from 3 different apostrophs: n'est nʼest n՚est. Even if you manage to define your own glyphs, which you certainly can do, using one of the "private use" code blocks, you have to make sure that all of your users will use your hacked font and use no other font. 1 I have an experiment that checks for the existence of a string of characters. Of course, my XeLaTeX input file uses the. Most of my GTK themes use DejaVu Sans, so I would start with editing that font. I just tried (without even generating a sfd) with a pfb pfa font I have and I do not experience that problem. In the Hebrew Unicode section, the apostrophe becomes geresh. Some cosmetic information (like lookup names) are not saved to the TTF file (the TTF structure does not have them, they are mainly cosmetic to help FontForge users), upon opening the font FontForge will 'generate' new names, so if that is the only difference it should be harmless, else please show us the files to compare. In UTF-8, the character is only the one-byte ASCII. The above link shows the neutral apostrophe as U 0027, multibyte, but that would be for UTF-16. There, go to Input Sources Scroll to languages and click on languages and input settings. On Mac, go to system preferences and click on Keyboard. The keyboard on your OS needs to be set at US Standard and not US International. That is, they are different glyphs, just look the same as the single-byte ASCII characters.Ī clarification: UTF-8 recognizes the 8-bit (one byte) ASCII characters, including ' and ". The apostrophe issue is most likely due to the keyboard settings on your computer's operating system. So, the question I am posing, for the truetype fonts that we are using in our pup, would it be easy to use a tool like Fontforge to duplicate ' and " as multibye characters and add them to the font? Then, we would completely eliminate any need to escape them. Anyway, the need to escape the ' and " characters can be completely avoided by having two extra characters (glyphs) in a truetype font that are multibyte and look exactly the same as the ' and " characters. FontForge will be able to check for more problems if you: AutoHint the font first. I am wondering if I am over-thinking this, perhaps in practice it is not such a problem. ![]() The same problem can occur with the neutral double-quote character, it may need to be escaped. ![]() ![]() Code: Select all VAR1='Sortie anticipée du script d'\''initialisation, rien n'\''est encore monté.'
0 Comments
Leave a Reply. |