Tim Green wrote:if you're creating new links always use the new simplified syntax.
Yes Tim, but...
In EWriter <%HREF_CURRENT_PAGE%> always returns the .htm extension.
3rd attempt to explain what I'm doing.
From my project I am creating both EWriter help (using a V2 skin) and Webhelp (using a V3 responsive skin). The content is largely identical apart from a few conditional differences (e.g. the video file format).
I'm creating links in EWriter to open the same topic page in Webhelp on the user's browser. I can do this now that my app can fetch updated EWriter data packages from the server -- it means that I can keep the Webhelp and the embedded EWriter help always in sync.
Generally users prefer EWriter (if only for the much easier-to-use keyword index in V2), but may wish to swap to the same page in Webhelp for various reasons, e.g. they prefer the responsive design, perhaps on a smallish screen; they want to be be able to copy a page link for posting on the forum or in emails to friends; they are not happy to be viewing the help in IE and prefer Firefox (e.g. for F7 caret browsing and keyboard copying); etc.
But I can't use the new V3 simplified URLs for these links because
in EWriter <%HREF_CURRENT_PAGE%> always returns the .htm extension.
However, I have now got round this issue by using
for the links. This creates the new-format URL for future compatibility and is much easier to read for users.
The only downside is the need to ensure that the topic ID matches the file name exactly, i.e. all lower case and underscores only. I always manually modify the auto-generated topic IDs to ensure this is the case, but I just need now to go back and double check that I have done all of them. I'm still mourning the one and only H&M6.x version which used to do this automatically -- I never could understand why it was changed, but we don't want to fight that battle again.
regards,
Martin.