Ok but if I found this number
and I divide it by 86400 then I convert it in date (since 01/01/1904) I obtain:
print datetime.datetime( 1904, 1, 1 ) + datetime.timedelta( seconds=3425616668 )
So I would say that looks similar.
this hour 08.11 is the real time or I have to add the +2 (timezone+DST ) of my zone?
It is impossible to tell that solely from the timestamp.
Judging by the article you linked I would say it looks like the timestamp represents a date and time value in the local timezone.
However if I need to know this for a case, I make sure to do a reference test.
"HFS time" or "HFS+ time" is a short hand of expressing the date and time format as used in the HFS file system. So it applies to the type of timestamp not the file system. The only relation to the file system is that the timestamps are used in it. Referring to them as MacTime or MacOSXtime would be even more ambiguous.
Note that in HFS+, there is exactly one timestamp that is in the local time zone -- the volume creation date stored in the volume header. It's in local time for backwards-compatibility reasons. All other timestamps are in UTC.
Again, the HFS in the name only indicates the origin of the timestamp you can find the same definition in:
indur for completeness also the information you refer to is in the same document:
The date and time the folder was created. See HFS Plus Dates for a description of the format. Again, the createDate of the Volume Header is NOT stored in GMT; it is local time. (Further, if the volume has an HFS wrapper, the creation date in the MDB should be the same as the createDate in the Volume Header).