It would be better, IMHO, if we didn't use HTML tags directly. Instead, we should wrapper them with templates. On en, we could use {{sup|...}}. The translation problem would then disappear.
Steve
On 5/4/07, Mohamed Magdy mohamed.m.k@gmail.com wrote:
Hello!
Can you please make these tags translatable?
%alnokta
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/wikitech-l
Steve Bennett wrote:
It would be better, IMHO, if we didn't use HTML tags directly. Instead, we should wrapper them with templates. On en, we could use {{sup|...}}. The translation problem would then disappear.
I think such templates are used already, but it's not efficient, it won't work on all wikis, and it's not as flexible as HTML.
On 5/4/07, Mohamed Magdy mohamed.m.k@gmail.com wrote:
Hello!
Can you please make these tags translatable?
%alnokta
I would like to see a proposed translation of all of HTML and CSS into Arabic and Hebrew. To do it piecemeal seems like a bit of a waste of developer time. If the Arabic/Hebrew language communities consider this worthwhile enough to have a serious attempt at it, the results may well be applicable outside of MediaWiki/Wikimedia.
-- Tim Starling
On 5/3/07, Tim Starling tstarling@wikimedia.org wrote:
I think such templates are used already, but it's not efficient, it won't work on all wikis
Oh? Because of directionality?
and it's not as flexible as HTML.
You mean because there are limits in what you can pass into a template as a parameter? My understanding was that that was primarily a problem for block elements that could contain massive chunks of code. But for <sup>, is it really a problem?
Steve
Steve Bennett wrote:
On 5/3/07, Tim Starling tstarling@wikimedia.org wrote:
I think such templates are used already, but it's not efficient, it won't work on all wikis
Oh? Because of directionality?
Because wikis don't start with a predefined set of templates.
and it's not as flexible as HTML.
You mean because there are limits in what you can pass into a template as a parameter? My understanding was that that was primarily a problem for block elements that could contain massive chunks of code. But for <sup>, is it really a problem?
I mean because you can't support the full attribute set. Well, maybe you could, but the resulting template would be extraordinarily ugly and inefficient. And yes, you couldn't use the "|" character.
-- Tim Starling
Tim Starling wrote:
Steve Bennett wrote:
On 5/3/07, Tim Starling tstarling@wikimedia.org wrote:
I think such templates are used already, but it's not efficient, it won't work on all wikis
Oh? Because of directionality?
Because wikis don't start with a predefined set of templates.
Then we're making things worse. If i import a page, i know i have to also import its included templates. If we change wiki-syntax from language to language, how do i know when importing if <???> tag is an extension, a translated html tag (which my wiki already has but with a different name) or where to get it?
An option could be translating to every mediawiki language setup. But doesn't seem too wise either.
On 5/4/07, Platonides Platonides@gmail.com wrote:
Tim Starling wrote:
Steve Bennett wrote:
On 5/3/07, Tim Starling tstarling@wikimedia.org wrote:
I think such templates are used already, but it's not efficient, it won't work on all wikis
Oh? Because of directionality?
Because wikis don't start with a predefined set of templates.
Then we're making things worse. If i import a page, i know i have to also import its included templates. If we change wiki-syntax from language to language, how do i know when importing if <???> tag is an extension, a translated html tag (which my wiki already has but with a different name) or where to get it?
How do you figure it out currently? Either Google it or ask someone.
Simetrical wrote:
How do you figure it out currently?
An HTML background + they are not so many. Try having them x200... Well, we can have fun when trying to deal with a mismatch of inline/block elements which you don't recognise on source ;-)
Either Google it
Most likely found on a html manual than a mediawiki one. BTW, i have problems to found it, as google ignores the < >
or ask someone.
Yes, just like "i get garbage on my page, many {{#if: ..." Which means people can't figure out. We can't be the fucking manual.
I have been thinking in automagically translate them on view source / save (a 'wikisyntax dialect' parameter?), while keeping the "official" on db & Special:Export but i don't feel like breaking "page editing is page source"
Platonides wrote:
Tim Starling wrote:
Steve Bennett wrote:
On 5/3/07, Tim Starling tstarling@wikimedia.org wrote:
I think such templates are used already, but it's not efficient, it won't work on all wikis
Oh? Because of directionality?
Because wikis don't start with a predefined set of templates.
Then we're making things worse. If i import a page, i know i have to also import its included templates. If we change wiki-syntax from language to language, how do i know when importing if <???> tag is an extension, a translated html tag (which my wiki already has but with a different name) or where to get it?
An option could be translating to every mediawiki language setup. But doesn't seem too wise either.
The proposal is Hebrew and Arabic HTML, available on all wikis regardless of content language.
http://meta.wikimedia.org/wiki/HTML_translation
-- Tim Starling
<snip>
I would like to see a proposed translation of all of HTML and CSS into Arabic and Hebrew. To do it piecemeal seems like a bit of a waste of developer time. If the Arabic/Hebrew language communities consider this worthwhile enough to have a serious attempt at it, the results may well be applicable outside of MediaWiki/Wikimedia.
Yes, I think that will be very nice :) and I'm willing to help...
-- Tim Starling
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org