Re: [Wikitech-l] Wikitech-l Digest, Vol 90, Issue 48

2011-01-23 Thread HW
Reply to message 7

Seems it can use anywhere but it not support Chinese at least. It do not 
support 
the http://en.wikipedia.org/wiki/Chinese_input_methods_for_computers . May it 
be 
fix? 

HW


寄件人﹕ "wikitech-l-requ...@lists.wikimedia.org" 

收件人﹕ wikitech-l@lists.wikimedia.org
傳送日期﹕ 2011/1/23 (日) 9:40:33 AM
主題: Wikitech-l Digest, Vol 90, Issue 48

Send Wikitech-l mailing list submissions to
wikitech-l@lists.wikimedia.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
or, via email, send a message with subject or body 'help' to
wikitech-l-requ...@lists.wikimedia.org

You can reach the person managing the list at
wikitech-l-ow...@lists.wikimedia.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wikitech-l digest..."


Today's Topics:

   1. Re: File licensing information support (Bryan Tong Minh)
   2. Re: File licensing information support (Platonides)
   3. Re: Announcing OpenStackManager extension (Platonides)
   4. Re: File licensing information support (Krinkle)
   5. Re: File licensing information support (Platonides)
   6. Re: File licensing information support (Magnus Manske)
   7. Re: WYSIFTW status (Magnus Manske)
   8. Re: Farewell JSMin, Hello JavaScriptDistiller! (Maciej Jaros)


--

Message: 1
Date: Sat, 22 Jan 2011 20:15:10 +0100
From: Bryan Tong Minh 
Subject: Re: [Wikitech-l] File licensing information support
To: Wikimedia developers 
Message-ID:

Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jan 21, 2011 at 3:36 AM, Michael Dale  wrote:
> On 01/20/2011 05:00 PM, Platonides wrote:
>> I would have probably gone by the page_props route, passing the metadata
>> from the wikitext to the tables via a parser function.
>
> I would also say its probably best to pass metadata from the wikitext to
> the tables via a parser function. ?Similar to categories, and all other
> "user edited" metadata. This has the disadvantage that its not easy 'as
> easy' to edit via structured api entry point, ?but has the advantage of
> working well with all the existing tools, templates and versioning.
>
This is actually the biggest decision that has been made, the rest is
mostly implementation details. (Please note that I'm not presenting
you with a fait accompli, it is of course still possible to change
this)

Handling metadata separately from wikitext provides two main
advantages: it is much more user friendly, and it allows us to
properly validate and parse data.

Having a clear separate input text field "Author: " is much more
user friendly {{#fileauthor:}}, which is so to say, a type of obscure
MediaWiki jargon. I know that we could probably hide it behind a
template, but that is still not as friendly as a separate field. I
keep on hearing that especially for newbies, a big blob of wikitext is
plain scary. We regulars may be able to quickly parse the structure in
{{Information}}, but for newbies this is certainly not so clear.
We actually see that from the community there is a demand for
separating the meta data from the wikitext -- this is after all why
they implemented the uselang= hacked upload form with a separate text
box for every meta field.

Also, a separate field allows MediaWiki to understand what a certain
input really means. {{#fileauthor:[[User:Bryan]]}} means nothing to
MediaWiki or re-users, but "Author: Bryan___ [checkbox] This is a
Commons username" can be parsed by MediaWiki to mean something. It
also allows us to mass change for example the author. If I want to
change my attribution from "Bryan" to "Bryan Tong Minh", I would need
to edit the wikitext of every single upload, whereas in the new system
I go to Special:AuthorManager and change the attribution.

> Similar to categories, and all other"user edited" metadata.
Categories is a good example of why metadata does not belong in the
wikitext. If you have ever tried renaming a category... you need to
edit every page in the category and rename it in the wikitext. Commons
is running multiple bots to handle category rename requests.

All these advantage outweigh the pain of migration (which could
presumably be handled by bots) in my opinion.


Best regards,
Bryan



--

Message: 2
Date: Sat, 22 Jan 2011 21:04:05 +0100
From: Platonides 
Subject: Re: [Wikitech-l] File licensing information support
To: wikitech-l@lists.wikimedia.org
Message-ID: 
Content-Type: text/plain; charset=ISO-8859-1

An internally handled parser function doesn't conflict with showing it
as a textbox.

We could for instance store it as a hidden page prefix.

Data stored in the text blob:
"Author: [[Author:Bryan]]
License: GPL
---
{{Information| Thi

[Wikitech-l] Old edit toolbar cannot use anymore?

2011-02-06 Thread HW
Dear all,

In Chinese Wikipedia, some user said that he do not want to use Vector skin 
anymore so he change the skin back to MonoBook. However, the edit toolbar is 
still the new editor. I want to ask that is it now possible to use the 
MonoBook's edit toolbar but not the Vector's Wikieditor?

Thanks.

HW
User from zhwp



  
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[Wikitech-l] Using old edit toolbar

2011-02-06 Thread HW
It is fixed at IRC channel, thank you.

HW


  
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[Wikitech-l] About LQT - on hold?

2011-05-29 Thread HW
Dear all,
 
As of a member of Chinese Wikipedia community, we have submitted a bug 
https://bugzilla.wikimedia.org/show_bug.cgi?id=29114 on requestion for adding 
LQT to Chinese Wikipedia. However, it seems that it is on hold. Due to a large 
amount of comment on Chinese Wikipedia Village Pump, we need it as soon as 
possible. When will it be enable? Or, need to wait for central action?
 
HW
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l