Apache OpenOffice (AOO) Bugzilla – Issue 60840
Aqua port creator codes
Last modified: 2008-09-19 21:58:51 UTC
I've registered the following creator codes with Apple. These should be used ONLY for the Aqua port of OpenOffice.org. I picked a relatively simple scheme, OOO + major release number. The creator code doesn't actually relate to the product name, but I picked these as an easy-to-remember set of codes. (Creator codes are 4 position alpha(upper)-numeric) OOO2 OOO3 OOO4 OOO5 OOO6 OOO7 OOO8 OOO9
Apple has completed the registration for the following... Application Signatures: OOO2 (Hex) 4F4F4F32 OOO3 (Hex) 4F4F4F33 OOO4 (Hex) 4F4F4F34 OOO5 (Hex) 4F4F4F35 OOO6 (Hex) 4F4F4F36 OOO7 (Hex) 4F4F4F37 OOO8 (Hex) 4F4F4F38 OOO9 (Hex) 4F4F4F39
ericb->dnedrow Have you some documented links about creator codes ?
Here are the rest of the creator codes that have been registered. Application: OpenOffice.org Base Application Signatures: OOB2 (Hex) 4F4F4232 OOB3 (Hex) 4F4F4233 OOB4 (Hex) 4F4F4234 OOB5 (Hex) 4F4F4235 OOB6 (Hex) 4F4F4236 OOB7 (Hex) 4F4F4237 OOB8 (Hex) 4F4F4238 OOB9 (Hex) 4F4F4239 Application: OpenOffice.org Draw Application Signatures: OOD2 (Hex) 4F4F4432 OOD3 (Hex) 4F4F4433 OOD4 (Hex) 4F4F4434 OOD5 (Hex) 4F4F4435 OOD6 (Hex) 4F4F4436 OOD7 (Hex) 4F4F4437 OOD8 (Hex) 4F4F4438 OOD9 (Hex) 4F4F4439 Application: OpenOffice.org Impress Application Signatures: OOI2 (Hex) 4F4F4932 OOI3 (Hex) 4F4F4933 OOI4 (Hex) 4F4F4934 OOI5 (Hex) 4F4F4935 OOI6 (Hex) 4F4F4936 OOI7 (Hex) 4F4F4937 OOI8 (Hex) 4F4F4938 OOI9 (Hex) 4F4F4939 Application: OpenOffice.org Writer Application Signatures: OOW2 (Hex) 4F4F5732 OOW3 (Hex) 4F4F5733 OOW4 (Hex) 4F4F5734 OOW5 (Hex) 4F4F5735 OOW6 (Hex) 4F4F5736 OOW7 (Hex) 4F4F5737 OOW8 (Hex) 4F4F5738 OOW9 (Hex) 4F4F5739 Application: OpenOffice.Org Calc Application Signatures: OOC2 (Hex) 4F4F4332 OOC3 (Hex) 4F4F4333 OOC4 (Hex) 4F4F4334 OOC5 (Hex) 4F4F4335 OOC6 (Hex) 4F4F4336 OOC7 (Hex) 4F4F4337 OOC8 (Hex) 4F4F4338 OOC9 (Hex) 4F4F4339
Creator codes are used in a couple of ways, the two most important being... Indicating which application is responsible for a particular file. Assigning a creator code to a document allows the correct application to open it even if the document does not have an extension. This is more "Mac-like", since file extensions mean virtually nothing to a Mac user. The second item is .Mac syncing, which requires unique creator codes. So, if we want to provide .Mac syncing of OOo prefs for the Aqua version, we'll need the creator code for OOOn. Another feature that creator codes enable is the ability to use the Finder to search for, e.g., *.html files that were created with Writer. There are other examples, but these are the most obvious.
Thanks for registering these codes ! Why do you suggest to use them for the Aqua port only ? If for good reasons, shouldn't we register some for the X11 port as well (see #i60095#).
First of all thanks, David. Actually, I registered the following codes two weeks ago: OOo2 (Hex) 4F4F6F32 OOo3 (Hex) 4F4F6F33 So maybe we can use those for the X11 version?!
I have attached a patch that changes the creator code to OOO2dplt for the aqua port to #60095#.
set target
To my understanding, the creator codes are already integrated in the OOo builds, for both X11 and Aqua builds
.
ericb->mox Why reassign ?
Closing
Just to have them at one place; Application: OpenOffice.org VCL TestTool got the following CCs: ASCII: OOT2 HEX: 4F4F5432 ASCII: OOT3 HEX: 4F4F5433 ASCII: OOT4 HEX: 4F4F5434 ASCII: OOT5 HEX: 4F4F5435 ASCII: OOT6 HEX: 4F4F5436 ASCII: OOT7 HEX: 4F4F5437 ASCII: OOT8 HEX: 4F4F5438 ASCII: OOT9 HEX: 4F4F5439
add me on CC
@fheckl Florian, can you please explain me how to use such value ? ( e.g. on IRC ) I have something working, but what is really expected is a bit unclear to me :/