Hi Uwe,
On 15 Jul 2007, at 16:14, Uwe Altmann wrote:
Hi Shaun, *
Thanks for the thoroughly reading - changed most of that.
You'll find a recent version of Resulting INTEL, PPC an Windows html
readme-File attatched (I finally found out how to process that in
jEdit).
${PRODUCTNAME} ${PRODUCTVERSION} are not replaced by XSLT-filtering
but
otherwise - this will be done while building anyhow.
I've found another one:
If you experience OpenOffice.org startup problems the reason is in
most cases a X11 installation missing. Please refer to the MAC
Porting FAQ http://porting.openoffice.org/mac/faq/index.html
should be changed to
If you experience OpenOffice.org startup problems the reason is in
most cases due to a missing X11 installation. Please refer to the Mac
Porting FAQ http://porting.openoffice.org/mac/faq/index.html
Please look out for necessary changes on that files. If these are
ok for
you, I'll attach the basic readme.xrm file to the issue so someone can
check it into cvs.
You'll find more in my comments to Shaun's mail
Shaun McDonald schrieb:
Great, can you please do a build of the module using aqua? We
need to
remove the X11 requirement, or to say
There is at the moment no variable defined in the dtd file to
distinguish between aqua and X11 version. To make this possible, there
has to be introduced a new variable or value in readme.dtd and also
some
adjustments in readme.xsl.
Relevant variables in readme.dtd are by now:
gui (all | UNX | WNT)
os (none | all | SOLARIS | LINUX | WNT | MACOSX)
cpuname (all | SPARC | INTEL | POWERPC)
Until now I use
os=MACOSX for the Mac-specific files and
cpuname=INTEL|POWERPC to distinguish between the two Mac Platforms.
I'll let someone else who knows more about the build process to
answer about this.
First we have to answer the question if there ever will be a parallel
release of X11 and Aqua other than testing builds. If we will have a
productive version of aqua and X11 at the same time, I'll introduce a
new value "AQUA" in "gui"-variable (assuming "UNX" means "X11" and
is by
now in use also for Mac X11 builds) and adapt the checks in
readme.xsl.
There are already preview releases of Aqua out, with X11 being the
stable release.
Maybe you could mark the X11 requirement as being only for the X11
version, or not required for the Aqua version, if we cannot do it
dynamically depending on the build.
But that implies also changing of building setup because these
variables
are read out of build environment for processing the XSLT filtering
while building! So the aqua build has to get a change from gui=UNX to
gui=AQUA if we proceed to make this distinction take place - an I
don't
know what that change will affect besides that!
(Maybe there is yet another environmental varible which flags aqua
builds?)
So we should check that very carefully and inform all of the aqua
builders in case we change that.
Surely there is already some form of way in the build environment to
determine whether X11 or Aqua is being built.
...
As all Macs already come with 800x600 resolution and 256 colours
already, I don't see why we cannot simply say:
"- Apple's X11 must be installed"
That's right - OK
Ideally use http://porting.openoffice.org/mac/faq/index.html instead
of http://porting.openoffice.org/mac/support.html
OK
Also "MAC-porting FAQ" to "Mac Porting FAQ"
OK
"You can install OpenOffice.org 2.3 alongside of an older version of
OpenOffice.org. If you later choose to deinstall the older
version of
OpenOffice.org, you must call the installation program of the newer
version and choose 'Repair'. This ensures that the new version is
correctly registered in your system."
is completely irrelevant for Mac OS X.
indeed. Applies oonly for Windows; changed flag to os=WNT
In "Please note that copy and paste via clipboard between
OpenOffice.org 1.x and OpenOffice.org 2.3 might not work in
OpenOffice.org format. If that happens, choose 'Edit - Paste
Special'
and choose a format other than OpenOffice.org, or open the
document in
OpenOffice.org 2.3 directly." shouldn't "OpenOffice.org 2.3" be
"OpenOffice.org 2.x"
this is "...${PRODUCTNAME} ${PRODUCTVERSION}..." - so because Eric
does
builds for 2.3., it's "2.3".
Is Gnome relevant for Mac OS X?
This is because this paragraph was flaged gui=UNX . I changed that to
os=LINUX (so Solaris users propably will no longer get this text
too :-)
Since "Changing the User Interface Font" is in there, why not add
"Removing the icons in menus".
I've created
http://porting.openoffice.org/mac/faq/hidemenuicons/index.html which
covers how to remove the menu icons.
I'd rather like to delete the whole "Changing the User Interface
Font"-section. Opinions?
Finally we will also need top update:
http://www.openoffice.org/welcome/readme.html
Indeed. But what to do with OS specific texts? Using a
"navigator.platform" - javascript switch will not be possible on
CollabNet afaik.
Javascript _can_ be used through the CollabNet framework. Maybe it
would be best to have one Readme for each platform.
Shaun
___________________________________________________________
Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
