Hi,

I need to work with some more properties that the actual ones on lpod.
I enable the properties I need in a fork of lpod:
danieltellez@42c1d8a

I know this is not the best way to do this things, mainly because it is difficult to maintain these fork in parallel with yours with my properties.

Is it possible to pull these properties on your code ?
Or is this any way to work with some kind of plugin over your code ?

As is known to all, ODF have versions 1.0, 1.1 and 1.2

LibreOffice/OpenOffice also come with "ODF 1.2 Extended", which I haven't fully understood why we need such option.

Hi,

I am trying to create an image inside a document, using frames, as you suggests in docs:

uri = my_doc.add_file(chartfilename)
image_frame = odf_create_image_frame(
  url = uri,
  name = "Chart",
)
my_doc.get_body().append(image_frame)

I tried also by adding position and size properties, but neither works.

I've noted in your examples that for presentations you first call get_draw_page. It is needed to do that also in documents ? Can I add images on documents or only on presentations ?

We need that to be able to work on the code without installing it in our virtualenv everytime we do a modification.

Code example:

from lpod.document import odf_new_document
from lpod.heading import odf_create_heading
import lpod

print lpod.version
doc = odf_new_document("text")
body = doc.get_body()
heading = odf_create_heading(level=1,text="A heading",start_value=11)
doc.save("/tmp/bug.odf")

throws:

v1.1.3
Traceback (most recent call last):
File "lpod_bug_report.py", line 8, in
heading = odf_create_heading(level=1,text="A heading",start_value=11)
File "/usr/local/lib/python2.7/dist-packages/lpod/heading.py", line 64, in odf_create_heading
element.set_attribute('text:start-value', start_value)
File "/usr/local/lib/python2.7/dist-packages/lpod/element.py", line 607, in set_attribute
element.set(name, value)
File "lxml.etree.pyx", line 695, in lxml.etree._Element.set (src/lxml/lxml.etree.c:35440)
File "apihelpers.pxi", line 563, in lxml.etree._setAttributeValue (src/lxml/lxml.etree.c:15471)
File "apihelpers.pxi", line 1364, in lxml.etree._utf8 (src/lxml/lxml.etree.c:22039)

TypeError: Argument must be bytes or unicode, got 'int'

Documentation:

lpod.heading.odf_create_heading(level, text=None, restart_numbering=False, start_value=None, suppress_numbering=False, style=None)¶

start_value – int

is it possible implement a good api for to merge/concatenate two or more filese in one without lost formattation and style of every element?

if i use lpod-merge.py in scripts it no take good the style formar of the last files

About the Lpod Project link is not working in README.md

http://lpod-project.net

After downloading lpod-1.1.3, installation fail :
No such file or directory: 'version.txt'
No such file or directory: 'MANIFEST'

After downloading using git :
ImportError: No module named setuptools

Hello !
I am working on porting lpod-python to python 3.
Do you think it would be interesting for community ?
Thank you

Many, if not all, pro-ODF sites still link to http://www.lpod-project.org/

Is this project is still under maintenance?, I would like to contribute to this project for GSOC 2018. It would be helpful if I can get any guidance on the project

With rows to repeat function enabled in spreadsheet, if you do table.set_value((x,y), value), the value is shift-down. It seems it will take the first non-repeating row as row 0.

is it possible to get a table of contents (toc) of an existing .odt file as element?

Because i need to update a TOC, which is already included.

I am having issues using several different fonts (can change font sizes but not the font face).

The perl version of the library states:

However, if you don't take care, your font specification could produce no visible effect in some situations. Of course you have checked the availability of the needed font in your environment. But, in any ODF document, a font must be declared to be used by a style. Fortunately such declaration is very easy to register thanks to the document-based set_font_declaration() method:

    $doc->set_font_declaration("Times New Roman");

Python binding appears to be missing this capability

This is how I am doing:

    stylename = str(uuid.uuid1())
    break_style = odf_create_style('text', stylename, break_before='page')
    break_style.set_properties(page_break_before='page', area="paragraph")
    self.report.insert_style(break_style)
    breakp = odf_create_paragraph('', stylename)
    body = self.report.get_body()
    body.append(breakp)

And it is not working. I've also tried with a paragraph with some text.

Currently the documentation is at documentation/html, why don't you put the documentation on the web site?

BTW, Odfpy ( https://joinup.ec.europa.eu/software/odfpy/home ) and ezodf2 ( https://github.com/iwschris/ezodf2 ) also make documentation hard, if not impossible, to access.

I was curious about this tool set for generating diff+patch type of workflow. It is great for text files and i wondered if it can be used for documents with this tool-set?

First time I added images, I did by passing an URL, so lpod insert the image as a reference. It was enough for me, up to now, that I need to be embedded.

When I use the second method it seems like the image has been added correctly, but I can't open the document on LibreOffice (3.6.2.2). It throws an exception about corrupted file.

I've tried few workarounds to do it, but nothing works. Could be something as simple as reader version incompatibility ? Is there a known issue ?

Please tag the releases for 1.1.6 and 1.1.7.