many thanks for this proposal, erik! what i would love to be considered in
this context as well would be native language. to give an example:
i am speaking english and german. therefor i like to read the contents in
the original version, as long as it is available in this language. e.g.
wmch s
Hoi,
One reason to identify a language is to exclude it from being considered
part of another language. What follows is that a single string can and
should be identified as not being the base language for an article.
Functionally there are great reasons why you want to do this including
providing
On Tue, Apr 23, 2013 at 9:08 PM, Brian Wolff bawo...@gmail.com wrote:
Hi Brian,
We already have the page lang support.
What do you mean by that? AFAICT there's no existing designated place
in the schema for associating a content language with a specific page.
Thanks,
Erik
On Tue, Apr 23, 2013 at 10:00 PM, MZMcBride z...@mzmcbride.com wrote:
I'm not sure I'd call what you're proposing a major architectural
undertaking, though perhaps I'm defining a much narrower problem scope.
Yeah. A lot depends on whether or not we want language to be a first
class citizen at
On 2013-04-25 7:04 AM, Erik Moeller e...@wikimedia.org wrote:
On Tue, Apr 23, 2013 at 9:08 PM, Brian Wolff bawo...@gmail.com wrote:
Hi Brian,
We already have the page lang support.
What do you mean by that? AFAICT there's no existing designated place
in the schema for associating a
2013/4/25 Brian Wolff bawo...@gmail.com:
On 2013-04-25 7:04 AM, Erik Moeller e...@wikimedia.org wrote:
On Tue, Apr 23, 2013 at 9:08 PM, Brian Wolff bawo...@gmail.com wrote:
Hi Brian,
We already have the page lang support.
What do you mean by that? AFAICT there's no existing designated
On 2013-04-25 9:12 AM, Amir E. Aharoni amir.ahar...@mail.huji.ac.il
wrote:
2013/4/25 Brian Wolff bawo...@gmail.com:
On 2013-04-25 7:04 AM, Erik Moeller e...@wikimedia.org wrote:
On Tue, Apr 23, 2013 at 9:08 PM, Brian Wolff bawo...@gmail.com wrote:
Hi Brian,
We already have the
I also prefer not to add magic words in the first place. But if it is
added, it shouldn't change the way the other magic words are
interpreted; only magic words from the wiki's language should be used.
Or no magic words at all - just use a language picker at the editing page.
--
Amir Elisha
I think ContentHandler already theoretically has the ability to store
per-page language info, it's just not being used. (And of course it'd
have to be actually deployed somewhere else than Wikidata.) Unless I'm
missing something, this mostly needs an interface (which is not a
small undertaking by
Just to add, ContentHandler is deployed on all Wikimedia projects.
2013/4/24 Bartosz Dziewoński matma@gmail.com
I think ContentHandler already theoretically has the ability to store
per-page language info, it's just not being used. (And of course it'd
have to be actually deployed
On Wed, 24 Apr 2013 12:53:50 +0200, Denny Vrandečić
denny.vrande...@wikimedia.de wrote:
Just to add, ContentHandler is deployed on all Wikimedia projects.
But with $wgContentHandlerUseDB = false, so not really.
--
Matma Rex
___
Wikitech-l mailing
I've already tried both using page properties to store page content
language and modifying ContentHandler::getPageLanguage()[1]. In both
cases parser worked in a different language scope and didn't process
magic words written in a default wiki language (e.g. Russian
[[Категория:Test]] wouldn't
2013/4/24 Paul Selitskas p.selits...@gmail.com:
I've already tried both using page properties to store page content
language and modifying ContentHandler::getPageLanguage()[1]. In both
cases parser worked in a different language scope and didn't process
magic words written in a default wiki
On 24 April 2013 06:28, Amir E. Aharoni amir.ahar...@mail.huji.ac.il wrote:
2013/4/24 Paul Selitskas p.selits...@gmail.com:
I've already tried both using page properties to store page content
language and modifying ContentHandler::getPageLanguage()[1]. In both
cases parser worked in a
On 04/23/2013 11:29 PM, Erik Moeller wrote:
(Keeping in mind that some
pages would be multilingual and would need to be identified as such.)
If so, this seems like a major architectural undertaking that should
only be taken on as a partnership between domain experts (site and
platform
Hi folks,
I'd like to start a broader conversation about language support in MW
core, and the potential need to re-think some pretty fundamental
design decisions in MediaWiki if we want to move past the point of
diminishing returns in some language-related improvements.
In a nutshell, is it time
Erik Moeller wrote:
I'd like to start a broader conversation about language support in MW
core [...]
Mailing lists are good for conversation, but a lot of your e-mail was
insightful notes that I want to make sure don't get lost. I hope you'll
eventually put together an RFC
17 matches
Mail list logo
