I am using Framemaker 188.8.131.523 under Windows 7.
I have defined paragraphs for notes, warnings and cautions that use an autonumber at the beginning, so that I will have Note: and Warning: and Caution: in front of my paragraphs. And the content of the paragraph I wanted to not be underlined (so the rest of the paragraph does not have the underline setting), so I defined it like in the screenshot below:
In framemaker it looks fine but if I save it to PDF using RGB setting it prints out a small underline in front of my paragraphs, see below:
But if I print using CMYK setting it doesn't print this line:
But I really need to print my files using RGB setting, so can you please tell me why if I use RGB setting it prints out that small underline?
What font is being used and what character is placed after the colon?
The font used is Arial.
In the above example I didn't put anything after the colon...but it doesn't matter...whatever I add after the colon it will have that small underline in front of it, but only in the pdf (if I print it with RGB).
RGB printed PDF:
CMYK printed PDF:
This might be related to an already filed bug in FM2015. See the following thread unwanted characters coming in pdf and bug report Bug#4116896 - Zero-width FM characters (anchors, markers, etc.) print artifact when underline is set...
Is there a marker (or anchored frame) at the beginning of these notes, warnings, etc. ? If so, try moving the marker to the end of the entry.
If this (re)moves the spurious line, then add a vote to the bug and describe your situation.
In the unlikely event that FM2015 has support for Unicode combining (non-advancing) diacriticals, a work-around would be to dispense with the underline Character Format assigned to the Autonumber format, and use instead text string:
U+0332 is COMBINING LOW LINE
I might further remark that if these headings involve matters of personal safety, underlining, with or without bolding, may not meet ANSI, IEC or industry or liability carrier standards for admonishments including CAUTION, WARNING and DANGER. See also Re: Define variable as caution icon
@Bob Niland (Error 7103) Nice workaround, but there is a small space between the underline of "N" and the rest "ote" and if I use all uppercase letters (NOTE), each letter will have a separate underline.
@Arnis Gubins I think it's definitely related to the Bug 4116896. But I do not have any markers at the beginning of the paragraph. But I do have a tab stop defined after NOTE: using \t .
An workaround would be to not define the tab stop and enter space after the autonumber, but this is affects productivity as I have to enter manually the desired space after each NOTE, WARNING and CAUTION.
re: Nice workaround, but there is a small space between the underline of "N" and the rest "ote"
But it otherwise worked, and didn't display as
If so, I'm impressed. Despite having such such retreating diacritics in the Unicode standard for over 20 years, support for them is not exactly universal yet.
re: and if I use all uppercase letters (NOTE), each letter will have a separate underline.
You might be able to get those gaps to join by playing with Spread and Stretch in the Paragraph Designer, in which case.
might solve your problem until the bug is fixed.
Are you using the default underline? If so, try a numeric underline inthe Character designer instead. This just moves it a bit lower.
You could also try putting a thin-space character between the colon and the tab. This might break the tendency for the underline to overshoot the characters.
Tried the numeric underline, it doesn't work.
Tried putting a thin space after the colon, but that also doesn't work. I have also tried other spaces or separation symbols (Nonbreaking space, En Space, Em space, Numeric space, End-of-flow symbol, End-of-paragraph symbol). Nothing works, as long as I have defined a tab stop, it will try to underline the "invisible tab stop symbol".
The only solution I see for this case is to not define the tab stop, and enter the space manually.
Please file a new bug report or cast your vote to the previous bug report (Bug#4116896 - Zero-width FM characters (anchors, markers, etc.) print artifact when underline is set...) and add your example of how it is failing.