New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[export] prefer ODF (.ods) instead of OOXML (.xlsx) #1206

Open
DJCrashdummy opened this Issue Jun 11, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@DJCrashdummy
Contributor

DJCrashdummy commented Jun 11, 2018

Expected behaviour

possibility to export to an ods-file (not just for the invoices).

Actual behaviour

beside print/html and pdf, exporting is only possible as xlsx and csv.

Steps to reproduce

go to the export-extention and have a look at the possible options...

Reproducible on demo.kimai.org? [yes|no]

yes

Kimai version [for example: dev 1.1.0.1389|github master|github develop]

v1.3.1.1394

Relevant log entries from log file (debug tab or temporary/logfile.txt)


don't get me wrong, i appreciate the variety of available options, but i don't get the inconsistency between invoices and export... and since there is obviously no technical obstacle, why do you feature the problematic OOXML instead of ODF?

for sure csv is the most important option for export and i'm thankful for it, but my noobs aren't used to raw data and prefer some nicer looking pre-formatted table...
yes, i know i can somehow prepare an ods-template and use the invoices-extension to get the same (or something even more matched to my/our needs) as an ods-file, but the export-extension seems much easier/better to handle for me.
...and not to talk about the fact, that it took me a huge effort, much time and endless discussions to get our noobs away from OOXML and now a FOSS-project i want to recommend uses OOXML instead of ODF. 😞

@simonschaufi

This comment has been minimized.

Member

simonschaufi commented Jun 11, 2018

Kimai has a long story already. This software is more than 10 years old already and is really hard to maintain because of the old code base. I don't know why the founders decided it this way but we currently have to deal with it that export and invoice extension do very similar things. In my opinion the export was meant for raw data export while the invoice more for a beautiful rendering of the data with your own templates (html or odt). If you don't need the export module, you can simply disable it.

why do you feature the problematic OOXML instead of ODF?

sorry, I don't get what you mean.

@DJCrashdummy

This comment has been minimized.

Contributor

DJCrashdummy commented Jun 11, 2018

why do you feature the problematic OOXML instead of ODF?

sorry, I don't get what you mean.

well... i'm not sure about which part you didn't get, so sorry if i'm explaining obvious things for you!

  • OOXML (e.g. xlsx, docx,...) is a problematic file format (although it was normalised) because it still contradicts other norms and was made so complicated by microsoft, that still MS Office is the only software which renders it nearly correct (but still not the complete norm!)... as "icing on the cake" there also still persist rendering differences between MS Office for Windows and MS Office for macOS; and simply no software is available for Linux.
    --> and all these still more than ~15(!) years after its first introduction.
  • ODF (e.g. ods, odt,...) is a real open format, free for everyone; which respects all existing norms and has more than one software available on every major platform which can completely read & write these files.
  • with "featuring" i refer to the Kimai export-extension, where you can only choose between csv or xlsx (=OOXML) if you have to further process the data... no possibility to get an ods (=ODF). 🙁
    and if you need the exact values (e.g. see some time-columns), it gets even worse: because then you have no other choice and forced to use xlsx. ☹️

is there any chance to get an ods-file from the export-extension? - maybe at least with some kind of a workaround?

Kimai has a long story already. This software is more than 10 years old already and is really hard to maintain because of the old code base.

yes, i read this at some other places... but concerning this, Kimai works pretty smooth and also looks still nice! 👍

I don't know why the founders decided it this way but we currently have to deal with it that export and invoice extension do very similar things.

IMHO that's not really the point, i kind of like both extensions... the invoice-extension for its power and possibilities if you dig into it and the export-extension for it's better GUI and detailed selection (in short: much quicker results, especially for noobs and/or not recurring tasks).

In my opinion the export was meant for raw data export while the invoice more for a beautiful rendering of the data with your own templates (html or odt).

well... i also guess so, which is IMHO not the worst idea. 😉

If you don't need the export module, you can simply disable it.

yes, i read about it and know how to do it... but i rather would deactivate the invoices-extension since we probably use Kimai for internal time tracking only, but the lacking easy export to ods kind of hurts... 🙁

@simonschaufi

This comment has been minimized.

Member

simonschaufi commented Jun 13, 2018

Since you are the only person requesting this feature, I don't just want to invest a day or two for a very specifig customer request. In this case I ask you to sponsor this feature.

Please tell me if you want this special export to be implemented by me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment