Skip to main content
NinaBR
NinaBR
Inspiring
January 8, 2020
Answered

Greater/Less Than or Equal To Symbols

  • January 8, 2020
  • 2 replies
  • 14762 views

Hello and Happy New Year!

 

I'm working on a document that has a lot of instances of "greater than/less than or equal to" symbols. From what I can figure out, there are two ways to do these in FrameMaker

 

1) Ctrl+q # / Ctrl+q 3

2) Alt+0163 / Alt+0179

 

Neither of these are working for me. Both sets result in symbols, but not the symbols I'm looking for.

I can't find either of these symbols on the character palette. It's possible that they're there, but my aging eyes can't see the small type. If someone can tell me where they're located there, I would appreciate it.

 

Ideally, I'd like to know what, if any, combination of keys I can type to get these two symbols.

I am in FrameMaker 15, using Windows 10.

 

Thanks!

    This topic has been closed for replies.
    Correct answer Bob_Niland

    The keyboard short cuts, and the Windows Alt codes may have changed with Unicode (and FM8 and later).

    In Unicode these two characters are at ≤ (U+2264) and ≥ (U+2265).

     

    When I need a character not on the keyboard, I've found it easier to do & maintain by using FM Variables. For these I would use:
    Name: U+2264 LESS-THAN OR EQUAL TO
    Definition: \u2264
    Name: U+2265 GREATER-THAN OR EQUAL TO
    Definition: \u2265

     

    Name is the Unicode U+ code point and formal descriptor. These sink to the bottom of the Variables pod, so don't get in the way, and self-organize by code point.

     

    This technique is also useful where your font doesn't actually populate the desired glyph, yet. The Definition might then have to invoke some other Character Format to invoke a font that does, or even be \x## hex code and legacy overlay font Character Format. But the variable Name memorializes the intent, for future document stewards.

    2 replies

    LinSims
    Community Expert
    LinSimsCommunity Expert
    Community Expert
    January 8, 2020

    Most of the time this is an issue when the font you chose doesn't support the symbol you want. You need to be sure your font supports Unicode. The Frame shortcuts will work then. I know, because I've used them. 🙂

     

    This page will show you all the glyphs supported in the font you chose.

    This site, although it hasn't been updated in a while, will provide you with the names of fonts that support particular ranges of Unicode. When in doubt, use Arial Unicode MS. It has over 38K glyphs.

     

    Whatever font you pick needs to include the Mathematical Operators unicode range. The site I gave you provides a list of fonts with math operators here.

    NinaBR
    NinaBRAuthor
    Inspiring
    January 8, 2020

    I use Arial for just about everything, which is part of why I was scratching my head. Thanks for the links!

    LinSims
    Community Expert
    LinSimsCommunity Expert
    Community Expert
    January 8, 2020

    Oh, yeah, and what Bob said. For things I use frequently that aren't easily found on the keyboard (or for which I haven't memorized the ANSI code), I create a variable and paste the symbol in to the definition from the Windows character map (after making sure that the correct font is selected—we use Source Sans Pro at my current job). Or a combination of characters: I have a lot of the standard fractions defined in a separate template file so I can import them when necessary.

    Bob_Niland
    Community Expert
    Bob_NilandCommunity ExpertCorrect answer
    Community Expert
    January 8, 2020

    The keyboard short cuts, and the Windows Alt codes may have changed with Unicode (and FM8 and later).

    In Unicode these two characters are at ≤ (U+2264) and ≥ (U+2265).

     

    When I need a character not on the keyboard, I've found it easier to do & maintain by using FM Variables. For these I would use:
    Name: U+2264 LESS-THAN OR EQUAL TO
    Definition: \u2264
    Name: U+2265 GREATER-THAN OR EQUAL TO
    Definition: \u2265

     

    Name is the Unicode U+ code point and formal descriptor. These sink to the bottom of the Variables pod, so don't get in the way, and self-organize by code point.

     

    This technique is also useful where your font doesn't actually populate the desired glyph, yet. The Definition might then have to invoke some other Character Format to invoke a font that does, or even be \x## hex code and legacy overlay font Character Format. But the variable Name memorializes the intent, for future document stewards.

      NinaBR
      NinaBRAuthor
      Inspiring
      January 8, 2020

      Bob, that makes so much sense, and it works!! Thank you! I appreciate your clear explanation -- very helpful!

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices