Re: Re: Move legacy info for install/windows
| From: | Peter Cowburn | Date: | Thu, 07 Apr 2016 13:49:26 +0000 |
| Subject: | Re: Re: Move legacy info for install/windows | ||
| References: | 1 2 3 4 5 6 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386092@lists.php.net to get a copy of this message | ||
On 5 April 2016 at 06:21, Pasindu De Silva <ppasindud@gmail.com> wrote:
> HI Matt
> Did you refer http://doc.php.net/tutorial/
>
Hi all. Christoph moved the files today (r338941), so the "install/windows"
directory is freed up for new files. What is your plan moving forward?
Currently the docs will build such that nothing has changed (since the
xml:id's weren't touched, hyperlinks aren't broken), which is good. Do you
want to work in that directory for a while, until such a point that you're
ready to "flip the switch" and have your install docs published? Or do you
want http://php.net/manual/en/install.windows.php
to point to your
documentation? I'd advise against the latter unless you're already a
significant way through the process.
Keep us posted.
>
>
> +1
>
> On Tue, Apr 5, 2016 at 1:09 PM, Matt Ficken <themattficken@gmail.com>
> wrote:
>
>> In the PHP Online Docbook Editor, I tried to move the old files to
>> install/windows/legacy, which it appears to do, the file tree is updated
>> and there is no error message. However, reloading the tree listing of
>> files, the changes aren't made.
>>
>> I have created a new install/windows/index.xml. However, its currently
>> modifying the existing index.xml which I don't want to do. I want to move
>> the existing index.xml to legacy.
>>
>>
>> Would someone with the karma or access to the repository move those files
>> to install/windows/legacy?
>>
>> I have a few more changes I want to add to index.xml and I want to add
>> Troubleshooting and Recommended Practices pages, but I don't want to do
>> that until that is cleared up (and I do think its worth all this trouble to
>> keep that legacy info).
>>
>>
>> What causes someone to run the PHD docbook rendering system? and release
>> the updated html files onto php.net?
>>
>> I can't find information about that. For other parts of php.net, I can
>> just commit to git repository and wait 20 minutes. For win32/install.txt, I
>> can just update php-src.git repository.
>>
>> The few changes I want to make, and changes to Troubleshooting page over
>> time, what is involved in getting those changes onto php.net?
>>
>>
>> Regards
>> -M
>>
>>
>>
>>
>> On Fri, Mar 25, 2016 at 3:16 AM, Christoph Becker <cmbecker69@gmx.de>
>> wrote:
>>
>>> On 24.03.2016 at 21:17, Matt Ficken wrote:
>>>
>>> > I can update win32/install.txt in php-src. Good point.
>>> >
>>> > Good point about other languages too. Same outdated info for
>>> > install/windows is in all languages and eventually should be updated.
>>> >
>>> > I can't update that document in all languages(just en, and maybe es or
>>> fr).
>>> >
>>> > For now, can we move just the
en copy of
>>> > install/windows to
>>> > install/windows/legacy ? Then I can update that document
>>> >
>>> > Then, when others are ready to do the translation, they can update it
>>> for
>>> > de, ru, etc...
>>>
>>> I'm note sure whether this is a good idea. Moving the en docs to a new
>>> folder and updating the old docs in place will cause additional
>>> translation work, if the translators are not aware of this change. The
>>> doc system[1] will report the install/windows/*.xml docs to be
>>> out-dated, so a translator would have to update them (what has to be
>>> done anyway – no problem here). However, the doc system will also tag
>>> the install/windows/legacy/*.xml docs as new files, and a translator
>>> might translate them *anew* (not being aware that those files only had
>>> moved).
>>>
>>> The best solution with regard to translations would be to *copy* all
>>> files under install/windows/ to the new folder. This way only those
>>> files that really will change will be tagged as being out-dated in the
>>> other languages.
>>>
>>> Anyhow, I have created en/install/windows/legacy/ right now.
>>>
>>> [1] <http://doc.php.net/> and
>>> <https://edit.php.net/>
>>>
>>> --
>>> Christoph M. Becker
>>>
>>
>>
>
>
> --
>
> *Pasindu De Silva**ppasindud@gmail.com <ppasindud@gmail.com>*
>