Matt-Tech Comm Tools

Community Expert

Community Expert

Question

target="_blank" hypertext marker parameter not processing properly to HTML

Forum|Forum|8 years ago
April 5, 2018
1 reply
510 views

Using Fm 14.0.4, when inserting a Go To URL hypertext marker, marker text of message URL https://forums.adobe.com/ works as expected in HTML output, replacing the source page with the destination.

However, I can't figure out the marker text needed to return <a href="https://forums.adobe.com/" target="_blank"> in the HTML output.

Which is unfortunate, because I tested this in Fm 14.0.0 and was able to use this string message URL https://forums.adobe.com/" target="_blank to give the <a href="https://forums.adobe.com/" target="_blank"> result I'm looking for.

Has anyone done this successfully in 14.0.4?

EXAMPLES with RESULTS

message URL https://forums.adobe.com/ target=_blank returns <a href="https://forums.adobe.com/  target=_blank">

message URL https://forums.adobe.com/" target="_blank returns <a href="https://forums.adobe.com/" target="_blank">

Suggestions for referencing HTML entities in Fm markers greatly appreciated!!!!

-Matt

This topic has been closed for replies.

Community Expert

Community Expert

Not clear that the dialog allows you even pass any HTML attributes, since you aren't actually authoring an <a tag.

But if you can, then you also need to get FM to stop trying to outsmart you on quotes.

I had to use
url target=\x27_blank\x27

just to get it to stop messing with the single quotes
(and then it emitted the space as %20,
so I wasn't able to get anything to work)

Matt-Tech Comm Tools

Community Expert

Author

Community Expert

Yep...I suggested they simply switch their syntax to HTML for the hypertext markers so we can more directly edit without having to guess when/where the quotes and entities will be parsed.

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant

Community Expert

Community Expert

re: ...suggested they simply switch their syntax to HTML for the hypertext markers...

Legacy issues, I imagine. Hypertext existed before HTML, and the initial FM implementation may have been limited to the sorts of HT that Postscript, and early PDF, could do. If arbitrary HTML were allowed, it would have to at least safely do nothing in particular in .ps and .pdf workflows.