<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Translating a PDF form using SE63 in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/translating-a-pdf-form-using-se63/qaa-p/9204068#M3266558</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After quite a lot of research it appears this is a bug due to the XSLT within SAP not beeing compatible with the XML sent back from Adobe Livecycle ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These SAP note will be helpful : &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;1458510, &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;1496928.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; mso-bidi-font-family: &amp;amp;quot; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; sans-serif&amp;amp;quot: ; ,&amp;amp;quot: ; font-size: 11pt; Times New Roman&amp;amp;quot: ; mso-ansi-language: EN-US; font-family: &amp;amp;quot; mso-fareast-theme-font: minor-latin; mso-fareast-font-family: Calibri; Calibri&amp;amp;quot: ;"&gt;Have a nice day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; mso-bidi-font-family: &amp;amp;quot; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; sans-serif&amp;amp;quot: ; ,&amp;amp;quot: ; font-size: 11pt; Times New Roman&amp;amp;quot: ; mso-ansi-language: EN-US; font-family: &amp;amp;quot; mso-fareast-theme-font: minor-latin; mso-fareast-font-family: Calibri; Calibri&amp;amp;quot: ;"&gt;Gilles Doyen&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Apr 2013 15:35:29 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-04-03T15:35:29Z</dc:date>
    <item>
      <title>Translating a PDF form using SE63</title>
      <link>https://community.sap.com/t5/technology-q-a/translating-a-pdf-form-using-se63/qaq-p/9204067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm having troubles translating a PDF form using SE63, here is the problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a standard Adobe Form (t.code SFP) called SEPA_MANDATE whi I had to make a copy of (to adjust it with the company's requirements).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've done all the changes in the Z copy of the form and it's working fine, the only thing is when I try to use the translation tool the XML it returns me is wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I do the same on the standard form (SEPA_MANDATE), i get this :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/178645" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when I try the same with my Z-copy I get this:&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/178649" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apparently, when I do a copy of the standard and don't modify it, running SE63 on the copy I still have the XML but as soon as I do any modification the SE63 doesn't show any XML anymore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried searching for a SAP Note talking about this (because I think it might be a bug in SAP), tried to play with different versions of LiveCycle designer (I use 10.0 and a colleague 8.2) but nothing has worked so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone know of another way of translating adobe forms? I cannot bind the texts inside the form to the interface as I'm using a standard interface (SEPA_MANDATE_IF) so I think my only solution is to use the standard translation mechanisms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks in advance,&lt;/P&gt;&lt;P&gt;Gilles Doyen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jan 2013 15:57:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/translating-a-pdf-form-using-se63/qaq-p/9204067</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-01-25T15:57:06Z</dc:date>
    </item>
    <item>
      <title>Re: Translating a PDF form using SE63</title>
      <link>https://community.sap.com/t5/technology-q-a/translating-a-pdf-form-using-se63/qaa-p/9204068#M3266558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After quite a lot of research it appears this is a bug due to the XSLT within SAP not beeing compatible with the XML sent back from Adobe Livecycle ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These SAP note will be helpful : &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;1458510, &lt;SPAN style="font-family: &amp;amp;quot;Calibri&amp;amp;quot;,&amp;amp;quot;sans-serif&amp;amp;quot;; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: &amp;amp;quot;Times New Roman&amp;amp;quot;; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;1496928.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; mso-bidi-font-family: &amp;amp;quot; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; sans-serif&amp;amp;quot: ; ,&amp;amp;quot: ; font-size: 11pt; Times New Roman&amp;amp;quot: ; mso-ansi-language: EN-US; font-family: &amp;amp;quot; mso-fareast-theme-font: minor-latin; mso-fareast-font-family: Calibri; Calibri&amp;amp;quot: ;"&gt;Have a nice day,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style=": ; mso-bidi-font-family: &amp;amp;quot; mso-fareast-language: EN-US; mso-bidi-language: AR-SA; sans-serif&amp;amp;quot: ; ,&amp;amp;quot: ; font-size: 11pt; Times New Roman&amp;amp;quot: ; mso-ansi-language: EN-US; font-family: &amp;amp;quot; mso-fareast-theme-font: minor-latin; mso-fareast-font-family: Calibri; Calibri&amp;amp;quot: ;"&gt;Gilles Doyen&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Apr 2013 15:35:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/translating-a-pdf-form-using-se63/qaa-p/9204068#M3266558</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-04-03T15:35:29Z</dc:date>
    </item>
  </channel>
</rss>

