LibreOffice 3.6.0: behind the scenes
people.gnome.org
LibreOffice 3.6.0: behind the scenes
1–10 of 23 posts
Re: LibreOffice 3.6.0: behind the scenes
#2Re: LibreOffice 3.6.0: behind the scenes
#3Most APIs are based on English so this makes a very messy combination. And yet people do it often, hindering the possibility of foreigners to contribute.
A recent example I've run into is the WYSIWYG editing extension for ShareJS, with all comments in Russian. I'd love to reuse it, but this just keeps me away:
https://github.com/rizzoma/ShareJS/blob/master/src/client/ri...
(note: I can read Cyrillic characters and do understand some Russian, but still)
Re: LibreOffice 3.6.0: behind the scenes
#4I think it's remarkable how much the LibreOffice folks have achieved compared to what was acheived when Sun was running this project!
Re: LibreOffice 3.6.0: behind the scenes
#5In fact, most spreadsheets today are created using OOXML, so it might be easier (notionally speaking) than the binary XLS format.
I daresay, there is a very, very large market for this - especially in Asia. I dont need the same for Word or Powerpoint - PDFs work fine in an emergency. For spreadsheets, I dont have an alternative.
Re: LibreOffice 3.6.0: behind the scenes
#6"German comments removal" sounds like a lot of work. It is always very annoying when programmers comment (or even name their variables/functions/whatever) using another language than English. Most APIs are based on English so this makes a very messy combination. And yet people do it often, hindering the possibility of foreigners to contribute. A recent example I've run into is the WYSIWYG editing extension for ShareJ…
Re: LibreOffice 3.6.0: behind the scenes
#7"German comments removal" sounds like a lot of work. It is always very annoying when programmers comment (or even name their variables/functions/whatever) using another language than English. Most APIs are based on English so this makes a very messy combination. And yet people do it often, hindering the possibility of foreigners to contribute. A recent example I've run into is the WYSIWYG editing extension for ShareJ…
Wikipedia: > The German company StarDivision in Lüneburg (founded by 16-year-old Marco Börries in 1984) wrote the original components of StarOffice
Re: LibreOffice 3.6.0: behind the scenes
#8Will pay a lot of money for a Linux-compatible Excel feature-parity version of a spreadsheet. In fact, most spreadsheets today are created using OOXML, so it might be easier (notionally speaking) than the binary XLS format. I daresay, there is a very, very large market for this - especially in Asia. I dont need the same for Word or Powerpoint - PDFs work fine in an emergency. For spreadsheets, I dont have an alternat…
OOXML is a beastly specification, because it's not just a description of how to create a document or spreadsheet -- it includes artifacts to maintain compatibility with MS Office software from the early 90's.
Re: LibreOffice 3.6.0: behind the scenes
#9Will pay a lot of money for a Linux-compatible Excel feature-parity version of a spreadsheet. In fact, most spreadsheets today are created using OOXML, so it might be easier (notionally speaking) than the binary XLS format. I daresay, there is a very, very large market for this - especially in Asia. I dont need the same for Word or Powerpoint - PDFs work fine in an emergency. For spreadsheets, I dont have an alternat…
Re: LibreOffice 3.6.0: behind the scenes
#10Will pay a lot of money for a Linux-compatible Excel feature-parity version of a spreadsheet. In fact, most spreadsheets today are created using OOXML, so it might be easier (notionally speaking) than the binary XLS format. I daresay, there is a very, very large market for this - especially in Asia. I dont need the same for Word or Powerpoint - PDFs work fine in an emergency. For spreadsheets, I dont have an alternat…
It's a tough thing to do -- particularly with Excel -- many spreadsheets include VBA code and other stuff that has dependencies on other parts of the Microsoft stack. OOXML is a beastly specification, because it's not just a description of how to create a document or spreadsheet -- it includes artifacts to maintain compatibility with MS Office software from the early 90's.
Not to mention the various versions of it (e.g ECMA vs ISO, and their revisions) which led to differing and incompatible implementations, numerous areas where things are ambiguous or undefined, and things that are defined by referencing the undisclosed DOC/XLS spec.