<html><head><style type="text/css">body, p, li { font-family: NokiaPureTextLight; }</style></head><body><div id="fenix-user-content">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Hello,</span></p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; font-family:'NokiaPureTextLight';"><br></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">sorry for top posting but I only have my phone with me.</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">I only know for presentations that the files converted do show up with wrong colors in LO due to LO assuming some defaults Calligra does not. Not sure about the other filters. If we want to promote the tool for the described usecase we should make sure these problems are fixed as otherwise all we will get is people complaining.<br></span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">--<br>Thorsten</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';"><br></span></p></div><br><div id="fenix-reply-header"><p>On 30/05/2012 17:43 matus.uzak@gmail.com wrote:<br></p></div><div id="fenix-quoted-body"><div>
Hi again,<br>
<br>
</div>
<div>
> And iWork sucks at that? After all they claim support*. Or is too expensive? I<br>
> would have guessed that iWork (Pages, Numbers, Keynote) is the natural choice<br>
> on OS X. Hm, all already 3 years old? So I guess they just suck to a degree :)<br>
> Or have a too unfamiliar interface/UX, compared to what people are trained to.<br>
> All guess work here.<br>
><br>
> * <a href="http://www.apple.com/iwork/compatibility/">http://www.apple.com/iwork/compatibility/</a><br>
<br>
</div>
<div>
People I have asked claim that OOo/LO does a much better job in means<br>
of compatibility with MS Office.<br>
<br>
</div>
<div>
I have collected a bunch of files in MS binary file formats created by<br>
iWorks that our filters classify as invalid<br>
and most of those can't be opened in MS Office 2003. MS Office 2007<br>
does a better job because input filters<br>
were improved. I have spent some time analyzing those and came to a<br>
conclusion that it's not worth to spent<br>
time on processing such invalid files at the moment. I can only<br>
generalize about the quality OOXML compatibility<br>
based on my experience with binary file formats. I don't have access<br>
to iWorks to analyze it's export filters on test data.<br>
<br>
</div>
<div>
>> Then I mentioned calligraconverter to people working at science<br>
>> academy and university. They were impressed<br>
>> that there's a command line tool enabling them batch conversions and<br>
>> can be included into scripts.<br>
><br>
> Did they also mention what would be their typical use cases for this tool?<br>
<br>
</div>
<div>
They usually have a bunch of files in MS file formats in a shared<br>
repository, so they could do batch conversion to ODF.<br>
And of course convert OOXML to ODF locally and continue using OOo/LO<br>
until especially Words are ready for everyday use<br>
of the whole population. :)<br>
<br>
</div>
<div>
We claim that "Calligra import filters for docx/xlsx/pptx are the best<br>
free translations tools available anywhere.", [2] and we should build<br>
on this and promote it better to attract potential sponsors. A<br>
separate calligraconverter package would make a good start.<br>
It would mean that people don't need to install the whole calligra<br>
suite. Can we consider this as a drawback?<br>
<br>
[2] <a href="http://www.apple.com/iwork/compatibility/">http://www.apple.com/iwork/compatibility/</a><br>
<br>
</div>
<div>
-matus<br>
<br>
</div>
<div>
On Wed, May 30, 2012 at 2:48 PM, Friedrich W. H. Kossebau<br>
<<a href="mailto:kossebau@kde.org">kossebau@kde.org</a>> wrote:<br>
> Hi,<br>
><br>
> Am Mittwoch, 30. Mai 2012, 12:31:45 schrieb <a href="mailto:kossebau@kde.org">kossebau@kde.org</a>:<br>
>> Hi,<br>
>><br>
>> I have had some time to socialize a bit and I have spent it by asking<br>
>> Mac users which office suite do they use. :)<br>
>> And the answer was OOo or LO recently. They simply have to deal with<br>
>> Microsoft office formats and communicate<br>
>> with people using MS Office on MS Windows.<br>
><br>
> And iWork sucks at that? After all they claim support*. Or is too expensive? I<br>
> would have guessed that iWork (Pages, Numbers, Keynote) is the natural choice<br>
> on OS X. Hm, all already 3 years old? So I guess they just suck to a degree :)<br>
> Or have a too unfamiliar interface/UX, compared to what people are trained to.<br>
> All guess work here.<br>
><br>
> * <a href="http://www.apple.com/iwork/compatibility/">http://www.apple.com/iwork/compatibility/</a><br>
><br>
>> -----<br>
>><br>
>> Then I mentioned calligraconverter to people working at science<br>
>> academy and university. They were impressed<br>
>> that there's a command line tool enabling them batch conversions and<br>
>> can be included into scripts.<br>
><br>
> Did they also mention what would be their typical use cases for this tool?<br>
><br>
>> And there's<br>
>> no information at calligra.org about calligraconverter.<br>
>><br>
>> Let's provide an option to download calligraconverter as a separate<br>
>> package. Mac OS X and GNU Linux users<br>
>> can still use OOo/LO to edit and save files to MIcrosoft formats but<br>
>> use calligraconverter to deal with OOXML.<br>
><br>
> +1<br>
><br>
> You made calligraconverter for a reason, there is demand for it.<br>
> Now if you want people to join the community around that product as users, it<br>
> needs to be googlable/discoverable and easily gettable. Nothing new, but just<br>
> be consequent :)<br>
><br>
> Cheers<br>
> Friedrich<br>
> _______________________________________________<br>
> calligra-devel mailing list<br>
> <a href="mailto:kossebau@kde.org">kossebau@kde.org</a><br>
> <a href="http://www.apple.com/iwork/compatibility/">http://www.apple.com/iwork/compatibility/</a><br>
</div>
<div>
_______________________________________________<br>
</div>
<div>
calligra-devel mailing list<br>
</div>
<div>
<a href="mailto:kossebau@kde.org">kossebau@kde.org</a><br>
<a href="http://www.apple.com/iwork/compatibility/">http://www.apple.com/iwork/compatibility/</a><br>
<br>
</div>
</div><br></body></html>