<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.openoffice.devel.sw">
    <title>gmane.comp.openoffice.devel.sw</title>
    <link>http://blog.gmane.org/gmane.comp.openoffice.devel.sw</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/242"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/241"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/240"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/239"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/238"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/237"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/236"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/235"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/234"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/233"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/232"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/231"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/230"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/229"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/228"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/227"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/226"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/225"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/224"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/223"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/242">
    <title>[sw-dev] Re: Libre Office - split window mentese</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/242</link>
    <description>&lt;pre&gt;sorry, I wanted to post this onto the Hungarian OOo users' mailing
list.

Csongor




------ Original Message ------
From: "Halmai Csongor" &amp;lt;halmai-7MJX9tesuGhVSaleMmNIzgdaaARWRX0o&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
To: dev-PqT6ug8IrFOBIukByRZ1s9i2O/JbrIOy&amp;lt; at &amp;gt;public.gmane.org
Sent: 2011.11.01. 6:15:19
Subject: [sw-dev] Libre Office - split window mentese

&lt;/pre&gt;</description>
    <dc:creator>Halmai Csongor</dc:creator>
    <dc:date>2011-11-01T05:51:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/241">
    <title>[sw-dev] Libre Office - split window mentese</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/241</link>
    <description>&lt;pre&gt;Sziasztok,

van egy nagyobbacska Calc tablazatom, amelyet evek ota hasznalok,
bovitgetek. Korabban OpenOfficeOrg alatt ugy mukodott, hogy ha a
fuggoleges gorditosav feletti fekete vonallal ketteosztottam a
munkalapot, akkor a mentes utyan visszatoltve tovabbra is ezt az
osztott nezetet kaptam.

LibreOffice-ban viszont mentes utan elveszik az osztott nezet, es
oszthatom fel ujra. Mivel megnyitasonkent csak 1-2 sort irok hozza,
viszont surun kell megnyitnom, ezert elegge bosszanto a dolog.

Hogyan lehet beallitani a LO-t, hogy a menteskor az osztottsagi
informaciot is mentse el, majd betoltes utan igy is jelenitse meg?

Kosz:

Csongi bacsi

&lt;/pre&gt;</description>
    <dc:creator>Halmai Csongor</dc:creator>
    <dc:date>2011-11-01T05:15:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/240">
    <title>[sw-dev] new Apache OpenOffice.org mail list to replace this list</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/240</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>KS-1oDqGaOF3Lkdnm+yROfE0A&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-10-29T21:51:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/239">
    <title>[sw-dev] Seeding faults in the Writer GUI</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/239</link>
    <description>&lt;pre&gt;Hi,

I am working on testing the OpenOffice Writer GUI for a class project, and I
need to seed some faults in the source code (I built OO330_m20 successfully
on Ubuntu 10.04 running on VMWare), that could possibly generate some errors
related to the Writer GUI. I've been looking through the wiki pages and the
source files, but I'm having trouble figuring out which modules in the
source code I should be focusing on. Can anyone point me to which
files/folders in the source code I should be looking at?

Thanks,

Wikum
&lt;/pre&gt;</description>
    <dc:creator>Wikum Dinalankara</dc:creator>
    <dc:date>2011-10-28T18:02:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/238">
    <title>[sw-dev] Game manual completed using openoffice</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/238</link>
    <description>&lt;pre&gt;Hi Devs at OpenOffice,

I've recently completed this game manual using OpenOffice. No monies were
exchanged for me doing this work. I did it all for free.

I've worked professionally as a typesetter in the Advertisement and Printing
industries in Ireland and have one single issue that I think would make
Openoffice much better.

Vertical justification within columns. I mean: To vertically justify the
lines within the confines of the column box, so all the lines line-up on the
bottom lines; making it much better visually. The vertical justification
controller being put instead or with a line space, or multiple line spaces
within the column.

Otherwise, things went very well. My compliments to OpenOffice, and thanks.

Game Manual is not attached as its compressed it is still 12MB in size and
my previous post was returned by the daemon on the server. If you can direct
me to where I can send it, I will.  It is available on the Paradox website,
in the Darkest Hour forum, Tech Support area.

Kind Regards, Peter Kenny
&lt;/pre&gt;</description>
    <dc:creator>Peter Kenny</dc:creator>
    <dc:date>2011-07-05T11:24:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/237">
    <title>[sw-dev] Re: full CSS &amp; HTML5 support in "Save As"-&gt;"HTML" ?</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/237</link>
    <description>&lt;pre&gt;
Thanks Michael !

So, I guess I will start looking at my developing this idea soon - in C++ + Java or perhaps in pure Java ?  :

HTML5 + CSS support for OOO (Open Office . Org) Writer :
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Goal :  To develop an XHTML odf -&amp;gt; html optional extra 'File -&amp;gt; Export To HTML5+CSS2"  plugin / possible replacement for OOO Writer ,  which will :

    o Store ALL Style Information in a single CSS HTML 
           '&amp;lt;head&amp;gt; ... &amp;lt;style ...&amp;gt; {CSS ...} &amp;lt;/style&amp;gt; &amp;lt;/head&amp;gt;&amp;lt;body&amp;gt;...&amp;lt;/body&amp;gt;&amp;lt;/html&amp;gt;'  section 
      element and DOES NOT include any '&amp;lt;FONT&amp;gt; | &amp;lt;COLOR&amp;gt; | &amp;lt;CENTER&amp;gt; | &amp;lt;b|i|strong&amp;gt;' or absolutely positioned
      elements in the '&amp;lt;body&amp;gt;', ONLY references to custom CSS style class definitions in that single style 
      section appear in the single '&amp;lt;body&amp;gt;...&amp;lt;/body&amp;gt;' section . 
 
      Thus all aspects of page layout / positioning are to be made controllable by CSS, which can be easily
      over-ridden or extended by users' own custom cascading style sheets , and the '&amp;lt;body&amp;gt;...&amp;lt;/body&amp;gt;' text
      is kept clean and human-readable / editable in a text editor / dedicated HTML editor , preserving text
      layout and whitespace / HTML comments , modern examples of which do properly support WYSIWYG CSS , 
      but not integration with Open Office - maybe because of the huge HTML files full of redundant style 
      information that OOO Writer's existing HTML filters normally produce ?
   
      If an '.odt' OOO Writer template file is exported, its customized styles will be exported to CSS style
      class definitions in the head section and references to such styles in the body section .      

    o Conform to latest new HTML5 + CSS 2.x + XHTML 2.x + XSL + XML  standards  
      and support useful new features of these standards supported in modern firefox browsers .

       o support CSS "media type" extensions for browser, print , teletype : terminal , video, audio, or X-Windows + GTK display -
          e.g.  one can parse CSS + HTML to create GUI controls in an X-Window / Window in a desktop manager environment , 
          perhaps using GTK XML Builder + cairo-script and / or pango layout script ,  to implement styles for the X-Windows media type,  as well as 
          use JavaScript to change style of elements in HTML documents for the browser media type ;  for the print media type,
          every block level element will be absolutely positioned by CSS to fit into a fixed page size, and can include "header" and 
          "footer" content - this could be used when exporting these CSS controlled documents to PDF using external browser ,
          which also rarely turns out nicely for current OOO HTML filter produced dox , which lack proper "&amp;lt;h(1|2|3|4)&amp;gt;" recognition
          as "heading sections" for which the browser should insert PDF links and PDF Contents section entries .  
   
    o above all Preserve any text data or style change made by users and accurately reflect them in output.
     
    o deal with client browser locale changes and the required changes to data sent to users of different locales correctly -
      correct utilization of XML + HTML + CSS + UTF-(8|16|32) unicode encodings new standards' features support
 
    o Can be re-used by future OOO -&amp;gt; DocBook XML + DSSL + XSL filter - these can support CSS too ?

 I'll have a go at this - should be able to complete in few weeks or so .

I'd be most interested in any comments list readers might have on feasibility / advisability of above - I can't see it should be terribly complicated, with
optimal re-use of modern third party open-source libraries + tools such as libxsl + libxml2  + libhtml2 + xsltproc + DocBook + cairo + pango + GTK + Boost as well as Open Office . 

I guess the preferred solution would be to do this in C++ ,  then maybe do a Java wrapper of the C++ ?

All the best,
Jason
&lt;/pre&gt;</description>
    <dc:creator>Jason Vas Dias</dc:creator>
    <dc:date>2011-07-05T01:22:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/236">
    <title>[sw-dev] Re: full CSS &amp; HTML5 support in "Save As"-&gt;"HTML" ?</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/236</link>
    <description>&lt;pre&gt;
that would probably be possible.
but of course using this approach an exported file
won't necessarily look like the input file.
but perhaps it is good enough.


in Writer there are actually 2 HTML filters.
the original HTML filter is in sw/source/filter/html, and uses the
hard-coded formatting tags.

there is also an XHTML filter in filter/source/xslt/odf2xhtml/
this is only an export filter (no import), so in the UI you don't
get it in File-&amp;gt;Save..., you have to use File-&amp;gt;Export...

i'm not familiar with the XHTML export filter;
i just know it's implemented via XSLT, taking an ODF file as input
(so it should be able to access all the styles).
perhaps it does a better job already of exporting styles.
you should try it out...

&lt;/pre&gt;</description>
    <dc:creator>Michael Stahl</dc:creator>
    <dc:date>2011-06-16T11:45:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/235">
    <title>[sw-dev] Re: full CSS &amp; HTML5 support in "Save As"-&gt;"HTML" ?</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/235</link>
    <description>&lt;pre&gt;Hi Michael -

Thanks for responding  - RE:

Well, leaving the existing HTML filters aside, I'd still like to write
a filter that does:
  o for every "style" that is used by a document: write CSS style
definitions to a header '&amp;lt;style../&amp;gt;' element
  o emits HTML elements without ANY style attributes (no &amp;lt;FONT&amp;gt; tags
either) and uses ONLY that CSS
Surely the list of of styles used by the document is not too difficult to list ?
And surely I could re-use the existing HTML filter code that generates
the elements in a new filter package ?
I'd find this really useful and interesting to do .   Any tips on what
to look at to get me started ?

Thanks &amp;amp; Regards,
Jason

On Tue, Jun 14, 2011 at 2:34 PM, Michael Stahl
&amp;lt;Michael.X.Stahl-QHcLZuEGTsvQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:
&lt;/pre&gt;</description>
    <dc:creator>Jason Vas Dias</dc:creator>
    <dc:date>2011-06-14T15:12:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/234">
    <title>[sw-dev] Re: full CSS &amp; HTML5 support in "Save As"-&gt;"HTML" ?</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/234</link>
    <description>&lt;pre&gt;
hi Jason,

Writer's internal representation of styles is quite different from CSS, so this is not easily possible.
Writer's HTML export will produce something that looks similar
to the writer document in a browser, without regard to styles.
perhaps the existing HTML filters could be improved a bit, but probably even with
all the things that can be done easily it won't be good enough for users
who expect human readable HTML/CSS.

i suggest using a tool that is more specialized for the Web.

&lt;/pre&gt;</description>
    <dc:creator>Michael Stahl</dc:creator>
    <dc:date>2011-06-14T13:34:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/233">
    <title>[sw-dev] full CSS &amp; HTML5 support in "Save As"-&gt;"HTML" ?</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/233</link>
    <description>&lt;pre&gt;Hi - this is my first post to this list, sorry if it is the wrong place,
but I gather my initial post to the "Writer Community Forum" &amp;lt; at &amp;gt;
 http://user.services.openoffice.org/en/forum/viewtopic.php?f=7&amp;amp;t=41683&amp;amp;sid=e0623b280a0d6461fc007da81f4ee3f5
was the wrong place - so here is the post :

Hi -

I want to be able to create and maintain HTML files which retain and maintain use of CSS from an original HTML document import .

So if I import a document like :

Code: Select all   Expand view
            &amp;lt;!DOCTYPE HTML&amp;gt;
            &amp;lt;html xmlns="http://www.w3.org/1999/xhtml"&amp;gt;
            &amp;lt;head&amp;gt;
               &amp;lt;title&amp;gt;Test Import HTML Document&amp;lt;/title&amp;gt;
               &amp;lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/&amp;gt;
               &amp;lt;meta http-equiv="Content-Script-Type" content="text/javascript"/&amp;gt;
               &amp;lt;meta name="author" content="JVD"/&amp;gt; 
                &amp;lt;style type="text/css"&amp;gt;
                     &amp;lt; at &amp;gt;page { size:            216mm 279mm;
                       margin:    12mm;
           }
                     body   { margin:       8mm;
            width:        180mm;
            font-family:  "Gill Sans", "Gill Sans MT",  "Garrison Sans", "Bauhaus", "Arial", "Verdana", "Helvetica", sans-serif, sans;
            font-size:    10pt;
            font-style:   normal;       
            font-weight:  normal; text-align: justify; text-decoration: none;
            background:   #FFFFFF;
            color:        #000000;
            text-align:   center;
          }
                    p        {  margin: +4mm;  text-align :  justify;  } 
                &amp;lt;/style&amp;gt;
              &amp;lt;/head&amp;gt;
              &amp;lt;body&amp;gt;
                 &amp;lt;h3&amp;gt;Heading - left indent here should be 20mm and this should be centered &amp;lt;/h3&amp;gt;
                  &amp;lt;p&amp;gt;This paragraph should be justified and its left indent should be 24mm.&amp;lt;/p&amp;gt;
              &amp;lt;/body&amp;gt;
              &amp;lt;/html&amp;gt;



OOO-writer seems to import this OK cosmetically - but if I make any change, for instance
I modify style "Paragraph" so that "Gill Sans" is removed from the font face list , or increase
the "Paragraph" style indent, then OOO-writer comments out my '&amp;lt;style&amp;gt;&amp;lt;!-- --&amp;gt;&amp;lt;/style&amp;gt;'
section and encloses every paragraph text in a '&amp;lt;FONT ...&amp;gt;...&amp;lt;/FONT&amp;gt;' tag , so I loose
my original style sheet settings and render the document horrible to edit in a text editor .

Is an OOO-writer HTML5+ compatible plugin that retains and is able to write CSS style sheets
to reflect OOO "Style" item changes feasible or on the cards ?
If not, I intend to develop one.

Thanks in advance for any responses, &amp;amp; Regards,
Jason
OpenOffice 3.3 linux

JVD
     
    Posts: 2
    Joined: Sat Jun 11, 2011 4:38 pm

Top
Re: full CSS + HTML5 support in "Save As"-&amp;gt;"HTML" ?

Postby TheGurkha » Sat Jun 11, 2011 6:32 pm
The ability of OOo to usefully edit HTML is pretty poor IMHO. I wouldn't recommend it at all. I use a dedicated tool such as KompoZer.
Ubuntu 11.04 Natty, LibO 3.3.2 (330m B:202)
OOo Portable 3.2.0 (320m12 B:9483)
Gurkha Welfare Trust

User avatar
TheGurkha
    Moderator
     
    Posts: 6093
    Joined: Thu Mar 13, 2008 12:13 pm
    Location: North Wales, UK.

Top
Re: Full CSS + HTML5 support in "Save As"-&amp;gt;"HTML" ?

Postby JVD » Sat Jun 11, 2011 7:18 pm

    Re: full CSS + HTML5 support in "Save As"-&amp;gt;"HTML" ?

    Postby TheGurkha » Sat Jun 11, 2011 6:32 pm
    The ability of OOo to usefully edit HTML is pretty poor IMHO. I wouldn't recommend it at all. I use a dedicated tool such as KompoZer.



Thanks for your response ! I will check out KompoZer .

But I prefer writing HTML generators myself with CGI programs / PERL + mod_perl + HTML::Mason for web development .

For non-web development documents , eg. for my CV, I have my own "simplified markup language" (like "intelligent troff") parsed by my own PERL script
that can emit DocBook XML + XSL , or HTML / XHTML + CSS .

It is really, really great the way OOO can load one of the HTML files produced by xsltproc from the DocBook source or my own HTML + CSS , and export
the document to PDF or MS-Word so that cosmetically it looks exactly like the printed document .

But if a document is loaded from an HTML file , and saved in HTML format, then I think OOO should have more respect for the CSS that it evidently is able
to parse successfully , rather than simply commenting it out .

I'd be interested in re-writing the OOO HTML 'Save As' plugin to do this - also as a way of refreshing my Java skills - and also upgrade it to support HTML5 -
unless people think this would be a waste of time / is already being done ?
OpenOffice 3.3 linux

JVD
     
    Posts: 2
    Joined: Sat Jun 11, 2011 4:38 pm

Top
Re: Full CSS + HTML5 support in "Save As"-&amp;gt;"HTML" ?

Postby TheGurkha » Sat Jun 11, 2011 8:28 pm
We're not the developers, just users trying to help other users. The developers don't hang out here.
Ubuntu 11.04 Natty, LibO 3.3.2 (330m B:202)

So do the developers hang out here ?

I'd be most grateful for their ideas on the above .

I have compiled OpenOffice before using gcc / g++ + Sun J2EE / gcj / OpenJDK ,  and would like to
understand how big a job the above might be .  If it is already parsing the CSS, as it seems to be, 
I can't imagine why this would be such a huge job . 

Thanks in advance for any responses, 
Jason ( JVD ) &amp;lt;jason.vas.dias-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>Jason Vas Dias</dc:creator>
    <dc:date>2011-06-11T22:43:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/232">
    <title>[sw-dev] difference between method SwFrm::InsertBefore and SwFrm::InsertBehind</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/232</link>
    <description>&lt;pre&gt;Hi all,

I find that there are 2 similar method in SwFrm to create the layout tree in sw,
they are SwFrm::InsertBefore and SwFrm::InsertBehind.

I wonder the difference between these 2 methods and when to use anyone of them.
And I find there is a while loop in method SwFrm::InsertBefore but there isn't in the other.

Could anybody help me regarding this question ? Thank you very much.

Regards,
2011-05-04 



lijian 
&lt;/pre&gt;</description>
    <dc:creator>lijian</dc:creator>
    <dc:date>2011-05-04T09:22:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/231">
    <title>[sw-dev] Re: issue 86769 - ww8 in vertical writing</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/231</link>
    <description>&lt;pre&gt;
It seems that Henning has confirmed that the fix is OK. I assume that 
you already have verified that it does what it is assumed to do, at 
least for the files you have used for testing.

I will try to see what I can do.

Regards,
Mathias

&lt;/pre&gt;</description>
    <dc:creator>Mathias Bauer</dc:creator>
    <dc:date>2011-04-26T15:56:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/230">
    <title>[sw-dev] issue 86769 - ww8 in vertical writing</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/230</link>
    <description>&lt;pre&gt;Hi,

How could we fix an issue 86769?

Best regards,
Tora
&lt;/pre&gt;</description>
    <dc:creator>tora - Takamichi Akiyama</dc:creator>
    <dc:date>2011-04-25T03:19:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/229">
    <title>Re: track change</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/229</link>
    <description>&lt;pre&gt;
some important things are in this file:
sw/source/core/doc/docredln.cxx

but the redlining/change tracking is actually spread out all over
sw/source/core, and contaminates pretty much everything there.


in that case it is probably unhelpful for me to mention that the writer
redlining implementation so far has stubbornly refused to be understood by
anybody.


&lt;/pre&gt;</description>
    <dc:creator>Michael Stahl</dc:creator>
    <dc:date>2011-01-18T13:36:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/228">
    <title>track change</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/228</link>
    <description>&lt;pre&gt;Hi,

One question: how to find out the source code module that is in charge of providing the track change feature in OOo?
It is a kind of urgent request, I actually do not have enough time to read through all the material or try out a build process.
Thanks in advance!
 Best regards
Zongbo Zhang
Software Developer
[cid:image001.gif-XLQ4Sn09p8g8ofhndwPS7DRmByFHzeGd&amp;lt; at &amp;gt;public.gmane.org]
E-mail: zzh-OyzMm2K3GN7YtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
Tel.:    +45 4436 6800
Direct: +45 4436 6827
Web:   www.bimco.org&amp;lt;http://www.bimco.org&amp;gt;

________________________________
[cid:image002.gif-XLQ4Sn09p8g8ofhndwPS7DRmByFHzeGd&amp;lt; at &amp;gt;public.gmane.org]

NOTE: Please be advised that the information contained in this communication may be confidential/intended only for the use of the recipient(s) indicated above, and may be legally privileged. If the reader of this message is not an intended/indicated recipient, please be hereby notified that the dissemination, distribution, or copying of this communication or any of its contents is prohibited. In the event you feel you have received this communication in error, you are hereby requested to so indicate by re-sending this communication to the sender and deleting the original message and any copy of it from your computer system.

Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.

Apology for any inconvenience and/or intrusion is hereby extended to any unintended recipients.


&lt;/pre&gt;</description>
    <dc:creator>Zongbo Zhang</dc:creator>
    <dc:date>2011-01-18T11:52:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/227">
    <title>Re: Re: [sw-issues] [Issue 115174] Crash when opening odt document having a lot of graphics and Redlines</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/227</link>
    <description>&lt;pre&gt;Hi Mike,

you must do that by yourself. All postings in the mailing lists have a 
footer with a link for unsubscribing. If you click on it, a mail is 
created that you must send. But make sure that your "from" mail address 
in this mail is the one that you have used when you subscribed.

Regards,
Mathias

On 23.12.2010 00:22, Mike Kierna wrote:


&lt;/pre&gt;</description>
    <dc:creator>Mathias Bauer</dc:creator>
    <dc:date>2011-01-04T18:26:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/226">
    <title>Re: [sw-issues] [Issue 115174] Crash when opening odt document having a lot of graphics and Redlines</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/226</link>
    <description>&lt;pre&gt;Please, REMOVE ME FROM THE E-MAIL LISTING'S !!!!!!!!!! Your system has literally 
locked up my e-mail system in both Yahoo and Google to the point that both 
system's mailbox's are in permanent 'load' cycle. And who ever came up with this 
system needs to be locked in an elevator and left to listen to the music for a 
week. 





________________________________
From: "mst-JNqQRFIbOJOM4zKIHC2jIg&amp;lt; at &amp;gt;public.gmane.org" &amp;lt;mst-JNqQRFIbOJOM4zKIHC2jIg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
To: issues-PqT6ug8IrFOBIukByRZ1s9i2O/JbrIOy&amp;lt; at &amp;gt;public.gmane.org
Sent: Wed, December 22, 2010 1:14:31 PM
Subject: [sw-issues] [Issue 115174] Crash when opening odt document having a lot 
of graphics and Redlines

To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=115174


User mst changed the following:

                What    |Old value                |New value
================================================================================
                      CC|'od'                      |'mib,od'
--------------------------------------------------------------------------------
                  Status|NEW                      |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from mst-JNqQRFIbOJOM4zKIHC2jIg&amp;lt; at &amp;gt;public.gmane.org Wed Dec 22 18:14:28 +0000 
2010 -------
the following fragment causes the crash:

&amp;lt;text:p text:style-name="newP183"&amp;gt;
  &amp;lt;text:span text:style-name="newAttribute"&amp;gt;full&amp;lt;/text:span&amp;gt;
  specifies a full circle or ellipse, like
  &amp;lt;draw:circle draw:style-name="newgr1" draw:text-style-name="P2227"
draw:z-index="0" svg:height="0.5cm" svg:width="0.5cm" 
text:anchor-type="as-char"&amp;gt;
    &amp;lt;text:p&amp;gt;
      &amp;lt;text:change-start text:change-id="ct5853"/&amp;gt;
      &amp;lt;text:change-end text:change-id="ct5853"/&amp;gt;
    &amp;lt;/text:p&amp;gt;
  &amp;lt;/draw:circle&amp;gt;
  .
&amp;lt;/text:p&amp;gt;


OOo crashes on reading the text:change-end element.

(gdb) bt
#1  0xb155def6 in SwXTextRange::GetDoc (this=0x0)
    at sw/source/core/unocore/unoobj2.cxx:893
#2  0xb181436c in lcl_GetDocViaTunnel (rRange=...)
    at sw/source/filter/xml/XMLRedlineImportHelper.cxx:87
#3  0xb181442c in XTextRangeOrNodeIndexPosition::GetDoc (this=0xb00ac7b0)
    at sw/source/filter/xml/XMLRedlineImportHelper.cxx:197
#4  0xb1814689 in XMLRedlineImportHelper::InsertIntoDocument (this=0xb051ea50,
    pRedlineInfo=0xb00ac794)
    at sw/source/filter/xml/XMLRedlineImportHelper.cxx:612

the problem is that lcl_GetDocViaTunnel expects the
XTextRange to be a SwXTextRange, but it is not:

(gdb) p *xTunnel._pInterface
$2 = (SvxUnoTextRange) {

this is apparently because the text:p is inside a draw:circle.
according to cl OOo currently does not support change tracking
inside drawing objects anyway, so the easiest fix is to just
not import the tracked change if the XTextRange does not belong
to writer.


fixed in cws sw34bf03
http://hg.services.openoffice.org/hg/cws/sw34bf03/rev/bc5dd26cbd6f

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe&amp;lt; at &amp;gt;sw.openoffice.org
For additional commands, e-mail: issues-help-PqT6ug8IrFMqu4YQ5wCXyw&amp;lt; at &amp;gt;public.gmane.org.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscribe-JNqQRFIbOJOM4zKIHC2jIg&amp;lt; at &amp;gt;public.gmane.org
For additional commands, e-mail: allbugs-help-JNqQRFIbOJOM4zKIHC2jIg&amp;lt; at &amp;gt;public.gmane.org


      &lt;/pre&gt;</description>
    <dc:creator>Mike Kierna</dc:creator>
    <dc:date>2010-12-22T23:22:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/225">
    <title>Looking for information</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/225</link>
    <description>&lt;pre&gt;Hi All,

I am currently working on some projects for the Documentation Project. 
I am looking for information on two different items.  The first is on 
XForms.  The second is on the standard styles that are installed with OOo.

I would greatly appreciate any links that I can get on either or both.

TIA.

Andy
&lt;/pre&gt;</description>
    <dc:creator>Andy Brown</dc:creator>
    <dc:date>2010-08-28T23:36:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/224">
    <title>RE:  Re: Improving the importing of placeholder fields</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/224</link>
    <description>&lt;pre&gt;Sorry, clicked send to fast. The other thing is:

- How to be noticed when a field is no longer selected. So that if was hidden because of being clicked, if the user chooses not to overwrite it and go to another place, the field appears again.

Thanks.

-----Mensaje original-----
De: Ramón García Fernández
Enviado el: viernes, 20 de agosto de 2010 16:36
Para: 'dev&amp;lt; at &amp;gt;sw.openoffice.org'
Asunto: Re: Improving the importing of placeholder fields

I am implementing the text placeholders. I managed to make them invisible, I added a flag to SwJumpEditField and SwFldPortion. Now

I need to know how to:
- Refresh: tell Writer to reformat the current paragraph. I am looking for invalidation functions. It looks like there is a way to invalidate fields of a given type (SwFieldType::Modify), but I can't find such function for fields. In fact, it looks like when a field is changed in the UI, the current field is removed and a new field is inserted.

If a field is changed programatically (for instance, SwJumpEditField::PutValue), no invalidation function is run. Or this is what it seems to be.



Aviso legal – Comisión Nacional del Mercado de Valores

Este mensaje y, en su caso, los ficheros que lleve incorporados, está dirigido exclusivamente a su destinatario y es de carácter confidencial. Si fuere recibido por error o se tuviere conocimiento del mismo sin ser su destinatario, rogamos nos lo comunique por la misma vía o telefónicamente (91 585 15 00) y proceda a su destrucción, debiendo abstenerse de utilizar, transmitir, divulgar o  reproducir la información contenida en el mismo. La CNMV se reserva las acciones legales que procedan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente de la entidad

Para información y consultas visite nuestra web: http://www.cnmv.es


Disclaimer - Comisión Nacional del Mercado de Valores

This message, its content and any file attached thereto is for the intended recipient only and is confidential. If you have received this e-mail in error or had access to it, you should note that the information in it is private and any use thereof is unauthorised. In such an event please notify us by e-mail or by telephone (+ 34 91 585 15 00). Any reproduction of this e-mail by whatsoever means and any transmission or dissemination thereof to other persons is prohibited. The Comisión Nacional del Mercado de Valores reserves the right to take legal action against any persons unlawfully gaining access to the content of any external message it has emitted

For additional information, please visit our website: http://www.cnmv.es
&lt;/pre&gt;</description>
    <dc:creator>Ramón García Fernández</dc:creator>
    <dc:date>2010-08-20T14:37:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/223">
    <title>Re: Improving the importing of placeholder fields</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/223</link>
    <description>&lt;pre&gt;I am implementing the text placeholders. I managed to make them invisible, I added a flag to SwJumpEditField and SwFldPortion. Now

I need to know how to:
- Refresh: tell Writer to reformat the current paragraph. I am looking for invalidation functions. It looks like there is a way to invalidate fields of a given type (SwFieldType::Modify), but I can't find such function for fields. In fact, it looks like when a field is changed in the UI, the current field is removed and a new field is inserted.

If a field is changed programatically (for instance, SwJumpEditField::PutValue), no invalidation function is run. Or this is what it seems to be.



-----Mensaje original-----
De: Ramón García Fernández [mailto:ramong&amp;lt; at &amp;gt;cnmv.es]
Enviado el: miércoles, 04 de agosto de 2010 16:01
Para: dev&amp;lt; at &amp;gt;sw.openoffice.org
Asunto: RE: [sw-discussion] Re: Improving the importing of placeholder fields

Our purpose is:
- Make the text placeholder user interface mor friendly, like in Impress templates.

When the user clicks the placeholder, the content should temporary disappear, in order to suggest the user to fill the text. Then, either the user types text, and the placeholder is removed from the document, or the user presses escape or moves the cursor, and the placeholder appears again.


- Import Word documents with text placeholders.

This is where you disagree.
Note that the recommended way of creating text placeholders in Word (2003) documents is to create a field with an undefined macro. This fields work in practice like ODF text placeholders. It would be incorrect to convert all macro fields to text placeholders. But there should be an option to convert those that call an specific macro, such as the non existent DoFieldClick. I talk from my experience. More input from users is needed.

Aviso legal – Comisión Nacional del Mercado de Valores

Este mensaje y, en su caso, los ficheros que lleve incorporados, está dirigido exclusivamente a su destinatario y es de carácter confidencial. Si fuere recibido por error o se tuviere conocimiento del mismo sin ser su destinatario, rogamos nos lo comunique por la misma vía o telefónicamente (91 585 15 00) y proceda a su destrucción, debiendo abstenerse de utilizar, transmitir, divulgar o  reproducir la información contenida en el mismo. La CNMV se reserva las acciones legales que procedan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente de la entidad

Para información y consultas visite nuestra web: http://www.cnmv.es


Disclaimer - Comisión Nacional del Mercado de Valores

This message, its content and any file attached thereto is for the intended recipient only and is confidential. If you have received this e-mail in error or had access to it, you should note that the information in it is private and any use thereof is unauthorised. In such an event please notify us by e-mail or by telephone (+ 34 91 585 15 00). Any reproduction of this e-mail by whatsoever means and any transmission or dissemination thereof to other persons is prohibited. The Comisión Nacional del Mercado de Valores reserves the right to take legal action against any persons unlawfully gaining access to the content of any external message it has emitted

For additional information, please visit our website: http://www.cnmv.es
&lt;/pre&gt;</description>
    <dc:creator>Ramón García Fernández</dc:creator>
    <dc:date>2010-08-20T14:35:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/222">
    <title>RE: Re: Improving the importing of placeholder fields</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.sw/222</link>
    <description>&lt;pre&gt;Our purpose is:
- Make the text placeholder user interface mor friendly, like in Impress templates.

When the user clicks the placeholder, the content should temporary disappear, in order to suggest the user to fill the text. Then, either the user types text, and the placeholder is removed from the document, or the user presses escape or moves the cursor, and the placeholder appears again.


- Import Word documents with text placeholders.

This is where you disagree.
Note that the recommended way of creating text placeholders in Word (2003) documents is to create a field with an undefined macro. This fields work in practice like ODF text placeholders. It would be incorrect to convert all macro fields to text placeholders. But there should be an option to convert those that call an specific macro, such as the non existent DoFieldClick. I talk from my experience. More input from users is needed.

-----Mensaje original-----
De: Michael Stahl [mailto:Michael.X.Stahl&amp;lt; at &amp;gt;Oracle.COM]
Enviado el: martes, 03 de agosto de 2010 11:12
Para: dev&amp;lt; at &amp;gt;sw.openoffice.org
Asunto: [sw-discussion] Re: Improving the importing of placeholder fields

On 09/07/2010 15:50, Ramón García Fernández wrote:

after i finally think i understand what you want, it doesn't seem so useful to me (see below)...

Aviso legal – Comisión Nacional del Mercado de Valores

Este mensaje y, en su caso, los ficheros que lleve incorporados, está dirigido exclusivamente a su destinatario y es de carácter confidencial. Si fuere recibido por error o se tuviere conocimiento del mismo sin ser su destinatario, rogamos nos lo comunique por la misma vía o telefónicamente (91 585 15 00) y proceda a su destrucción, debiendo abstenerse de utilizar, transmitir, divulgar o  reproducir la información contenida en el mismo. La CNMV se reserva las acciones legales que procedan contra todo tercero que acceda de forma ilegítima al contenido de cualquier mensaje externo procedente de la entidad

Para información y consultas visite nuestra web: http://www.cnmv.es


Disclaimer - Comisión Nacional del Mercado de Valores

This message, its content and any file attached thereto is for the intended recipient only and is confidential. If you have received this e-mail in error or had access to it, you should note that the information in it is private and any use thereof is unauthorised. In such an event please notify us by e-mail or by telephone (+ 34 91 585 15 00). Any reproduction of this e-mail by whatsoever means and any transmission or dissemination thereof to other persons is prohibited. The Comisión Nacional del Mercado de Valores reserves the right to take legal action against any persons unlawfully gaining access to the content of any external message it has emitted

For additional information, please visit our website: http://www.cnmv.es
&lt;/pre&gt;</description>
    <dc:creator>Ramón García Fernández</dc:creator>
    <dc:date>2010-08-04T14:01:04</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.openoffice.devel.sw">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.openoffice.devel.sw</link>
  </textinput>
</rdf:RDF>

