[Framers] [FrameMaker 2019] Customizing responsive HTML5 output: best practices and good documentation?

[Gust, Dieter]

Sorry bad English - instead of exclamation marks I should say quotation marks

> I just tested FM 2019 15.0.3.603

"If you use "quotation marks" around the numeric sequence, the search works the way you want it to."
And Yes if you insert Index entries for any of these product designations like "123.456".
HTML would include an index search.



[cid:image003.jpg at 01D500EE.67CF6840]



Dieter

itl AG, München

+49 89 892623-600

-----Ursprüngliche Nachricht-----
Von: Framers <framers-bounces+dieter.gust=itl.eu at lists.frameusers.com> Im Auftrag von Gust, Dieter
Gesendet: Donnerstag, 2. Mai 2019 11:25
An: An email list for people using Adobe FrameMaker software. <framers at lists.frameusers.com>
Betreff: Re: [Framers] [FrameMaker 2019] Customizing responsive HTML5 output: best practices and good documentation?



Hi Winfried,



additional answers:



5.) "Most of our products have order codes like 123.4567. When I want  to search for such order codes, the . is interpreted as separator between   two words. As if I want to search for 123 and 4567. I do not know a solution."



I just tested FM 2019 15.0.3.603

If you use exclamation marks round about the numeric sequence search works the way you asked for.



6.) In my tests in update 15.03.603 search term highlighting works!



-----Original Message-----

From: Framers <framers-bounces+w.reng=carecom-solutions.com at lists.frameusers.com<mailto:framers-bounces+w.reng=carecom-solutions.com at lists.frameusers.com>> On Behalf Of Gust, Dieter

Sent: Tuesday, April 30, 2019 10:56 AM

To: An email list for people using Adobe FrameMaker software. <framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>>

Subject: Re: [Framers] [FrameMaker 2019] Customizing responsive HTML5 output: best practices and good documentation?



Hi Winfried,

you recognized the different layout/formatting concept between Desktop FrameMaker with Paper/PDF Editing view and the different HTML layout and box model.

1.) "I do not know which font will be used. "

Font substitution you may define in the resulting CSS. Once defined you can use the CSS as part of the general conversion settings

2.) a) "Graphics conversion with SVG is best"

Sure it remains SVG

2.b) "However, if you have   some other objects in the same anchored frame, then you should  convert to raster images. I find the results much better than I expected."

This is the standard approach as the layer concept (as defined in FM) is not supported by the HTML conversion process The quality has been dramatically improved upon the several updates

3.) "When you have tables with table titles with several paragraphs, then  you have to use a work-around. HTML allows only a single paragraph."

    See here: https://forums.adobe.com/message/10987920#10987920

4:) "I do not know how I can define which text goes into a topic title.   E.g. when my paragraph to start a new topic has a table anchor, then   the whole anchor paragraph and the whole table text will be in the topic

  title."

  Well that's clear, as the table anchor defines the position of the content of the table within the text flow. This table anchor is a DTP relict.

  Therefore in my templates tables must be anchored in an separate paragraphs called table anchor.

In addition topic title" is a very difficult term which is often misunderstood: For a customer a topic title always is the first paragraph in a HTML Topic and therefore it shall start with a heading.

If the topic content does not start with a heading the technical writer created a structural mistake.

In technical aspects the topic title might be interpreted as the HTML title tag. Therefore the conversion or topic creation process clearly must take into account that the first paragraph (heading) and the topic title will get the identical content.

A third aspect might be seen in the filename of the HTML topic: This can be but only "by accident" identical with the topic title but never should be taken as the standard topic title!

5.) "Most of our products have order codes like 123.4567. When I want  to search for such order codes, the . is interpreted as separator between   two words. As if I want to search for 123 and 4567. I do not know a solution."



6.) In my tests (FM 2019) using "wx.yz" seems to work, but highlighting didn't work - I'll ask the FM development team regarding this issue Regards Dieter Gust Aufsichtsrat, Leitung Forschung & Entwicklung itl AG, München



_______________________________________________



This message is from the Framers mailing list



Send messages to framers at lists.frameusers.com<mailto:framers at lists.frameusers.com> Visit the list's homepage at  http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/

Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com

Send administrative questions to listadmin at frameusers.com<mailto:listadmin at frameusers.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 11955 bytes
Desc: image003.jpg
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20190502/5e1fccb7/attachment.jpg>