General „Is it a bug in FP/ Lazarus“ thread.

[JuhaManninen]

Oddly, sometimes BCDToInt(120) returns 78, and sometimes it returns 120

You mean it returns different result with the same parameter value?

I suppose you are talking about that:

Code: [Select]


TBcd  = packed record
   Precision: Byte;
   SignSpecialPlaces: Byte;
   Fraction: packed array [0..31] of Byte;
 end;

Right. I don't know how an integer can be casted to TBcd.
You could ask about it in FPC mailing list. Some of the clever FPC devels will know.

[CM630]

Oddly, sometimes BCDToInt(120) returns 78, and sometimes it returns 120

You mean it returns different result with the same parameter value?
 

Well, I just found why. There are two functions. BCDtoInt and BCDToInteger.

BCDToInt(120)= 78 //BCDToInt does not belong to FmtBCD
BCDToInteger (120)=120
The correct use for  BCDToInteger and BCDToString is

Code: [Select]

var
  MyBCD: tBCD;
begin
  MyBCD.Fraction[0]:=120; //hex 12
MyBCD.Precision:=2;  //app crashes if precision is not stated.
ShowMessage (IntToStr (BCDToInteger(MyBCD)));
  ShowMessage (BCDToStr(MyBCD));
end;Well, yet still it is not that simple. If a wrong byte is sent the app crashes (exception is generated). Practically either exceptions shall be handled, or the byte array shall be checked for BCD validity first.
And yet, no direction of conversion is given, so the byte array might need to be reversed, before conversion.
So there is a bug and it is just as you explained-  BCDToStr and BCDToInteger accept integer values, but they should not. And when they do, they return a wrong result.

[Timewarp]

Just noticed, maybe FPC rev26434 should be merged to fixes branch also

[marcov]

Maybe somebody did :-)

[CM630]

When using PO files to translate Lazarus apps, some strings are marked as FUZZY.
When PO files are used in native *nix apps, strings marked at FUZZY are a ignored.
But Lazarus does not ignore them, which is definitely a problem, because such strings often occur after automatic translation with for example PoEdit, whose automatic translations are often disastrous.
Example:

Code: [Select]

#: tfobject3d.rendering.caption
#, fuzzy
msgid "Rendering"
msgstr "Измазване"In an application, the displayed text shall be Rendering,  because the entry is marked as fuzzy, but in Lazarus apps  displayed text is  Измазване.
Maybe there is a way to tell Lazarus to ignore fuzzy strings, or that is simply a bug?

[BigChimp]

The logical solution would seem to fix the fuzzy translation IMO.
http://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html
"Fuzzy entries, even if they account for translated entries for most other purposes, usually call for revision by the translator."

[CM630]

Yes, the logical solution is that the translator should check fuzzy items, but the translated values shall not be displayed, until the fuzzy flag is removed. Our Gnome translation coordinator confirmed that this is how it should be.
I will report it as a bug.

[CM630]

Reported as bug 26527.