Copy link to clipboard
Copied
Hey gang,
I've got a document that requires me to place mathematical symbols in text. Some of these symbols don't have a Unicode component, e.g., the letter "V" with a vector arrow (→) over it. In Word, for example, you would type a letter, add the four-character Unicode and press ALT+X, or use the "Insert Symbol" dialog box. This doesn't seem to exist in Frame. Am I overlooking something?
TL;DR: Is there a way to combine diacritical marks in Frame to replicate this, or am I stuck using the Equation Editor?
Regards,
-terry-
FrameMaker 11
Windows 7 (64-bit)
You can try using FM's micro-positioning with the two glyphs. Select the character, hold the Alt key and then press the arrow keys to move the glyph in the desired direction.
Note: the amount of movement is sensitive to your current zoom level. The higher the zoom level, the less movement (i.e. more finesse).
Tip: if you need to use these characters a lot, create a text frame on (one of) your Reference pages and then create the combined characters. You can then copy&paste as needed.
Copy link to clipboard
Copied
You can try using FM's micro-positioning with the two glyphs. Select the character, hold the Alt key and then press the arrow keys to move the glyph in the desired direction.
Note: the amount of movement is sensitive to your current zoom level. The higher the zoom level, the less movement (i.e. more finesse).
Tip: if you need to use these characters a lot, create a text frame on (one of) your Reference pages and then create the combined characters. You can then copy&paste as needed.
Copy link to clipboard
Copied
re: You can try using FM's micro-positioning...
Does that translate to:
FM'15 still doesn't support Unicode combining diacritics?
Have there been any major enhancements to Unicode support since FM8?
If an FM release, later than the FM11 at issue here, does support Unicode's combining diacritics, that might break existing documents that worked around the lack of support for these retreating glyphs. That suggests that anyone using the micro-positioning technique might want to use standard (non-combining) characters as the diacritics, where available. Their behavior might be expected to not change later.
Copy link to clipboard
Copied
Just to re-revisit this for FM2019 (15.0.5.838), FM support for Unicode combining character is still some ways from optimal (and that's in addition to FM not yet rendering Unicode SMP at all; code points above U+FFFF).
FM is more or less elegantly handling cases where a decomposed base character plus a combining character can be collapsed into a single precomposed Unicode code point. An example might be:
U+0061 LATIN SMALL LETTER A
followed by
U+0300 COMBINING GRAVE ACCENT
entered as body text or even as a\u0300 in dialogs, it is collapsed to a
U+00E0 LATIN SMALL LETTER A WITH GRAVE
Where there is no composition pathway, the base+combined get rendered on top of each other, but usually inelegantly, and that includes the case in this thread: V plus U+20D7 COMBINING RIGHT ARROW ABOVE
Until the FM Unicode engine gets enhanced for this, perhaps doing it as a Rubi might be worth a look.
Copy link to clipboard
Copied
You can also create a Character Format to position a diacritical, but you have to use MIF to do so, because no GUI is provided:
<Para
<Unique 999266>
<PgfTag `Body'>
<ParaLine
<String `B'>
<Font
<FTag `'>
<FDX -41.66%>
<FDY -27.77%>
<FDW -20.0%>
<FLocked No>
> # end of Font
<String `’'>
<Font
<FTag `'>
<FLocked No>
> # end of Font
<String `C'>
> # end of ParaLine
> # end of Para
<MIFFile 12.0>
<FontCatalog
<Font
<FTag `my_character_format_name'>
<FDX -41.66%>
<FDY -27.77%>
<FDW -20.0%>
<FLocked No>
> # end of Font
> # end of FontCatalog
# End of MIFFile
You can then use the Character Format to position the diacritical, and any others of similar size. Because the values are percentages, and so relative to the fnt size, you can use it in different contexts.
Copy link to clipboard
Copied
Arnis and Mike,
Thanks for your help. Arnis' solution works in the short term, and I'm working on Mike's solution for the long term. As for you, Adobe...little help here? I can't be the only person worrying about this.
Thanks again, guys!
-terry-