You are viewing limited content. For full access, please sign in.

Question

Question

Is there any way to access and expanded character sets?

asked on September 13, 2018

Is there any way to access and expanded character sets available within, for example, multi-value fields? There are certain characters and symbols that Forms will not accept. When we try to cut-and-paste from Word, the symbols get stripped.

Example 1: The way a bilateral tolerance is drawn is “+”. Forms does not allow for underlined text nor does it allow the use of the equivalent symbol (Unicode character 0081). This forces us to either refer to an image attachment or use a facsimile such as “+/-“.

Example 2: Diameters are called out on drawings using “Ø”. In Word, this is entered in one of two ways, typing CTRL / + O or inserting the equivalent Unicode character. Neither is permitted when entering directly in Forms.

I suppose the answer is only plain text is available but, for our application, would be much more usable if it had a Word-like character set, permitted things like underlined text, superscripts and subscripts, and allowed the use of common symbols.

0 0

Answer

SELECTED ANSWER
replied on September 13, 2018

Maybe I'm misunderstanding the question, but both of those characters are available in high ASCII--they don't require unicode. Both are working for me on 10.3.1.

  • ± - Alt+0177
  • Ø - Alt+0216
1 0
replied on September 17, 2018 Show version history

Good to know it works on 10.3. We are in the process or scheduling our upgrade. Thank you!

Update: It just tried in 10.2 and it worked. I'll let the users know they can use the Alt + a number.

0 0

Replies

replied on September 13, 2018

In Forms 10.4, we will be adding a new field type for rich text. This Rich Text Field will allow you to format your text using bold, italics, strike through and underline, you can use bulleted or numbered lists, justify the text to one side, even change the font size and add links. 

I also just checked, the Ø character works fine when pasted into the RTF field. 

0 0
replied on September 13, 2018

Thank you!

The issue with the Ø character was not that it didn't keep but that it couldn't be created directly in the field. It had to be copy/pasted from the Word file.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.