[Lazarus] TAChart Localization

[Werner Pamler]

Am 17.12.2015 um 12:09 schrieb Maxim Ganetsky:
>
> 17.12.2015 04:19, Werner Pamler пишет:
>> Am 17.12.2015 um 01:01 schrieb Maxim Ganetsky:
>>> 16.12.2015 17:34, Werner Pamler пишет:
>>>> Another question related: Is it possible to find the address of a
>>>> resource string in the internal resource string table by using its hash
>>>> value? This would allow me to go back to the old calling convention
>>>> which had a "string" in the RegisterXXXX procedure (instead of a pointer
>>>> to a string): In this procedure I could calculate the hash value of the
>>>> passed untranslated resource string, store it and use it later to
>>>> retrieve the translated string from the tables.
>>> See here for the list of available resource string functions:
>>>
>>> http://www.freepascal.org/docs-html/3.0.0/prog/progse40.html#x229-2420009.3
>>>
>>>
>> Thanks. I know this page, but my fpc-trunk does not find these
>> functions, even if I "search in files" of the entire fpc folder, they do
>> not show up. They do exist in the objpas of fpc3.0.0, but only enclosed
>> by a define "RESSTRSECTIONS" which is not active, and I can't make
>> TAChart depend on a non-standard define of fpc...
> FPC changed its format of resource strings from RST to RSJ. So
> documentation seems to be outdated in this regard. Maybe resource string
> functions were changed too.
>
> In any case I think that it is not worth all the hassle. The current
> implementation is basically OK IMO.
>
I added an overloaded version of each registration procedure which 
accepts a string as parameter like in the old version (of course, this 
one will not be translated). Therefore, TAChart is backward-compatible 
again. All related changes were added to the list for merging to RC2.

Thank you for the Russian translation.