Name the beast

From Apache OpenOffice Wiki
Revision as of 10:11, 10 December 2012 by Od (Talk | contribs)

Jump to: navigation, search



Purpose of this page is to document the work on Issue 121388 - Adapt naming "" --> "Apache OpenOffice".

Hopefully, it serves also the goal to have a guide how to "brand" your product based on the Apache OpenOffice project.

Usages of the name


'State of the art' usage of the name - 2012-11-23:

usage description comments examples value
name of the Apache project
  • fixed name of our Apache project
  • even fixed in derived products
  • About dialog: "... product based on Apache OpenOffice ..."
  • references to corresponding ASF trademark
  • in help content to name the project
  • see also Thesaurus::getServiceDisplayName
"Apache OpenOffice" - fixed until Apache OpenOffice project decides on a new name
BASISROOTNAME 1 3-layer-office: folder name of the "basis layer" under Windows IMPORTANT: no longer used --> remove it ""
UNIXBASISROOTNAME 1 3-layer-office: folder name of the "basis layer" under Linux/Unix orw: Should be changed to lower case, no space containing variant of the Apache project name, e.g. "apache_openoffice" ""
PRODUCTNAME 1 name of the product
  • Windows
    • in installation dialogs in window title and in text content
    • part of path for unpacked installation files
    • part of the default installation path and the default user profile path
    • part of the application names in the Windows Start Menu
    • part of shortcut name which is optionally placed on the users desktop
    • part of Windows registry entry " Service Manager (Ver 1.0)"
    • part of Windows registry entry " Property Handler"
    • part of Windows registry entry " Service Manager"
key in Windows registry orw's opinion: should be equal to product name
  • "HKEY_CURRENT_USER\\Software\\\\UNO\\InstallPath\\"
  • "HKEY_LOCAL_MACHINE\\Software\\\\UNO\\InstallPath\\"
part of XML namespace declarations orw's opinion: should not be adapted "" - fixed
part of Public Identifier of document type definitions (DTD) for internal used DTDs orw's opinion: should not be adapted, but name could be removed <!DOCTYPE statusbar:statusbar PUBLIC "-// OfficeDocument 1.0//EN" "statusbar.dtd"> ""
in module cli_ure  ?
  • [assembly:System.Reflection.AssemblyCompany( "" )]
  • --assembly-company ""
in module desktop as part of a version info for Windows  ? may be related to usage in module cli_ure
  • value "CompanyName", "\0"
in meta data about extensions certain XML elements contain the name
as part of website URLs in the help content orw: check the URLs, if still valid; adapt URLs "" - fixed
packaging process - *.idt files  ?
  • ""
in module ODK
  • part of Windows registry keys
  • part of 'hard-coded' directory paths
  • part of 'hard-coded' names
  • "HKEY_CURRENT_USER\\Software\\\\UNO\\InstallPath\\"
  • "/Applications/"
  • "${OOVERSION}_sdk"
  • ""
  • "$(PRODUCT_RELEASE)_sdk"

(1) found in /main/instsetoo_native/util/openoffice.lst

Personal tools