Technical Communication

Technical Communication: FrameMaker Archives,FrameMaker,DocTrain,Technical Communication,XML authoring,PDF,CMS,conref,MIF,cross-reference,WebDav,STC,Publishing,Patch,p273

 

We heard!           We worked!           We fixed!

 

Hello everyone

I am just back from the great ‘DocTrain West’ Conference held at Vancouver. I was really excited to discuss the interesting ideas and thoughts you shared with me in relation to both the short term and long term strategies. As I continued meeting you people, some of you told me about a few issues still faced by you in your workflows. We have been listening to you and we have fixed these problems through yet another patch 8.0.3.

FrameMaker 8.0.3 patch is live now and it is available through Adobe Update Manager (AUM). This patch (8.0p276) must be applied on top of 8.0.2 (8.0p273) only. You can check for updates through Help->Updates Menu in FrameMaker. Currently this update is available for English, French and German installations and we would shortly make it available for Japanese too.

With the help of these fixes, following workflows are now enabled/supported:

• DITA conrefs get resolved properly.
• Extended characters do not have a preceding space when using Arial Unicode MS font.
• Higher code point characters are not dropped on MIF open.
• FM catalogs sort properly.
• Quotation marks look as per the expectation in documents with Chinese, Japanese and Korean combination fonts.
• While using combined fonts, non-Asian characters present in the Asian font are now displayed using non-Asian fonts.
• Random letters do not disappear from text line present in oval within anchored Frame.
• Use of page range in Index does not randomly add question marks left and right in the generated index file.
• Characters do not become invisible on the screen on the next line while hyphenating words just before the accented chars.
• The NextPfgTag is correctly applied when pressing Enter at the beginning of the line.
• FM does not crash when a document containing hypertext (spread over two lines) to marker is saved.
• FM spellchecker uses user.dct entries
• History palette records typing command in text line.
• FM does not crash on saving a file after deleting split-ed text line.
• Pressing space button at the start of line does not place cursor at the end of line.
• Drag does not fail even if the target is a locked range.
• For a 3D imported by reference, on moving it from hidden to show all after applying conditional text, the referenced path is not lost.
• FM does not crash when a graphic file with object properties dialog open is overwritten at the system.
• Importing object to the second file when "Quick Access Bar" and "Formatting Bar" are open and then closing the file, does not crash FM.
• Converting a cross-reference to text does not crash FrameMaker when the format of the cross-reference has been edited.
• Performing a find change using the backwards option does not lead to a crash.
• Change All operation of a character does not crash FM.
• When an equation is applied in conditional text and hidden, it does not lead to a crash.
• The hyphenation of words in old Netherland language does not change character case.
• In Netherland language words do not get corrupted when un-hyphenation is done with the words having dieresis.
• Garbage characters are not shown in Tab stop list box if a legacy file containing higher ANSI characters in Align field of decimal tab is opened in FM 8.
• Japanese tab stops now work in FM 8.

 

This patch has fixes for some more issues not listed above.

Please install this patch on top of 8.0.2, retest your workflows and share your feedback with me.

 

Thanks

-Mahesh (mahesh@adobe.com)

Posted by Mahesh Kumar Gupta at 08:11 AM | Permalink | Comments (0)

Adobe Technical Communication Suite,RoboHelp,FrameMaker,Lists,import,HAT,Help Authoring

Adobe RoboHelp 7 and Adobe Technical Communication Suite enable you to convert the FrameMaker paragraph styles with autonumber formats to HTML lists.  After import is complete, you can add or delete list items and the numbering of the list items will change accordingly.

a. Style Mapping - You can map the FrameMaker paragraph styles to new styles in RoboHelp and control the indentation and numbering format through the style definition.   Through style mapping, you can customize the display as bullet, (a), (i) or 1,2,3.

b. Complex and Nested lists - RoboHelp will convert complex list numbering to a single enumeration, for example, list item with number format 1.1.(a) will be enumerated as (a), preceding 1.1 will be lost.  Also, please note that RoboHelp considers the string of building blocks, for example, <n> <n> <a> etc to determine the levels in lists. 

• Named lists in FrameMaker - At present, RoboHelp does not change the level of lists based on names used in autonumber format in FrameMaker.  The solution is to use an empty building block in autonumber format to skip a level. For example, if you are using "A:<n+>." as the autonumber format for level 1 list and "a:<a+>" for level 2 list, change the autonumber format for the level2 list from"a:<a+>" to "a:< > <a+>".
• Using building blocks in Autonumber format -If you are using auto-number formats to display numbering like 1.0, 2.0, 3.0 and have sub-lists 1.1, 1.2, 1.3, please make sure you are using autonumber format in level 1 paragraph style as "<n>.0" and not "<n><n=0>".  If you use the second definition in autonumber format, RoboHelp treats the paragraph style as part of level 2 list.

c. Ignore Autonumber Properties - You can also select to ignore auto-number properties for specific styles.  If you choose to ignore auto numbering, the paragraph style will not be mapped to a HTML list in RoboHelp.

If you choose not to "Convert AutoNumber to HTML list", all paragraph styles in FrameMaker will be converted to paragraphs and the numbering, bullets etc will become part of the paragraphs.  You can still map FrameMaker styles to RoboHelp styles as mentioned in (a) above.

Posted by Vivek Jain at 08:04 PM | Permalink | Comments (0)

Adobe RoboHelp,HAT,Technical Communication Suite,Performance,MDI,Fonts

As you are aware, we implemented Multiple Document Support (MDI) in Adobe RoboHelp HTML 7. However, this change resulted in a small performance bug on systems having large number of fonts installed on your system.

I request customers to remove the extra fonts that they were not using for enhancing problem and believe me I hated stating that. However, today I am happy, as we have fixed the problem and the fix is available through Tech Note - 40336 on Adobe.com. All you have to do is download a single dll and replace it in the Adobe RoboHelp HTML 7 installation.

- Akshay

Posted by Akshay Madan at 07:12 PM | Permalink | Comments (0)