[libreoffice-users] Re: BUG: Writer seems to ignore some \par in RTF file

2013-03-15 Thread prino
Tom,

On 15 March 2013 10:50, Tom [via Document Foundation Mail Archive]
ml-node+s969070n4043988...@n3.nabble.com wrote:
 If it's just text then why not use the txt format?

Because it's text with limited bolding of some words.

 I'm not sure why your Odts are ending up so large.  Typically around 20-50Kb
 seems fairly normal for just a couple of pages.

The ODT's are not that big, but on z/OS I would have to create them as
the constituent XML files and those are huge!

 I feel i should apologise that MS never made the Rtf format OpenSource
 rather than proprietary and hid the format's specs so that other programs
 couldn't use it until years after each new release of it and then withdrew
 development of it after they lost their court case but MS is a 3rd party
 organisation and we have no control over what they do.

I don't think they're hidden any longer, and as for my problem, the
file I gave as an example is laughably simple, so don't blame M$ for
hidden specs. Writer should be able to import it correctly.

Robert
-- 
Robert AH Prins
robert(a)prino(d)org


 From: Robert Prins [hidden email]
To: Tom Davies [hidden email]
Cc: [hidden email] [hidden email]
Sent: Friday, 15 March 2013, 10:31
Subject: Re: [libreoffice-users] BUG: Writer seems to ignore some \par in
 RTF file

Tom,

On 15 March 2013 09:09, Tom Davies [hidden email] wrote:
 The Odt format is a zip container that holds an Xml file(s).  So my guess
 is
 that if you can generate Xml in text-files then it should be reasonably
 easy.

You've got to be kidding...

Take this line from a file (in fixed pitch font):
=== SOURCE ===
|   72 | 1386 |   43 |   26 |  112 |   14 | FL  RG  P   CH  D   GB  LV
NL  B   S   |
=== SOURCE ===

In RTF it's simple:
=== RTF ===
|   72 | 1386 |   43 |   26 |  112 |   14 | FL  RG  P   CH  D   GB  LV
NL  B   S   |\par
=== RTF ===

And in ODT?

=== ODT ===
text:p text:style-name=P1text:span text:style-name=T1| text:s
text:c=2/72 | 1386 | text:s text:c=2/43 | text:s
text:c=2/26 | text:s/112 | text:s text:c=2/14 | FL
text:s/RG text:s/P text:s text:c=2/CH text:s/D text:s
text:c=2/GB text:s/LV text:s/NL text:s/B text:s
text:c=2/S text:s text:c=2/|/text:span/text:p
=== ODT ===

Care to explain why Writer breaks up this line in umpteen parts, and
seems to do so on all places where there are two of more spaces? What
is wrong with spaces in XML? Why, so it seems to me, replace 2 spaces
with a *20* character substitute of text:s text:c=2/?

Also, in this case the RTF file is just 325kb. The content.xml is
 1,152kb.

Another RTF file is 2,887kb. For this one the content.xml is
merely 8,961kb, and even stranger: Open the RTF-saved-as-ODT, add
and insert and delete a single space at the very beginning, and save
again, and now content.xml is suddenly reduced to 7,056kb. Why
wasn't is saved like that right from the start?

RTF may have drawbacks, but for simple text it's vastly easier to
generate than the XML used in Writer. Add the fact that CPU time on
z/OS is rather more expensive than on Windoze boxes, and the case
against generating ODT files on z/OS is pretty strong... I'll probably
file the problem as a bug, but I won't hold my breath for the
solution.

Robert
--
Robert AH Prins
robert(a)prino(d)org

 But as you point out it does generate fairly different results on
 different
 machines using different OSes or / and different programs.  Then when
 generated you have no idea how it will display on other different
 machines,
 different OSes or in different programs.

 You are free to post it as a bug-report but it's an inherent problem with
 the format itself and one that MS never fixed.  Remember that this mess
 of a
 format and the vast waste of effort endure by quite a lot of people and
 companies did land MS in court and MS lost the case.  Some companies seem
 to
 have been put out of business by it's failures to be more
 cross-compatible.
 So, you are not alone.
 Regards from
 Tom :)


 
 From: Robert Prins [hidden email]
 To: Tom Davies [hidden email]
 Cc: [hidden email] [hidden email]
 Sent: Friday, 15 March 2013, 7:04
 Subject: Re: [libreoffice-users] BUG: Writer seems to ignore some \par
 in
 RTF file

 Tom,

 Maybe...

 But RTF has one huge advantage, it's very easy to create on other
 systems, as it is pure text. The file I posted is generate on IBM's
 z/OS. Maybe you can tell me how I can generate an ODT file on that
 platform?

 Robert
 --
 Robert AH Prins
 robert(a)prino(d)org


 On 15 March 2013 00:11, Tom Davies [hidden email] wrote:
 Hi :)
 MS developed Rtf making all the promises about cross-platform and
 cross-product compatibility that are currently being made for their ISO
 format.  Unfortunately they never quite lived up to those promises and
 got
 taken to court about it and lost the case.  So they stopped developing
 it
 and created the OOXML and got that registered as an ISO standard
 instead.
 Now people seem to be having similar problems with the new OOXML formats

[libreoffice-users] BUG: Writer seems to ignore some \par in RTF file

2013-03-14 Thread prino
If you open the following, name it whatever.rtf

=== CUT ===
{\rtf1\ansi\deff0
{\fonttbl
{\f0\fmodern\fcharset0\fprq1 Courier New;}}
\paperw16840\paperh11907\margl709\margr709\margt1418\margb567
\lndscpsxn
\cols2\colsx709
\pard\plain
\sl-140\slmult0\fs14
{\b Rows\par}{
\par
+--+\par
| Row  |\par
+--+\par
|1 |\par
|   60 |\par
+--+\par
\column
\par
\par
+--+\par
| Row  |\par
+--+\par
|   61 |\par
|  120 |\par
+--+\par
\column
\par
\par
+--+\par
| Row  |\par
+--+\par
|  121 |\par
+--+\par
| Tot  |\par
+--+\par
}}
=== CUT ===

in Word, it will correctly put two blank lines above the second and third
column. Open it in Writer (4.0.1.2) and there will be only *one* blank line
above columns two and three. 

Not good!



--
View this message in context: 
http://nabble.documentfoundation.org/BUG-Writer-seems-to-ignore-some-par-in-RTF-file-tp4043901.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] LO cannot correctly import quoted text

2012-10-01 Thread prino
I’ve got some data, that, very simplified looks like

1,2,3,4,“Cell E1”
2,2,3,4,“Cell E2”
3,2,3,4,”“Cell E3”“
4,2,3,4,“Cell E4”
5,2,3,4,”“Cell E5”“

i.e. it contains both text and quoted text.

When I import this (LO 3.6.1, W7-64, UK English) using

Codepage: System
Separated by: Comma
Merge delimiters: Yes (irrelevant)
Text delimiter: “

Quoted fields as text: Yes
Detect special numbers: Yes

line 4 of the input file ends up as the second line in cell E3 and the final
“CELL E5” (in cell E4) is followed by a newline

How do I get this imported correctly - any solutions that suggest to modify
the input data are unacceptable, the data comes from z/OS and for what it's
worth, imported correctly in LO 3.5.4...



--
View this message in context: 
http://nabble.documentfoundation.org/LO-cannot-correctly-import-quoted-text-tp4010110.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted


[libreoffice-users] Bar charts with user-defined x-axis

2012-06-25 Thread prino
Suppose I've got the following data:

Year  KM
1980 2,981.2

1982 7,901.6
198312,021.6

1985 8,529.9
1986 5,903.7
1987 1,951.7
1988 8,152.8
1989 6,528.1
199015,346.3
1991 6,120.6
199211,389.0
199313,186.1
199415,542.9
199521,593.5
199610,384.7
1997 4,548.8
1998 5,395.5
1999 5,820.4
200030,360.0
2001 8,328.8
200219,446.9
2003 2,554.6
200415,864.1
2005   788.6
200610,924.0
2007 1,712.9
200814,957.1
2009 7,098.7
201022,289.4
201129,866.7
2012 9,925.0

And I want to put it into a bar-graph. No problem, I get this:
http://nabble.documentfoundation.org/file/n3992054/km.png 

However, how do I get the years on the X-axis rather than the meaningless
1..33 numbers?



--
View this message in context: 
http://nabble.documentfoundation.org/Bar-charts-with-user-defined-x-axis-tp3992054.html
Sent from the Users mailing list archive at Nabble.com.
-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] Re: Bar charts with user-defined x-axis

2012-06-25 Thread prino
Thank you, this works!

It shows every third year as label (1980/1983/1986...) Is there a way to
show only every n-th year? For this chart  n=5 would be my choice.


--
View this message in context: 
http://nabble.documentfoundation.org/Bar-charts-with-user-defined-x-axis-tp3992054p3992128.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] Re: Bar charts with user-defined x-axis

2012-06-25 Thread prino
Hi Regina,

On Mon, Jun 25, 2012 at 1:02 PM, Regina Henschel [via Document Foundation
Mail Archive] ml-node+s969070n3992144...@n3.nabble.com wrote:
 prino schrieb:
 Thank you, this works!

 It shows every third year as label (1980/1983/1986...) Is there a way to
 show only every n-th year? For this chart  n=5 would be my choice.

 Set chart in edit mode.
 Format  Axis  x-Axis
 Dialog page Scale. Set Type to 'Date'.
 Then you get elements on that dialog page to trim the axis labels.

OMG, holy this, it works, but there is absolutely nothing intuitive about
it...

Thanks,

Robert

--
View this message in context: 
http://nabble.documentfoundation.org/Bar-charts-with-user-defined-x-axis-tp3992054p3992166.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] Re: LO 3.4.3 Writer cannot handle RTF document

2011-11-07 Thread prino

Tom wrote:
 
 If a machine appears to be dead then often you can still use it by booting
 up a LiveCd session of a GnuLinux distro.   
Not in this case, a number of the capacitors on the motherboard have blown
and even with replacements it won't boot anymore. :(


--
View this message in context: 
http://nabble.documentfoundation.org/LO-3-4-3-Writer-cannot-handle-RTF-document-tp3485447p3486456.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] RE: LO 3.4.3 Writer cannot handle RTF document

2011-11-07 Thread prino

Dennis E. Hamilton wrote:
 
 Using the RTF as provided in Robert's e-mail, Wordpad displays everything 
 through the Total amount due row and that is the end.  The additional
 RTF 
 after that row is has no effect.
Same here, I've got other similar invoices but they display OK. Now trying
to figure out the difference.


Dennis E. Hamilton wrote:
 
 In Microsoft Word 2010, the document displays completely, all the way down
 to 
 the Registered in England line with VAT number placeholder at the bottom
 of 
 the page.
 
 Libre Office 3.3.2 also opens the RTF document perfectly, except that one
 line 
 at the bottom of the page rolls off onto a separate sheet.  The layout is
 not 
 quite so faithful as the Word 2010 appears to be.
 
 I saved the Word version as an ODF Text (.odt) document and it is all
 there. 
 I had to delete two rows of blank lines to get the bottom matter back onto
 the 
 single sheet (perhaps because of default paper-size differences on my US 
 configuration).
The document is for (European) A4, and US Letter is ~18 mm shorter, which
explains the page-overflow.


Dennis E. Hamilton wrote:
 
 I can make the ODT available to Robert if that satisfies his short-term 
 requirement.  It doesn't explain why WordPad 6.1 SP1 stumbles.
No need, these are old invoices, I can make future ones with Writer, but
given the fact hat the full RTF spec is available, I would have expected
Writer to handle it.

Robert

--
View this message in context: 
http://nabble.documentfoundation.org/LO-3-4-3-Writer-cannot-handle-RTF-document-tp3485447p3486476.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] Re: LO 3.4.3 Writer cannot handle RTF document

2011-11-07 Thread prino

Pedro wrote:
 
 
 prino wrote:
 I would appreciate it if someone could have a look at to why this
 document doesn't display the way it should be displayed.
 
 
 Actually RTF must be the worse format in the world :)
 
 I opened your document under XP SP3 Pro x86 in 6 different word processors
 and it didn't look the same in any two: Wordpad, Abiword 2.9.0,
 LibreOffice 3.4.4RC2, IBM Lotus Symphony 3,  Kingsoft Office 2012 and
 Softmaker Office 2012.
 
 I would say that the only one where it looked complete and properly
 formatted was in Softmaker, which isn't surprising :)
 
 If you are using LibreOffice I advise you to stick with ODF. If you need
 to send files to people who don't use LibreOffice, then stick with doc
 (not docx)
 
If I need to send documents to others, I use plain text, where I might add
some *bold* or _underscore_ tags, but nothing more. Files are small and
everyone can read plain text!

Actually, other than the fact that LibreOffice cannot read (some) RTF
correctly, its implementation of an RTF writer is absolute, excusez-le-mot,
Sh*te, with a capital S!  It doesn't do any factoring of tags, and the
documents it produces are humongous.

An example? 

I have a program that processes my, don't laugh,  hitchhiking data. (Yes, at
the age of 51 I still hitchhike, see http://hitchwiki.org/community/prino/ )
It optionally outputs the files in RTF format (it dates back to the early
1990'ies, i.e. well before OO  LO) All of the resulting RTF files contain
the absolute minimum of tags and one has a size of just 299kb, a mere 26kb
more than the plain text file.

M$ Word was already bad, blowing it up to around 330kb, but LO Writer
completely takes the piss by saving it as a 1.1Mb RTF file, and looking at
it makes you wonder why Writer adds the same set of completely irrelevant
tags over and over and over (and over and over ad nauseam) again. 

As an aside, the fact that it's very easy to turn plain text into RTF using
about any editor and/or simple scripts is a big advantage that RTF has over
ODF, try making an ODT file on IBM's z/OS...

Robert


--
View this message in context: 
http://nabble.documentfoundation.org/LO-3-4-3-Writer-cannot-handle-RTF-document-tp3485447p3486607.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted



[libreoffice-users] LO 3.4.3 Writer cannot handle RTF document

2011-11-06 Thread prino
System: Windows XP SP3 (+everything after it)
LO: LibreOffice 3.4.3 
OOO340m1 (Build:302)

Recently my PC died (and with it the freebie version of Word 2002
(10.2627.2625)) and I having never had any problems with XLS  files and LO
Calc, I expected LO Writer to have little trouble with he following very
simple Word .RTF document.

How wrong can one be...

I would appreciate it if someone could have a look at to why this document
doesn't display the way it should be displayed.

=== CUT ===
{\rtf1\ansi\uc1\deff0
{\fonttbl
{\f0\froman\fcharset0\fprq2 Times New Roman;}
{\f1\fmodern\fcharset0\fprq1 Courier New;}
{\f2\fscript\fcharset0\fprq2 Monotype Corsiva;}}
\paperw11907\paperh16840\margl992\margr1418\margt567\margb567
\pard\plain\qj
\fs20
{\b\f2\fs32\qc XX XX X Ltd\par }
\par
\par
{\b\ql XXX XXX \par
XXX XXX\par
 \par
XXX}
{\ul
\par
\par
\par }
\pard
\ql
\tx993
\tx1985
\tqdec
\tx2694
{Invoice no:
\tab X-XX
\tab
\tab Date:
\tab XX X 2011
\par }
\pard
{\ql\par
\par
Dear Sirs,\par
\par }
\pard
{\qj You have never received written permission to send any email to
 xxx...@x.xxx and as such the ten emails that my company,
 the owner of the x.xxx domain, received on 2010-05-28, 2010-06-29,
 2010-09-29, 2011-01-26 (3x), 2011-02-23, 2011-03-25, 2011-05-26 and
 2011-06-22 are SPAM, in direct violation of EU directive 2002/58/EC.\par
\par
As it costs me time and effort to deal with such messages, time that I
 could otherwise use more productively, and because I have called you
 before about the abuse of this email address used by my company in July
 2010 and March 2011 I have no other choice than to charge you for this
 time. I think a reasonable amount is GBP 100 per spam message, but if
 you think that this is too much, I am quite happy to let the courts in
 England decide on a more appropriate amount, in the case of Nigel
 Roberts v Media Logistics Limited before the Colchester County Court in
 2005 (Claim No: 5CO03667) the defendant paid GBP 300 to settle the
 claim for a {\b single} spam message.\par
\par
Needlessly to say, I also want you to remove every trace of the above
 email address from your systems.\par
\par }
\trowd\trgaph107\trleft-107\cellx5529\cellx6664
\pard\ql\intbl
{Processing 10 spam messages @ GBP 100 per message\cell }
\pard\ql\intbl
\tqdec\tx593 {\b 1,000.00\cell }
\pard\ql\intbl
{\trowd\trgaph107\trleft-107\cellx5529\cellx6664\row }
\pard\ql\intbl
{VAT @ 20%\cell }
\pard\ql\intbl
\tqdec\tx593 {\b 200.00\cell }
\pard\ql\intbl
{\trowd\trgaph107\trleft-107\cellx5529\cellx6664\row }
\trowd\trgaph107\trleft-107\cellx6664
\pard\ql\intbl
{\cell }
\pard\ql\intbl
{\trowd\trgaph107\trleft-107\cellx6664\row }
\trowd\lastrow\trgaph107\trleft-107\cellx4819\cellx5529\cellx6664
\pard\ql\intbl
{\b Total amount due\cell }
{\b GBP\cell }
\pard\ql\intbl
\tqdec\tx593 {\b 1,200.00\cell }
\pard\ql
{\trowd\lastrow\trgaph107\trleft-107\cellx4819\cellx5529\cellx6664\row }
\par
\pard
\qj
{Payment is due }
{\b immediately}
{, please transfer the sum above to our account with X plc. Our
banking details are:\par }
\par
\pard
\ql
\tx1276
\tx1418
{\b Accountholder}{\tab :\tab }
{\f1 XX XX X Ltd\par }
{\b IBAN}{\tab :\tab }
{\f1      XX\par }
{\b BIC}{\tab :\tab }
{\f1 XXX\par\par }
\pard
\ql
{The address of the bank is:\par
\par }
{\b X XX plc,\par
,\par
XXX XX XXX XX,\par
XXX,\par
XX XXX,\par
XX XXX\par }
\par
\par
\par
\par
\par
\par
\par
\par
\par
\par
\par
\par
\par
{\b\f1\fs16\qj
XX XX X Ltd reserves the right to claim statutory interest at 8%
above the
 Bank of England reference rate in force on the date the debt becomes
overdue and at
 any subsequent rate where the reference rate changes and the debt remains
unpaid in
 accordance with the Late Payment of Commercial Debts (Interest) Act 1998 as
amended
 and supplemented by the Late Payment of Commercial Debts Regulations 2002.
\par }
\pard
\par
\pard
\qc
{\f1\fs16 XX XX X Limited, XX XXX X, , XXX,
XXX, XXX XXX\par
Registered in England No XXX   Registered office as above   }
{\b\f1\fs16 VAT number XXX  XX}}
=== CUT ===

Robert

--
View this message in context: 
http://nabble.documentfoundation.org/LO-3-4-3-Writer-cannot-handle-RTF-document-tp3485447p3485447.html
Sent from the Users mailing list archive at Nabble.com.

-- 
For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted