pdf files Code examples display incorrectly

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
Dokkie
Posts: 43
Joined: Wed 08 Oct 2008 21:58

pdf files Code examples display incorrectly

Post by Dokkie » Thu 09 Oct 2008 04:03

I'm using Acrobat Reader 9.12 to read the IBDAC pdf document
the code fragments shown in the pdf file do not display correctly.

Example included below:-
This is how it should display
procedure TForm1.Form1Create(Sender: TObject);
var
Master, Detail: TIBCQuery;
MasterSource: TDataSource;
begin
// create master dataset
Master := TIBCQuery.Create(Self);
Master.SQL.Text := 'SELECT * FROM Department';
// create detail dataset
Detail := TIBCQuery.Create(Self);
Detail.SQL.Text := 'SELECT * FROM Employee WHERE Dept_No = :Dept_No';
// connect detail dataset with master via TDataSource component
MasterSource := TDataSource.Create(Self);
MasterSource.DataSet := Master;
Detail.MasterSource := MasterSource;
// open master dataset and only then detail dataset
Master.Open;
Detail.Open;
end;

This is how my Adobe Acrobat Reader 9.12 displays it
procedure TForm1.Form1CreateESender: TObjectF;
var
Master, DetailW TIBCQuery;
MasterSourceW TDataSource;
begin
LL create master dataset
Master WZ TIBCQuery.CreateESelfF;
Master.SQL.Teñt WZ 'SELECT * FROM Department';
LL create detail dataset
Detail WZ TIBCQuery.CreateESelfF;
Detail.SQL.Teñt WZ 'SELECT * FROM Employee WeERE Dept|No Z WDept|No';
LL connect detail dataset with master via TDataSource component
MasterSource WZ TDataSource.CreateESelfF;
MasterSource.DataSet WZ Master;
Detail.MasterSource WZ MasterSource;
LL open master dataset and only then detail dataset
Master.Open;
Detail.Open;
end;

It appears if the encoding is different. However, if I copy the fragment to the clipboard and paste it to a notepad txt file the code fragment displays correctly.

Peter

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Thu 09 Oct 2008 08:35

This is a known problem. We are working on it.

Post Reply