@Nahum: What is "Table interface"? Can you please link a page using it,
just to take a look?

Alex

2015-12-01 1:44 GMT+01:00 Nahum Wengrov <novar...@gmail.com>:

> Multilingual texts are not a priority (35 people in the conference didn't
>> even mention them, I think).
>
>
> Multilingual texts can either be treated on the ws of its main language.
> In case of a translation, that would most likely be the destination
> language. We have examples of English and Russian texts translated into
> Hebrew and placed side-by-side using Table  interface in he.ws. In other
> cases the language site could be decided arbitrarily by the original
> contributor (perhaps according to where he feels more comfortable, either
> for his personal native language or for the specific community happening to
> be there), etc. The current form enables flexibility which would be
> unavialble on a single multilingual site and is most likely to drive
> possible contributors away. Just my 10 cents, based by my own personal
> experfience as a veteran he.ws (and former en.wp and he.wp) active editor.
>
> On Mon, Nov 30, 2015 at 11:56 AM, Andrea Zanni <zanni.andre...@gmail.com>
> wrote:
>
>> Maybe it's me,
>> but I think that we are missing the real, huge point: *we are not ready
>> for this*.
>>
>> I mean, we, as a community: in the few days in Vienna, we discovered how
>> many problems each Wikisource and community has, and that was the first
>> time we had the chance to meet and talk (at that scale).
>> Yes, being all in the same place would maybe shorten the distance within
>> the international community, but it would be an enormous challenge for the
>> amount of software tweakings (gadgets, css, proofread page, layouts,
>> everything), and it would be a real, literal "babel" of languages.
>> And, remember, without the support of any engineer at the WMF! :-)
>>
>> So, please, keep our feet on the ground. Xanadu was the perfect model for
>> a digital library, and after 50 years is still not real. Our problem, in
>> Wikisource, is that each community has created little, complicated gadgets
>> and templates to do amazing things, but the result is that we are overly
>> complicated.
>> We need to simplify things, be better for our readers and beginners, new
>> editors.
>> Our strength is the community, above everything else.
>> That we have to nurture and care about.
>>
>> As much as I love the idea of a unique, Babelian (Borges style) digital
>> library, it won't happen if before we don't fix much more urgent things.
>> Multilingual texts are not a priority (35 people in the conference didn't
>> even mention them, I think).
>>
>> Aubrey
>>
>>
>>
>> On Mon, Nov 30, 2015 at 10:44 AM, Federico Leva (Nemo) <
>> nemow...@gmail.com> wrote:
>>
>>> Ankry, 29/11/2015 23:22:
>>>
>>>> >
>>>>> >What about two multilanguage Wikisources? One for RTL languages,
>>>>> another
>>>>> >for LTR languages.
>>>>>
>>>> ... and the third for some Asian scripts:
>>>> https://phabricator.wikimedia.org/T60729  ?
>>>>
>>>> And maybe a separate one for French:
>>>> https://phabricator.wikimedia.org/T14752  ?
>>>>
>>>> If you dig deeper then more such issues.
>>>>
>>>
>>> Again, this problem is already solved: content language can be decided
>>> per page. As usual, this is blocked on silly bottlenecks on WMF servers:
>>> https://phabricator.wikimedia.org/T69223
>>>
>>> Nemo
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> 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

Reply via email to