Free Webinar – Bulleted/Numbered List in RoboHelp 8 or 9 Want to learn tips and tricks with bulleted or numbered lists in old RoboHelp projects in RoboHelp 8 or 9? Join Neil Perlin in this free Hyper/Word Services webinar that explains:
Why styles are important.
How styles work in RoboHelp 8/9.
Why list items break, how to fix them, and how to use them correctly going forward.
Friday, Dec. 9, 11-12 AM ET.
This is the first of a series of free Hyper/Word Services webinars on RoboHelp, Flare, Captivate, Mimic, MobiFlex, mobile, and several other topics. This first webinar is a test of the system and is limited to 14 attendees. Please contact Neil Perlin at firstname.lastname@example.org to sign up.
What we are going to talk about today is another example of how Adobe FrameMaker 10 is all about increasing your productivity in an XML workflow. There is a host of enhancements and improvements. If you watch the video below, you will see how easy it is to add an attribute value choice parameter through a pull down menu across all instances of the attribute in your structure.
Here is the example. DITA has an audience attribute. This attribute can have any string value as per the DITA Spec. In reality, you probably want to limit the information that gets placed in the attribute to a specified list. This way you will have a much easier time filtering your content.
This is starting to make sense, but those of you who know how to create choice attribute values in your edd may say that this sounds like it’s just good for beginners. This is not the case. If you want to create a choice pull down for all instances of the audience attribute and not use this wizard, it’s going to take you a real long time. Using the Config File Maker wizard cuts that time down to minutes and you can reuse the config file that you make on many different projects.
This is a very powerful tool. Enjoy the video and spread the word.
DITA is a popular standard. Part of the reason for it’s popularity is it’s ability to be extended through the use of specialization.
Most “real” XML editors support DITA 1.1 and 1.2 out of the box. Giving you the ability to open, edit and save DITA content with no configuration required by the user. FrameMaker 10 is no different. You can take off the shrink wrap. Install it on your system and start editing, saving and publishing your DITA content within minutes.
It really does not take very long before you realize that although DITA is a great starting point, your situation requires you to create your own specialized topics. This is where it could get expensive if you choose a different XML Editor than FrameMaker 10. The big question is, what does it take to merge your DITA Specialized topics into your templates.
FrameMaker 10 makes it easy with a wizard. I created a quick video to show you how easy using the wizard is to merge your specialization and get your group up and working.
Most of today’s content authors are very familiar with FrameMaker’s Condition Text Feature. The ability to create condition names and tag our content for filtered publishing. We create one master set of documentation. Condition tag any differences in the content and filter publish multiple scenarios to pdf or print.
With Technical Communication Suite 3 (which of cause includes FrameMaker 10 and RoboHelp 9 with special integration) you can easily create a RoboHelp Adobe AIR Template that will understand how you conditional tagged your work in FrameMaker 10. From within FrameMaker 10 we can publish an Adobe Air Application that has complete dynamic filtering.
Of cause you can just do a file open in FrameMaker 10 of your past V.7, V.8, V.9 books and sections. FrameMaker 10 will easily upgrade those files and you to can do what I am showing you in the video. One more thing, although I’m showing you an XML example, it works just as well with your Unstructured FrameMaker files!
It’s best to see what I’m talking about. Enjoy the video and spread the word!
Today we are going to demonstrate how you can augment the new FrameMaker 10 XML Workspace Toolbar View with a customized menu configuration file that eliminates the format menu from the Maker Main Menu.
Today’s topic is about dispelling the rumor that FrameMaker is not a real XML Editor. Some people say this because FrameMaker has the ability to embed Processing Instructions into the XML Source. FrameMaker by default embeds these Processing Instructions. This gives the average user the ability to roundtrip Conditional Tags and Show / Hide setting without having to create an xslt stylesheet to filter their content on file open. FrameMaker of cause can also use xslt stylesheets to filter content, drop in Processing Instructions on open and delete them on save.
As you will see in the following video, you can always change FrameMaker’s default settings and have “pure xml” content at your discretion. FrameMaker is powerful and flexible. If you are in need of a recommendation of an Adobe Consulting Partner in your area that understands the power of FrameMaker, please do not hesitate to contact me.
I heard through the grape vine that there were some new misunderstandings about how FrameMaker and XML features work.
I am going to address today, one of my favorite new FrameMaker 10 XML features, view XML source. It has been said that you can not edit your XML code in notepad, if you use FrameMaker 10′s new feature to open it.
With that in mind, I pulled together quick captivate video that shows you exactly how you can both view and edit your XML statement in Notepad with a simple turning off of network file locking in your FrameMaker Preferences. I also show you how you can modify the default “View In Notepad” settings to have a choice of XML source editors. My personal favorite is Notepad++.
Ok, for you expert XML / FrameMaker users and developers, I have posted a zip file contenting everything you need to round-trip an edd in xml format with FrameMaker 10.
You may ask why. If you know about xslt, then you are starting to get the answer. Once you save your edd to xml you can apply xslt stylesheets to transform your edd globally. I use this most often when I want to add the same specialized elements, attributes and formatting content and level rules to a variety of different edd’s.
You will probably find other uses. Be sure to let me know how you use this new capability.