Le 21/12/2016 à 22:42, Gergo Tisza a écrit :
I sympathize with the goal but accessibility benefits
would be far
outweighed by maintaince costs.
Maybe. Or maybe not. I can't judge very
objectively without metrics, can I?
We regularly use grep to find code which is
about to be deprecated;
Well, that's fine, and surely having localized versions
of code would
fall into your grep process, wouldn't it?
wikis copy gadgets from each other;
Yeah, sure
that's a problem, and having a centralized gadget repository
is a saner way to go that happen to be number 1 on 2016 Community
Wishlist Survey/Results
<https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results>
:)
more
experienced developers are sometimes asked to help a wiki where the local
maintainers have less experience. We have a whole global user group for
people who go from wiki to wiki and fix things.
Well, I share your concerns, and I
don't pretend that I have a perfect
out of the box solution which make the best balance between technical
maintainability, technical skill dissemination, linguistic
diversity/accessibility and so on.
And that's not even taking into account the implementation costs, which
would probably be massive if it includes stuff like localizing
Lua/Javascript language keywords.
Well, that's why the thread is about
internationalization, and not
localization. Just like they are tools to translate all the Wikimedia
non-executable hosted content. Or more generally, the way Wikimedia
provide the technical facilities but not the human resources to make it
so wide projects constructed on this infrastructure.
The Wikimedia community collectively has
a lot of experience with web development but not a whole lot of experience
with programming language compiler development.
Once again, I don't have
metrics about that (but I admit that to my mind
you statements seems relevant).
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l