On Fri, Jan 21, 2011 at 1:36 PM, Do Hong Phuc wrote:
> On Fri, Jan 21, 2011 at 10:06 AM, Nguyen Vu Hung
> wrote:
>>
>> On Fri, Jan 21, 2011 at 11:53 AM, Do Hong Phuc
>> wrote:
>> > This issue makes our migration some hundreds users from Ms Office 2k7 to
>> > LibO postponed.
>> A temporary workar
On Fri, Jan 21, 2011 at 10:06 AM, Nguyen Vu Hung wrote:
> On Fri, Jan 21, 2011 at 11:53 AM, Do Hong Phuc
> wrote:
> > This issue makes our migration some hundreds users from Ms Office 2k7 to
> > LibO postponed.
> A temporary workaround is using LibOffice Base.
>
> I don't think a spreadsheet is d
On Fri, Jan 21, 2011 at 11:53 AM, Do Hong Phuc wrote:
> This issue makes our migration some hundreds users from Ms Office 2k7 to
> LibO postponed.
A temporary workaround is using LibOffice Base.
I don't think a spreadsheet is designed for handling that much data,
but a database is.
Keep doing it
This issue makes our migration some hundreds users from Ms Office 2k7 to
LibO postponed. Full compatibility with Ms 2k7 formats maybe make LibO more
popular. Why not try to fix this issue in version 3.3 Final but let it in
some other minor version like 3.4 , 3.5 , 3.6 etc..?
On Wed, Jan 19, 20
On Wed, 2011-01-19 at 06:52 -0500, Charles Marcus wrote:
> On 2011-01-19 12:43 AM, Kohei Yoshida wrote:
> > Fixing it the right way will be very invasive, and risks breaking the
> > xls (not xlsx, xls the binary) import and export filters into utterly
> > useless state (I mean, really useless). Th
On 2011-01-19 12:43 AM, Kohei Yoshida wrote:
> Fixing it the right way will be very invasive, and risks breaking the
> xls (not xlsx, xls the binary) import and export filters into utterly
> useless state (I mean, really useless). This is because so much code is
> shared between the xls import/exp
On Wed, 2011-01-19 at 14:15 +0900, Nguyen Vu Hung wrote:
> On Wed, Jan 19, 2011 at 2:22 AM, Kohei Yoshida wrote:
> > Yes, it's a known issue which unfortunately didn't get fixed in time for
> > 3.3. The fix will be very x10 invasive, so we've decided to postpone it
> > until next minor release.
>
On Wed, Jan 19, 2011 at 2:22 AM, Kohei Yoshida wrote:
> Yes, it's a known issue which unfortunately didn't get fixed in time for
> 3.3. The fix will be very x10 invasive, so we've decided to postpone it
> until next minor release.
As far as I understand, supporting that feature will make LibO le
On Wed, 2011-01-19 at 02:07 +0900, Nguyen Vu Hung wrote:
> On Tue, Jan 18, 2011 at 5:29 PM, Do Hong Phuc wrote:
> > Dear All,
> >
> > Does anybody know why spreadsheets (.xlsx) over 65536 rows are not saved
> > fully in LibreOffice 3.3RC3 Calc? Only 65536 rows are saved and the rest
> > from 65537
On Tue, Jan 18, 2011 at 5:29 PM, Do Hong Phuc wrote:
> Dear All,
>
> Does anybody know why spreadsheets (.xlsx) over 65536 rows are not saved
> fully in LibreOffice 3.3RC3 Calc? Only 65536 rows are saved and the rest
> from 65537 is thrown away?
Dear Miss,
Kohei-san will answer you.
http://cgit.
Dear All,
Does anybody know why spreadsheets (.xlsx) over 65536 rows are not saved
fully in LibreOffice 3.3RC3 Calc? Only 65536 rows are saved and the rest
from 65537 is thrown away?
Thanks for your support!
--
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: htt
11 matches
Mail list logo
