Re: [fpc-pascal] Working Free Pascal android JNI example

2011-08-12 Thread Felipe Monteiro de Carvalho
Well, the hack doesn't seam to really work well anyway, because it crashes executables generated by the compiler =( So one can either activate the hack and have a compiler only for DLLs or not have it and have a compiler only for executables... Where does argv and argc come from? From dllprt0.as

Re: [fpc-pascal] Working Free Pascal android JNI example

2011-08-12 Thread Felipe Monteiro de Carvalho
Or more generally: Any ideas of where / what I should look for to fix this? -- Felipe Monteiro de Carvalho ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal

[fpc-pascal] XMLXSDExport: line ending in Excel cells

2011-08-12 Thread Reinier Olislagers
Hi list, I've been refactoring the XMLXSDExport code and am now busy fixing some bugs based on testing. I'd appreciate your input. In Excel text fields, you can generate a line ending by pressing Alt-Enter. On export to XML this is written as #10; So far so good. If exporting dataset text

[fpc-pascal] Should Lazarus and FPC release library updates separately from product updates?

2011-08-12 Thread Frank Church
Whenever updates are made it is difficult to tell whether they are due to updates or fixes in the libraries, ie FCL, LCL etc or the product ie the Lazarus IDE and the FreePascal language and compiler. Unless library updates don't depend on product updates shouldn't they be kept separate? I don't

Re: [fpc-pascal] Should Lazarus and FPC release library updates separately from product updates?

2011-08-12 Thread Jonas Maebe
On 12 Aug 2011, at 13:04, Frank Church wrote: Unless library updates don't depend on product updates shouldn't they be kept separate? I don't know if it is something already done that is not explained well enough or is not done at all? It is not done at all for FPC. The reason is that

[fpc-pascal] Re: XMLXSDExport: line ending in Excel cells

2011-08-12 Thread Reinier Olislagers
On 12-8-2011 12:32, Reinier Olislagers wrote: In Excel text fields, you can generate a line ending by pressing Alt-Enter. On export to XML this is written as #10; So far so good. If exporting dataset text (memo, string, ..) data to Excel XML text fields, which characters do I need to

Re: [fpc-pascal] XMLXSDExport: line ending in Excel cells

2011-08-12 Thread michael . vancanneyt
On Fri, 12 Aug 2011, Reinier Olislagers wrote: Hi list, I've been refactoring the XMLXSDExport code and am now busy fixing some bugs based on testing. I'd appreciate your input. In Excel text fields, you can generate a line ending by pressing Alt-Enter. On export to XML this is written as

[fpc-pascal] Explicit encoding of LF in XML

2011-08-12 Thread Reinier Olislagers
All, Looking at multiline support of text/string cells for export to Excel XML format. My code, such as: TDOMElement(FieldNode).SetAttribute('ss:Type', 'String'); FNode := Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(EF.Field.AsString), 32767)); writes out a cell like: CellData

RE : [fpc-pascal] Explicit encoding of LF in XML

2011-08-12 Thread Ludo Brands
All, Looking at multiline support of text/string cells for export to Excel XML format. My code, such as: TDOMElement(FieldNode).SetAttribute('ss:Type', 'String'); FNode := Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(EF.Field.AsString ), 32767)); writes out a cell like:

Re: RE : [fpc-pascal] Explicit encoding of LF in XML

2011-08-12 Thread Reinier Olislagers
On 12-8-2011 16:31, Ludo Brands wrote: Excel needs an encoded LF: CellData ss:Type=StringFirst line.#10;Second line/Data/Cell How can I produce that? Uses strutils; ... Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(AnsiReplaceStr(AnsiReplaceStr(E

RE : RE : [fpc-pascal] Explicit encoding of LF in XML

2011-08-12 Thread Ludo Brands
Uses strutils; ... Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(AnsiReplaceStr(AnsiReplac eStr(E F.Field.AsString,#10,'#10;'),#13,'')),32767)); Ludo That's what I thought at first, too ;) But the gets encoded again by the XML unit and you get: amp;#10; Of course