<html 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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">> A first step would be to preserve style information for stories. Using marked content to preserve an XML-like structure
<o:p></o:p></p>
<p class="MsoNormal">><o:p> </o:p></p>
<p class="MsoNormal">That’s called Tagged PDF and been part of PDF since v1.4<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">>and storing CSS styles as page piece dictionaries should achieve similar results as interoperability between word processors.<o:p></o:p></p>
<p class="MsoNormal">><o:p> </o:p></p>
<p class="MsoNormal">Actually, the right way to do this is using attributes on the tags and the ClassMap in the tag tree. CSS is an official type of attribute in PDF 2.0.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You do have to be careful about arbitrary CSS, since you can have scripts inside of CSS…and that impacts security.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Leonard<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Andreas Vox <andreas.vox@gmail.com><br>
<b>Reply-To: </b>Scribus List <scribus-dev@lists.scribus.net><br>
<b>Date: </b>Monday, June 10, 2019 at 11:21 PM<br>
<b>To: </b>Scribus List <scribus-dev@lists.scribus.net><br>
<b>Subject: </b>Re: [scribus-dev] Fwd: Great meeting you in Saarbrücken<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Tamir<o:p></o:p></p>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">... <br>
<br>
For the benefit of everyone else on this list, when Leonard and I spoke <br>
at PDF Days 2018 in Berlin, I proposed the idea of extending the PDF <br>
spec to support the embedding of sufficient metadata that would make it <br>
possible to edit the document in some sort of "standardized" way. We <br>
would then finally have a way to exchange editable documents with others <br>
with robust layout and the other features of PDF - no other format <br>
offers this.<br>
<br>
Obviously, most applications have their own proprietary format and their <br>
own internal models of the document structure. But there are very many <br>
similarities among the various canvas-based document formats and, just <br>
like PDF is a common standard for final form documents now, wouldn't it <br>
be great if there were a common standard for editable documents too?<br>
... <o:p></o:p></p>
</blockquote>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I think it's only possible to achieve two of the following: editable, stable layout and optimal layout. If you modify a document in another application than the one which produced it, there will always be difference in appearance, functionality
or both. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But there's definitely a lot of opportunity to improve editing PDF if you accept adequate layout changes. IMHO, reflow, font substitution, change of color model, change of resolution and scaling are acceptable layout changes. Missing content,
inconsistent line breaking or distortion are obviously not acceptable. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A first step would be to preserve style information for stories. Using marked content to preserve an XML-like structure and storing CSS styles as page piece dictionaries should achieve similar results as interoperability between word processors.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Layout programs like Scribus do not only use margins and columns, but also have master/template pages, layers and text flowing around images. Providing a standard for that will be much more challenging.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>