To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92708





------- Additional comments from [EMAIL PROTECTED] Tue Aug 12 14:02:42 +0000 
2008 -------
Here I present some sample warnings and discuss them.

ICE03   WARNING String overflow (greater than length permitted in column); 
Table:
File, Column: Component_, Key(s): statusbar5.xml

ICE03   WARNING String overflow (greater than length permitted in column); 
Table:
FeatureComponents, Column: Component_, Key(s):
gm_o_jf_Palm_Aportisdoc.g_f_registry_spool_oo_td_palm_filters_xcu__share_registry_modules_o_o_td_filter

ICE03   WARNING String overflow (greater than length permitted in column); 
Table:
Registry, Column: Registry, Key(s):
g_r_software_manufacturer_productname_productversion_capabilities_applicationdescription

ICE03   WARNING String overflow (greater than length permitted in column); 
Table:
Component, Column: Component, Key(s):
g_f_share_c_sc_uiconfig_zip__share_c_soffice_cfg_modules_schart_statusbar

These are caused by many component names still being too long. Even more radical
abbreviation is needed in get_file_component_name() in
solenv/bin/modules/installe/windows/file.pm. Probably it would make sense to
just use underscore-prefixed MD5 hashes as component names, instead of trying to
use "human readable" component names. I think many installer-builders do that.

ICE33   WARNING Reg key g_r_bau is used in an unsupported way. ProgId should be
registered via the ProgId table. This entry may overwrite a value created
through that table.

ICE33   WARNING Reg key g_r_openoffice_calcdocument_1_clsid is used in an
unsupported way. ProgId - CLSID associations should be registered via the ProgId
and Class tables. This entry may overwrite a value created through those tables.

ICE33   WARNING Reg key g_r_office_extension_curver is used in an unsupported 
way.
Version Independent ProgId should be registered via the ProgId table. This entry
may overwrite a value created through that table.

ICE33   WARNING Reg key g_r_office_extension_1_defaulticon is used in an
unsupported way. ProgId - Icon associations should be registered via the ProgId
and Icon tables. This entry may overwrite a value created through those tables.

ICE33   WARNING Reg key g_r_office_extension_1_shell is used in an unsupported
way. Shell extension verbs info should be registered via the Verb table. This
entry may overwrite a value created through that table.

ICE33   WARNING Reg key g_r_bau is used in an unsupported way. Extensions should
be registered via the Extension table. This entry may overwrite a value created
through that table.

ICE33   WARNING Reg key g_r_c_30a2652a_ddf7_45e7_aca6_3eab26fc8a4e_ is used in 
an
unsupported way. CLSIDs should be registered via the Class table. This entry may
overwrite a value created through that table.

ICE33   WARNING Reg key g_r_c_30a2652a_ddf7_45e7_aca6_3eab26fc8a4e_defaulticon 
is
used in an unsupported way. CLSID - Icon associations should be registered via
the Class and Icon tables. This entry may overwrite a value created through
those tables.

ICE33   WARNING Reg key 
g_r_c_30a2652a_ddf7_45e7_aca6_3eab26fc8a4e_inprochandler32
is used in an unsupported way. CLSID DefInprocHandler should be registered via
the Class table. This entry may overwrite a value created through that table.

ICE33   WARNING Reg key 
g_r_c_087b3ae3_e237_4467_b8db_5a38ab959ac9_inprocserver32
is used in an unsupported way. CLSID contexts should be registered via the Class
table. This entry may overwrite a value created through that table.

ICE33   WARNING Reg key g_r_c_30a2652a_ddf7_45e7_aca6_3eab26fc8a4e_progid is 
used
in an unsupported way. CLSID - ProgId associations should be registered via the
Class and ProgId tables. This entry may overwrite a value created through those
tables.

ICE33   WARNING Reg key g_r_odb_mime_database is used in an unsupported way. 
MIME
info should be registered via the MIME table. This entry may overwrite a value
created through that table.

These warnings are more or less self-explanatory I think. Presumably the current
way the installer pokes directly into the Registry works fine, but it would be
cleaner to use the higher levels of abstraction offered by the ProgId, Class,
Icon, Verb, Extension and MIME tables.

ICE57   WARNING Component 'g_f_exe_sbase__program' has both per-user and
per-machine data with an HKCU Registry KeyPath.

ICE57   WARNING Component 'g_m_root_registry' has a registry entry that can be
either per-user or per-machine and a per-machine KeyPath.

These warnings I don't really understand yet...

ICE60   WARNING The file soffice.exe is not a Font, and its version is not a
companion file reference. It should have a language specified in the Language
column.

This is a pretty clear message, at first sight. The Language column needs to be
populated.

But... another question is then whether the values in the Language column need
to match the language in the executable's version resource block? Argh, I hate
Windows Installer... this is just so typical, that the same information (Version
and Language) can be duplicated in the File table and in the (executable) file
itself, and it is very unclear whether this is OK (and whether they then must
match exactly or not), or whether it is enough that the executables contain
version resource blocks and it in fact is wrong to then also give them in the
File table...

ICE60   WARNING The file alignmentbar3.xml is not a Font, and its version is 
not a
companion file reference. It should have a language specified in the Language
column.

For non-executable files, though, the File table is the only place where the
language can be specified, so it probably should be done. I guess even just a
zero would make the validator satisfied?

ICE61   WARNING This product should remove only older versions of itself. The
Maximum version is not less than the current product. (36.0.0 2.4.9310)

Hmm, what is that 36.0.0 version in the Upgrade table?

ICE86   WARNING Property `AdminUser` found in column 
`LaunchCondition`.`Condition`
in row 'AdminUser'. `Privileged` property is often more appropriate.

Maybe so then. I doubt this is essential?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
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]

Reply via email to