<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello Tino H. Haida,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We would like to understand bit more on the trouble you are facing while translating the content from RTL to LTR. Therefore, can you please elaborate by giving
some examples.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for reporting the issue. For time being as a workaround, you have to set the document direction manually, after creating the document from RTL template.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Harsh Gupta<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">FrameMaker Engineering<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com]
<b>On Behalf Of </b>Heiko Haida<br>
<b>Sent:</b> Tuesday, June 16, 2015 12:39 AM<br>
<b>To:</b> Framers<br>
<b>Subject:</b> RE: Adobe announces FrameMaker (2015 Release) -- first steps with Arabic (RTL)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Dear Maxwell,<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">thank you for this announcement and for the many new features of FM 2015, of course.<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">I bought a subscription license and just made the very first steps to use FM 2015 in our XML-based workflow for Arabic documents. The conversion to Arabic looks very well. Only changing the
direction from RTL to LTR (with the setting of bidi-markers) is different to Indesign and not so intuitive and handy.<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">One point where there might be a small bug:
<br>
Although the structured template is set to "Document > Direction > RTL", my new FM files based on this template still are set to "LTR"... It seems that this new property is not correctly transfered during the structured workflow (unless I am missing sth ...).<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Best regards -- Tino H. Haida, Berlin<o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif""> <o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif""> <o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Verdana","sans-serif"">Maxwell Hoffmann:<o:p></o:p></span></p>
<blockquote style="border:none;border-left:solid #1010FF 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Robert,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>You can view the following featurette video to get a preview of how Conditional Table Columns work:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><a href="http://tv.adobe.com/watch/framemaker-2015/fm-cond-tbl-cols/">http://tv.adobe.com/watch/framemaker-2015/fm-cond-tbl-cols/</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I'll post separately on the REGISTRATION pages for LAUNCH WEBINARS for FrameMaker 2015 on June 16 and RoboHelp 2015 on June 18<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>UNSUBSCRIBE FROM MAIL LIST<o:p></o:p></pre>
<pre>Maxwell Hoffmann | Product Evangelist | Adobe | p. 503.336.5952 | c. 503.805.3719 | <a href="mailto:mhoffman@adobe.com">mhoffman@adobe.com</a> <o:p></o:p></pre>
<pre><a href="http://twitter.com/maxwellhoffmann">http://twitter.com/maxwellhoffmann</a> - <a href="http://www.linkedin.com/in/maxwellhoffmann ">http://www.linkedin.com/in/maxwellhoffmann </a> blogs.adobe.com/techcomm<o:p></o:p></pre>
<pre>Upcoming webinars <a href="http://adobe.ly/Pbz6xI ">http://adobe.ly/Pbz6xI </a> Recorded webinars: <a href="http://adobe.ly/Pbdp0J">http://adobe.ly/Pbdp0J</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: <a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a> [mailto:<a href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a>] On Behalf Of Robert Lauriston<o:p></o:p></pre>
<pre>Sent: Tuesday, June 02, 2015 11:17 AM<o:p></o:p></pre>
<pre>To: Keith Soltys; Framers Mailing List (<a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>)<o:p></o:p></pre>
<pre>Subject: Re: Adobe announces FrameMaker (2015 Release)<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Looking at the version comparison, the additions for unstructured FrameMaker in English are:<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>- conditional table columns<o:p></o:p></pre>
<pre>- book-level conditional text<o:p></o:p></pre>
<pre>- web help custom "skins"<o:p></o:p></pre>
<pre>- auto-insert table continuation variables<o:p></o:p></pre>
<pre>- mini-TOCs<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Still no wiki integration.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I'll be curious to see how well the conditional table columns work.<o:p></o:p></pre>
<pre>That seems like a major challenge.<o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>You are currently subscribed to framers as <a href="mailto:mhoffman@adobe.com">mhoffman@adobe.com</a>.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Send list messages to <a href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>To unsubscribe send a blank email to<o:p></o:p></pre>
<pre><a href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a><o:p></o:p></pre>
<pre>or visit <a href="http://lists.frameusers.com/mailman/options/framers/mhoffman%40adobe.com">http://lists.frameusers.com/mailman/options/framers/mhoffman%40adobe.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Send administrative questions to <a href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>. Visit <a href="http://www.frameusers.com/">http://www.frameusers.com/</a> for more resources and info.<o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
</blockquote>
</div>
</body>
</html>