On 18 Oct 2008, at 16:32, Zaher Dirkey wrote:
I notice UTF8 from Delphi not Compatible with Lazarus/FPC and vise
versa.
It Corrupt the characters.
When you set the encoding of an FPC source file to UTF-8 (either by
adding a BOM or by using {$codepage utf-8}), then
a) all constant strings
I notice UTF8 from Delphi not Compatible with Lazarus/FPC and vise versa.
It Corrupt the characters.
On Sat, Oct 18, 2008 at 4:12 PM, Jonas Maebe <[EMAIL PROTECTED]> wrote:
>
> On 18 Oct 2008, at 14:38, Zaher Dirkey wrote:
>
>> Hi, i have some units shared between 2 Project First in Delphi 2007
>>
On 18 Oct 2008, at 14:38, Zaher Dirkey wrote:
Hi, i have some units shared between 2 Project First in Delphi 2007
and the second in Lazarus for Wince
for unicode support on WinCE i converted my my files to UTF8, but i
discovered that Delphi not take my local language in shared units as
will, an
Hi, i have some units shared between 2 Project First in Delphi 2007
and the second in Lazarus for Wince
for unicode support on WinCE i converted my my files to UTF8, but i
discovered that Delphi not take my local language in shared units as
will, and if convert the files in Delphi IDE it work in De
On Fri, Oct 17, 2008 at 3:01 AM, Francisco Reyes <[EMAIL PROTECTED]> wrote:
> What do you mean by by that?
> Tried
> WriteToFile('test.ods', sfOpenDocument)
You need to add the unit which registers the open document format into
your uses clause.
uses fpsopendocument;
for OOXML:
uses xlsxooxml;
Actually there is documentation. In subversion there is a chm file
with a description of the API.
I think I will be writing my next Toolbox article about fpspreadsheet,
so I will take this opportunity to improve it's wiki page.
I may also improve one of the formats, not sure yet which one ...
th
Brad Campbell wrote:
G'day all,
I've been having a play with simpleipc.pp for trying to do
cross-platform single instance detection.
Ordinarily it behaves perfectly, but I just noticed on Linux that it
all comes crashing down if the server application crashes without
removing the pipe.
I
Can someone explain the new FPC source layout?
I find out so far:
In rtl/inc/systemh.inc there is
{$ifndef FPC_HAS_FEATURE_SUPPORT}
...
{$define FPC_HAS_FEATURE_CLASSES}
...
{$ENDIF}
Because FPC 2.3.1 defines FPC_HAS_FEATURE_SUPPORT the above is never
executed and therefore FPC_HAS_FEATURE_CLASS
Don't see my response to the list..
Resending.. and updating..
completely obsolete, and I just kept it in the website because I still
haven't written docs for the new version. I would recommend against
using it.
Gotcha.
In which operating system did you run it? Excel 5 needs the generatio
I just updated the wiki page, added the API reference file, added a
proper example, status information
And commited some small improvements in the wiki
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://li
Felipe Monteiro de Carvalho writes:
completely obsolete, and I just kept it in the website because I still
haven't written docs for the new version. I would recommend against
using it.
Gotcha.
In which operating system did you run it? Excel 5 needs the generation
of a OLE documented.
Ope
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
14 matches
Mail list logo
