Hannes Magnusson escreveu:
On Dec 10, 2007 1:48 PM, Fernando Correa da Conceição
<[EMAIL PROTECTED]> wrote:
Philip Olson escreveu:
On Dec 9, 2007, at 11:52 AM, Hannes Magnusson wrote:
Hi all
I will be merging from the REF_STRUCT_DEV branch as of tomorrow and
would therefor like to request a total commit freeze to phpdoc/ as of
December 10th, 15:00 UTC (tomorrow, Monday) until "further notice".
Translations are not affected. In fact, translators are encouraged to
sync their translations while this freeze is in affect.
It is a lot of work (~180 extension references) so I don't expect the
docs to build or even validate for the next few days until everything
has been merged.
To make this process as painless as possible for our translators I'll
do my best to merge only one extension at a time and taking notes of
any "weirdness" that may occur.
The biggest changes, as you should be aware of by now, are the
reference pages and renamed files (OO extensions).
There are virtually no content changes, only refactoring and minor
markup upgrades.
Note: Even after the merge _no_ translations will validate.
Unfortunately there is pretty much nothing we can do about that.
I am hoping to push out these changes onto phpweb somewhere around new
year, it would be great if most translations have been brought in sync
by that time.
Hello all,
Hannes, have fun doing the merge! And again sorry translators... if
you have questions or desire help then please speak up.
If this is necessary. I have a simple request, if is possible. There is
a server that builds the docs using the phd. There is a way to make it
send a mail when a build fails? If this is possible, will be good, as we
will know that some change breaks the build and we can try to fix it.
The build fails, guaranteed, if the translation is not up2date with
the reference.xml split due to duplicated IDs.
These duplicated IDs are caused by the new "root/container" file,
book.xml (since all extensions are now <book>s), which includes a
setup.xml <chapter> file (containing the
installation+configuration+requirements <section>s).
Then the reference.xml file will be included which (unless it is
up2date) again defines the same sections, causing duplicated IDs.
Furthermore, the constant sections are now <chapter>s, not <section>s
and the document will therefor not validate.
So:
1. There is a new file, book.xml. This is the main file for each extension.
2. There is a new file, setup.xml. It have howto install and setup a
extension.
3. The reference.xml will contain samples and this kind about a
extension. The setup and what is an extension will go to the files above.
3. The file functions.xml is now entities.functions.xml. Is a simple
rename or there is other change?
Quick'n'dirty "build fix" is would therefore be "possible" by simply
removing all reference.xml and either upgrade the root elements in
constants.xml to <chapter> or simply remove the file.
We do send out automatic "build failure" mails[1], when the CHM
versions are built (once a week). However, since the English build
will be "messed up" for few days all translations will be too. There
is therefor no point in spamming the lists with these mails and have
they therfore been disabled for a while.
And a dumb question. This merge is from a branch to head. We keep
working(translating) on head, sure?
Indeed.
I duly recommend translators "blindly sync" their translations with
the English version right away. Then when everything appears to be in
sync try to validate it and fix any errors that come up.
-Hannes
[1] With the exception of the pt-br translation, as there was/is a
typo(I assume) in the mailinglist name causing the mail to be sent out
to non-existing-mailinglist.
I will look at this. The mailing list is not [EMAIL PROTECTED] ?
Fernando
I however get CC'ed all build failures and have have fixed them all
when they occur :]
