Hello everyone,

Hope you are well. I am pleased to announce the availability of 3 key new and 
improved FrameMaker related documentation.


1.       We have provided documentation on couple of .ini files that come with 
FrameMaker. The first of these files is maker.ini, which has several flags 
through which you can control various aspects of FrameMaker. In addition, we 
are also providing documentation on the new ditafm-output.ini file in 
FrameMaker 11. Thought the flags in this file, you can generate professional 
looking PDF output easily from your DITA content (e.g. you have options for 
automatically generating TOC/ Index, setting numbering options, specifying 
templates etc.)

a.       For more information on what the documentation covers, please see the 
blog post http://blogs.adobe.com/tcs/2012/10/uncategorized/iniref.html

b.      The documentation for both these .ini files can be found at 
http://help.adobe.com/en_US/framemaker/ini/framemaker_11_ini_reference.pdf



2.       Updated FDK11 documentation (including what's new) is also available 
now

a.       For more information on FDK11 documentation, see the blog post 
http://blogs.adobe.com/tcs/2012/10/uncategorized/fdk-11-documentation-now-available.html

b.      FDK11 documentation is available at the FrameMaker devnet page 
http://www.adobe.com/devnet/framemaker.html

Thanks to the Adobe Learning Resources team for producing and making this 
content available. Hopefully, FrameMaker developers and users will find this 
documentation useful. Let us know your thoughts/comments.

Have a great weekend!

Thanks,

Kapil Verma
Sr. Product Manager - FrameMaker | FrameMaker Publishing Server
O: +91-120-2444711 x 34505

http://blogs.adobe.com/techcomm/category/framemaker
http://twitter.com/KapilVermaAdobe<http://twitter.com/#!/KapilVermaAdobe>
http://www.adobe.com/products/framemaker/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20121005/56aff288/attachment.html>

Reply via email to