> > Uses strutils;
> > ...
> >
> Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(AnsiReplaceStr(AnsiReplac
> > eStr(E
> > F.Field.AsString,#10,'
'),#13,'')),32767));
> >
> > Ludo
> >
> That's what I thought at first, too ;)
>
> But the & gets encoded again by the XML unit and you get:
>
On 12-8-2011 16:31, Ludo Brands wrote:
>> Excel needs an encoded LF:
>> First line.
Second line
>>
>> How can I produce that?
>>
>
> Uses strutils;
> ...
> Foutputdoc.CreateTextNode(LeftStr(UTF8Decode(AnsiReplaceStr(AnsiReplaceStr(E
> F.Field.AsString,#10,'
'),#13,'')),32767));
>
> Ludo
>
That's
> 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 li
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:
First line.
Second
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
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
> So far so good.
>
> If exporting dataset text (memo, string, ..) data to Excel XML text
> fields, which characters do I need to conv
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 i
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
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
So far so good.
If exporting dataset text (memo, st
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
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
11 matches
Mail list logo
