| Product | Graphic System Layer |
| Type | changed |
| Title | Changes to Resource handling |
| Posted by | [EMAIL PROTECTED] |
| Affected | ,all using resources |
| Effective from | CWS res32bit |
API/ BASIC [ ]
Configuration [ ]
File format change [ ]
Help/ Guide [ ]
Performance test [ ]
Translation [ ]
UI relevant [ ]
Description
For language pack handling the Resource system was changed in CWS
res32bit.
- Resources were freed of a lot of 16bit constraints (which are now 32
bit constraints :-) ). Resources can grow larger than 64K now (which
already happened in OOo1.1 for Thai and Kannada localizations and led
to a crash there). Resource IDs also are 32 bit wide now. Resource
files of earlier versions will be incompatible to versions after
integration of CWS res32bit; also the new resource files are around
50% larger than the old files (small wonder since many former 16bit
fields are now 32bit).
- A resource fallback has been established; if a resource cannot be
found in a resource file, then the same global or local resource is
searched for in fall back languages (as detailed in the spec; fallback
to nonspecialized locales, then to english). If all fallbacks fail,
the resource will be faked by an buffer set to all zero; strings will
be initialized to "missing resource" in nonpro versions to notify
about the problem. Also, in nonpro versions all fallbacks and missing
resources will be asserted as this should not happen in an office
installation. The feature is only relevant for language packs, which
may not be complete if compiled for a different patch level.
- the ResMgr implementation does not depend implicitly on the
SolarMutex anymore; it is protected by its own mutex. This does not
mean that you should access the same ResMgr instance out of different
threads; the ResMgr is a stateful object and even though its access is
now thread safe, if you access it concurrently the results will be
nonsense. Also still valid (even if some people may not have known) is
that all resources (Strings, Windows, Controls, ALL Resources) have to
be destroyed before the ResMgr they came from is deleted.
- the search mechanism for resource files was changed; resources now
are searched for relative to the tools library in a subdirectory
"resource" (which happens to be at the same place where they are now:
at <office>/program/resource) The old feature of having an implicit
resource file for the application (e.g. soffice.res for soffice) was
removed since there are no more customers.
Specification URL http://specs.openoffice.org/g11n/lang_pax/language_packs.sxw
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
