Header and footer sections aren't being displayed on pt.wikisource.Maybe it's due to local scripts?On Wed, Dec 11, 2013 at 12:52 AM, billinghurst <billinghurst@gmail.com> wrote:
Gday Tpt,
I would like to thank you for all the work that you have been doing to
firstly convert the ProofreaPage extension away from the javascript
methodology, into the new schema. Then all the time that you have spent
bug fixing this past week. It probably sounds as though we are complaining
at times with raising issues, but to let you know personally that I think
that the work that you have been doing for the editing community, and then
for the reading community, is magnificent.
So that big thank you to you, and to those who have helped problem solve
this past week. Really appreciated.
Regards Billinghurst
On Tue, 10 Dec 2013 21:34:09 +0100, Thomas Tanon <thomaspt@hotmail.fr>
wrote:
> Hi!
>
> Some improvements and bug corrections have been deployed some minutes
ago
> as part of MediaWiki 1.23wmf6:
>
> Here is a list of fixed issues:
> * A JavaScript fatal error in Page: pages editing interface is solved
for
> Internet Explorer 8 or less and old Safari versions.
> * Mediawiki:proofreadpage_default_header and
> Mediawiki:proofreadpage_default_footer and text layer extraction now
works
> for Page: pages without index.
> * It is possible again to zoom in on mouse scroll.
> * The level change summary tag is now added when you click on the level
> selector (it’s what was done before the new Page: pages editing
interface
> deployment)
>
> Here is the remaining known issues (thanks to report ones that haven’t
> been listed here):
> * Fatal error on submit for a very few pages (a correction is on review)
> * the issue with gadget that Aubrey have reported here (I think that the
> solution is more on the gadget side that on the extension one)
> * It isn't possible to edit only the body of a page throw the API
> * The body content editing area doesn’t fit the scan height in vertical
> editing mode. I’m looking for a clean way to fix this problem.
> * The tab order in Page: pages editing interface is strange. A
correction
> for it is ready and will be deployed soon.
>
> Thomas
>
> Le 6 déc. 2013 à 23:53, Alex Brollo <alex.brollo@gmail.com> a écrit :
>
>> Thanks Thomas but.... I can't write php, just a little of python and
>> javascript.
>> But more or less I can read it (if statements are simple) , thanks for
>> link.
>>
>> Alex
>>
>>
>> 2013/12/6 Thomas Tanon <thomaspt@hotmail.fr>
>> The trim final routine is done automatically by the Wikitext content
>> representation. So, it have been very easy to implement. If you are
>> interested, here is the internal representation of a Page: page:
>>
https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FProofreadPage.git/8435e3855decbebc809280edffc9013b38b1f349/includes%2Fpage%2FProofreadPageContent.php
>> About automatic addition of the references tag, it’s a good idea. Feel
>> free to hack the extension (you are really invited to do so :-)) or to
>> fill a bug on bugzilla.
>> Thomas
>>
>> Le 6 déc. 2013 à 14:28, Alex Brollo <alex.brollo@gmail.com> a écrit :
>>
>>>> Hi!
>>>> No, there isn’t any doc about it. The Proofread Page doc is very
messy
>>>> and work on documentation is something really needed (it’s something
>>>> that any advanced editor of Wikisource can do).
>>>> # yes the bottom of nsPage body is trimmed (it’s normal normalisation
>>>> of wikitext content). If it breaks pages we can disable this
>>>> normalisation.
>>>> # you can add a default footer content in Mediawiki:proofread
>>>> page_default_footer (it doesn’t works currently because of a bug but
it
>>>> should be fixed soon (in the worst case at next Tuesday deployment)).
>>>> If you want to customize this value for a specific index, just add a
>>>> new field called 'Footer’ (the ID is important) in
>>>> MediaWiki:Proofreadpage_index_data_config with header:true.
>>>> en.wikisource use this feature.
>>>> # basically yes
>>>> # yes you have to if you use the action=edit API. I’m working on an
>>>> other API action that will allow to edit only the body and/or the
>>>> proofreading level (and that will be used also by the VisualEditor
when
>>>> it’ll be integrated)
>>>
>>> by Thomas
>>>
>>> Thanks for details; usually we are learning by "try and learn" and
>>> explicit details like those you give save hours of tries!
>>>
>>> # trimming bottom of the page: IMHO it's an excellent idea. The simple
>>> trick to add (manually or by a script launched at onSubmit event) a
>>> tl|nop at the bottom of the page when needed to force the closure of a
>>> paragraph at the bottom of the page and saves many transclusion
issues.
>>> # in the meantime, since we have to activate such a "final cleanup
>>> routine", it would be easy to "take a look" to body text and to add a
>>> references tag (after a new line) into the footer only when needed
(t.i.
>>> when text contains a ref tag or a template building a ref tag - an
>>> infrequent case.
>>> # I only use wikipedia.Page .put() method to edit pages by bot, I
don't
>>> know if it uses API action=edit, but anyone writing by itself scripts
to
>>> edit nsPage is used to test carefully the header-body-footer stuff so
>>> that here some try-and-learn will clarify the matter.
>>>
>>> I'm going to copy-and-paste your message.... as soon as this
>>> unavoidable "bug explosion" will rest, I've many other questions for
>>> you.... but not now. :-)
>>>
>>> Thanks again.
>>>
>>> Alex
>>>
_______________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l
_______________________________________________
Wikisource-l mailing list
Wikisource-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikisource-l