<?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://permalink.gmane.org/gmane.editors.abiword.devel">
    <title>gmane.editors.abiword.devel</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel</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.editors.abiword.devel/23986"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23985"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23984"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23983"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23982"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23981"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23980"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23979"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23978"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23977"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23976"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23975"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23974"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23973"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23972"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23971"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23970"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23969"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23968"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.editors.abiword.devel/23967"/>
      </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.editors.abiword.devel/23986">
    <title>Re: paragraph style</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23986</link>
    <description>&lt;pre&gt;
Hi Simon,

I agree with your proposal. It preserves the users intentions and
helps clear out messes. BTW I am the MES in the discussion :-)

Cheers

Martin


On Mon, May 21, 2012 at 2:33 AM, Simon Larochelle
&amp;lt;larochelle.simon.1&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:

&lt;/pre&gt;</description>
    <dc:creator>Martin Sevior</dc:creator>
    <dc:date>2012-05-20T23:47:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23985">
    <title>paragraph style</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23985</link>
    <description>&lt;pre&gt;
I am trying to correct a bug when the user changes paragraph style.
Presently, all font properties and character styles are removed from
the paragraph until the first footnote (or endnote), while after the
footnote, none of these things are cleared. There are a few issues:

1) the behavior needs to be same before and after the footnote
2) clearing character styles affects the font properties of footnote
references (i.e. they are no longer in superscript)
3) clearing font properties is a mix bag. If the user has a word in
italic or in bold, he likely does not want it to be affected by the
paragraph style change. However, abiword tends to explicitly set a
large number of properties that are defined in the paragraph style
(for example if the user sets the font to bold, type a word, and then
unsets it, a font property font-weight:normal will be added to every
text fragment afterward). These extraneous properties will likely
cause undesirable effects during the paragraph style change (that is,
keep a number of t&lt;/pre&gt;</description>
    <dc:creator>Simon Larochelle</dc:creator>
    <dc:date>2012-05-20T16:33:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23984">
    <title>L10n update</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23984</link>
    <description>&lt;pre&gt;
Dear AbiWo4rd localizers

All of the PO files for 2.9 have had their headers adjusted and
re-committed to SVN.

Please make sure you download a fresh copy of the PO files (rather
than using a local copy) if you are going to work on L10n.  I would
like to preserve the header adjustments that have been made and not
overwrite them with the old headers, if possible.

Ideally, please work on the L10n online via the Pootle user interface.

http://translate.sugarlabs.org/projects/AbiWord/

Everything there is now synchronized with SVN (except German I think
because Ingo has been committing directly).

I will be working on getting the two way connection between SVN and
Poolte established.

SVN &amp;gt; Poolte (updated POT files)
Poolte &amp;gt; SVN (individual PO files)

I will update you as progress is made.

cjl

&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-20T03:11:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23983">
    <title>Re: Mechanism for proposing Abisource web-site changes/corrections</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23983</link>
    <description>&lt;pre&gt;

Sometimes ago a discussion about making the site multilingual was 
started. Any news?

cheers
Besnik


Më 05/19/2012 10:02 AM, Chris Leonard shkrojti:



&lt;/pre&gt;</description>
    <dc:creator>Besnik Bleta</dc:creator>
    <dc:date>2012-05-19T13:36:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23982">
    <title>Mechanism for proposing Abisource web-site changes/corrections</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23982</link>
    <description>&lt;pre&gt;
Dear AbiWord devs,

I don't see the HTML for the Abisource website

http://www.abisource.com/

as a folder in the SVN

 http://svn.abisource.com/

There are some errors I would like to fix ((for example) updating

Development
(2.7.x)

to

Development
(2.9.x)

at top of table on this page:
http://www.abisource.com/contribute/translate/exist/

If the HTML were checked into SVN, it would be relatively
straightforward to submit patches that could be reviewed easily for
acceptance and publication on the website by whoever is currently
acting as webmaster&amp;lt; at &amp;gt;abisource.com.

cjl

&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-19T07:02:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23981">
    <title>Re: Python binding documentation is missing</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23981</link>
    <description>&lt;pre&gt;
On Thu, May 17, 2012 at 5:52 PM, J.M. Maurer &amp;lt;uwog&amp;lt; at &amp;gt;uwog.net&amp;gt; wrote:

Is there a way to call it from the Python binding? Guessing: "no"

I think I have to patch the library to do this, and I'm in the same
case that in the last email. I would be very happy if I don't have to
do that :)

&lt;/pre&gt;</description>
    <dc:creator>Manuel Kaufmann</dc:creator>
    <dc:date>2012-05-17T21:55:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23980">
    <title>Re: Python binding documentation is missing</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23980</link>
    <description>&lt;pre&gt;
On Thu, May 17, 2012 at 5:45 PM, J.M. Maurer &amp;lt;uwog&amp;lt; at &amp;gt;uwog.net&amp;gt; wrote:

Well, it seems that I'm not as good as you at reading C++ source code :)


I think is not a good idea having a patched version of a library on
our releases. Things like this will be happening all the time.

I'm not sure what decision will we take about this. But I'm really
sure that we don't want that dialog at exporting HTML files... :(

&lt;/pre&gt;</description>
    <dc:creator>Manuel Kaufmann</dc:creator>
    <dc:date>2012-05-17T21:53:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23979">
    <title>Re: Python binding documentation is missing</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23979</link>
    <description>&lt;pre&gt;


The good thing is that during last year's GSoC, the HTML exporter gained
a nice function called IE_Exp_HTML.suppressDialog():

  http://svn.abisource.com/abiword/trunk/src/wp/impexp/xp/ie_exp_HTML.h

So it should be fairly trivial to call that in the widget when a user is
exporting to HTML.

Cheers,
   Marc


&lt;/pre&gt;</description>
    <dc:creator>J.M. Maurer</dc:creator>
    <dc:date>2012-05-17T20:52:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23978">
    <title>Re: Python binding documentation is missing</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23978</link>
    <description>&lt;pre&gt;
On Thu, 2012-05-17 at 12:45 -0300, Manuel Kaufmann wrote:

When I wrote Write, I never really had documentation myself. I always
just looked at the canvas widget header file, which usually was "good
enough":

  http://svn.abisource.com/abiword/trunk/src/wp/ap/gtk/abiwidget.h


You won't be able to solve that problem without extending the widget
API. They way I solved this when the first XO's shipped, was by
distributing some patches in the RPM that simply disabled the HTML
exporter dialog altogether :P

I think I also added those patches to the official Fedora abiword
package, which at the time contained a flag to do a "suger build".
Someone ripped that out a while ago, without ever really solving the
original issue you are now running into as well :'(

Cheers,
  Marc





&lt;/pre&gt;</description>
    <dc:creator>J.M. Maurer</dc:creator>
    <dc:date>2012-05-17T20:45:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23977">
    <title>Python binding documentation is missing</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23977</link>
    <description>&lt;pre&gt;
Hello guys,

I'm working on Write Activity from Sugar (OLPC Project) that uses
Python's Abiword bindings and I'm trying to find a useful
documentation about this.

I was taking a look at the wiki but I didn't find the explanation
about the functions. I found these pages but they are not useful to
me:
 * http://www.abisource.com/wiki/PyAbiWord
 * http://www.abisource.com/wiki/AbiWidget_Header
 * http://svn.abisource.com/pyabiword/trunk/examples

"pradeeban" was helping me a lot on the IRC #abiword channel, and he
told me about this mailing list. So, I'm going to explain what's my
specific problem.

I'm trying to export to HTML the abiword document using
abiword.Canvas.save() method passing this options:

abi.save('file://' + fileObject.file_path, format['mime_type'], exp_props)

abi: abiword.Canvas
fileObject.file_path: "/home/olpc/help.html"
format['mime_type']: "text/html"
exp_props: "'html4:yes; declare-xml:no; embed-css:yes; embed-images:yes;"

The problem that I have[1] is I don't want to show the pop-u&lt;/pre&gt;</description>
    <dc:creator>Manuel Kaufmann</dc:creator>
    <dc:date>2012-05-17T15:45:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23976">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23976</link>
    <description>&lt;pre&gt;
On Thu, May 17, 2012 at 10:38 AM, Hubert Figuière &amp;lt;hfiguiere&amp;lt; at &amp;gt;teaser.fr&amp;gt; wrote:

Yes, that occurred to me after I sent the message.

cjl

&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-17T14:51:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23975">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23975</link>
    <description>&lt;pre&gt;
On 16/05/12 09:33 PM, Chris Leonard wrote:

The question is "is it available on non glibc platforms like Windows?"

Hub

&lt;/pre&gt;</description>
    <dc:creator>Hubert Figuière</dc:creator>
    <dc:date>2012-05-17T14:38:49</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23974">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23974</link>
    <description>&lt;pre&gt;
Chris Leonard wrote on Thu, 17 May 2012 00:33:01 -0400:


I can't really answer why specific things in AbiWord are the way they are,
because I'm only contributing for a few years now (and most of the time only
for a plugin). There might be some stuff that is just inherited waste.

The system.profiles are meant to allow the system administrator to override
built-in values. These probably don't necessarily have to be the locale
values.

For the templates, things are easier. Although my locale is de_DE, I might
want to write a document with paper type letter, so there must be a way to
get these values without regard to my locale.

But we probably could pick up Simon's idea for the "lang" property and extend
it for the other properties as well, i.e. if there isn't already a necessary
property set, use the locale's one (provided that we can get all these for
all our ports).

The template files should change then from normal.awt-ll_CC to something like
normal.A4.awt, normal.Letter.awt, normal.portrait.awt, normal&lt;/pre&gt;</description>
    <dc:creator>Ingo Brückl</dc:creator>
    <dc:date>2012-05-17T11:01:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23973">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23973</link>
    <description>&lt;pre&gt;
On Wed, May 16, 2012 at 10:16 AM, Ingo Brückl &amp;lt;ib&amp;lt; at &amp;gt;wupperonline.de&amp;gt; wrote:


Please forgive me if this sounds like an ignorant question, but is
there some reason we maintain this information ourselves instead of
relying on the glibc locale file which contains:

LC_Paper and LC_Measurement

LC_Paper gives height and width in mm

LC_MEASUREMENT:
1 = cm
2 = inches


**** fr_CA locale ****

LC_PAPER
copy "en_CA"
END LC_PAPER

LC_MEASUREMENT
copy "en_CA"
END LC_MEASUREMENT

**** en_CA locale ****

LC_PAPER
height 279
width  216
END LC_PAPER

LC_MEASUREMENT
measurement 1
END LC_MEASUREMENT

**** fr_FR locale ****

LC_PAPER
height 297
width  210
END LC_PAPER

LC_MEASUREMENT
measurement 1
END LC_MEASUREMENT

**** en-US locale ****

LC_PAPER
height 279
width  216
END LC_PAPER

LC_MEASUREMENT
measurement 2
END LC_MEASUREMENT

&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-17T04:33:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23972">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23972</link>
    <description>&lt;pre&gt;
Simon Larochelle wrote on Wed, 16 May 2012 13:44:43 -0400:



Sounds good. I vote for that.

Ingo

&lt;/pre&gt;</description>
    <dc:creator>Ingo Brückl</dc:creator>
    <dc:date>2012-05-16T18:12:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23971">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23971</link>
    <description>&lt;pre&gt;
Ingo's plan sounds good. Concerning the "lang" property, it determines
which dictionary is loaded by default. For languages which do not have
a specific normal.awt file, the en-US dictionary is loaded by default.
Maybe we could remove the property from the default files and set
"lang" to the system locale when opening a new document (checking
before if the user has defined the variable). After all, presently we
are using the system locale to determine which normal.awt file to load
in order to set the correct lang.

We could then reduce the normal.awt files to countries where some of
the variables "papersize", "units" and "dom-dir" are different from
the default.

Simon

&lt;/pre&gt;</description>
    <dc:creator>Simon Larochelle</dc:creator>
    <dc:date>2012-05-16T17:44:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23970">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23970</link>
    <description>&lt;pre&gt;
On Wed, May 16, 2012 at 10:16 AM, Ingo Brückl &amp;lt;ib&amp;lt; at &amp;gt;wupperonline.de&amp;gt; wrote:

Ok, I'm getting a better picture of how country-specific locale info
is represented in AbiWord.  I suspected it had to be a little
different because it doesn't directly use gettext, with preprocessing
to .strings files first. but I wasn't up-to-speed on the details.



I'm happy to collaborate on achieving the best i18n/L10n results for
AbiWord.  I'm still learning about the specific quirks of AbiWord in
that regard, but I'm a fairly quick study and more than willing to
take on mundane clean-up tasks for the larger goals of better native
language user experiences and greater administrative efficiency in
providing it.

Regards,

cjl

&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-16T16:00:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23969">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23969</link>
    <description>&lt;pre&gt;
Chris Leonard wrote on Tue, 15 May 2012 16:52:03 -0400:




These have a slightly different meaning, because they are more related to
the user's locale which does not only include the language, but additional
information. For example, in fr_CA the pagetype is letter and in fr_CH it
is A4. (Same goes for units, cm vs. inch.)

But we should reduce them and use generic ones, like cm (ISO standard) in
system.profiles and inch in system.profile-en-US. We could then remove all
system.profile-ll{-CC} that currently only define cm as well.



This is an interesting aspect. I agree that the language files should be
considered to represent the written language.

For language en, for example, we possibly could reduce to four files:

po/en.po                       (generic)
po/en-GB.po                    (country-specific)
user/wp/system.profile         (generic, unit: cm)
user/wp/system.en_US.profile   (inch instead of cm)

(Using hyphen if focus is on language and underscore if focus is on locale.)

The template file&lt;/pre&gt;</description>
    <dc:creator>Ingo Brückl</dc:creator>
    <dc:date>2012-05-16T14:16:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23968">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23968</link>
    <description>&lt;pre&gt;
I wrote on Tue, 15 May 2012 21:22:49 +0200:


Focusing on the UI part however.

Ingo

&lt;/pre&gt;</description>
    <dc:creator>Ingo Brückl</dc:creator>
    <dc:date>2012-05-16T14:16:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23967">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23967</link>
    <description>&lt;pre&gt;
On Tue, May 15, 2012 at 3:46 PM, Ingo Brückl &amp;lt;ib&amp;lt; at &amp;gt;wupperonline.de&amp;gt; wrote:

However lines for these apparently exist in two of the Makefiles, and
it is from there that they should be removed to leave the code as
clean as possible.

user/wp/Makefile.am
user/wp/templates/Makefile.am



I am deeply committed to linguistic self-determination and I maintain
a Pootle instance with 130-odd languages (or variants).  I am not
however in favor of maintaining meaningless distinctions and doing
extra work when it makes no real difference.

Simply because it is possible to make a distinction does not mean it
is worthwhile to do so.  The vocabulary from which a word processing
program draws (even one as fully featured as AbiWord) is a limited
universe of phrases.  Were this a program that were rich in culinary
or cultural terms, I might make the opposite argument, but it is a
word processing tool.  Certain distinctions are common in FLOSS L10n
(pt, pt_BR, en_US, en_GB, various script variations in Slavic
languages between&lt;/pre&gt;</description>
    <dc:creator>Chris Leonard</dc:creator>
    <dc:date>2012-05-15T20:52:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.editors.abiword.devel/23966">
    <title>Re: [PATCH] Automatize creation of DATA lists for Makefiles</title>
    <link>http://permalink.gmane.org/gmane.editors.abiword.devel/23966</link>
    <description>&lt;pre&gt;
On Tue, May 15, 2012 at 3:46 PM, Ingo Brückl &amp;lt;ib&amp;lt; at &amp;gt;wupperonline.de&amp;gt; wrote:


As a Canadian, I think I can say that an en_CA localization does not
add value to AbiWord in any way.

pat

&lt;/pre&gt;</description>
    <dc:creator>Patrick Lam</dc:creator>
    <dc:date>2012-05-15T19:54:09</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.editors.abiword.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.editors.abiword.devel</link>
  </textinput>
</rdf:RDF>

