skip to main |
skip to sidebar
Software design school
Start creating games.
============================================================================================================================ Op Do, 2009-03-05 om 11:15 +0100 skryf Axel Hecht: Hi all, please note that the releases/l10n-mozilla-1.9.1 repos participating in the Firefox 3.1 Beta 3 release have been tagged. The tags themselves have been pushed to changesets on a relbranch, GECKO191b3_20090304_RELBRANCH. Hallo all Since I don't really follow the discussion in the rest of the thread about the relative merits of different approaches, I'll put an unguided vote in for whatever will allow me to have the faintest chance to ever explain this to a non-technical translator. We've had some interest from people in currently unsupported languages, but this part of the process continues to be beyond any complexity I've needed to master in any other project. As some people in IRC would know, my last two commits collectively took several hours due to struggling with mercurial errors that were eventually only solved with a fresh clone (each time). And this was just for beta releases. I've been translating GNOME for several releases, and don't even have commit access yet - the process can be that simple for GNOME if needed. So I believe we should continue to think of ways in which we can simplify our process. I don't think we really need to anticipate advanced branching requirements or similar VCS features as needed by developers (which I think is what Robert was saying). Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/video-virtaals-functionality _______________________________________________ dev-l10n mailing list dev- ... @lists.mozilla.org https://lists.mozilla.org/listinfo/dev-l10n Platonides wrote: Mohamed Magdy wrote: * I think it would be doable to make a tab that Egyptianizes (or any other dialect) the Arabic article, that is, if we have some sort of conversion memory, that is if the dialect is stable (or standard), the dialect differs from a place to another, from a muhafazah to another ( http://en.wikipedia.org/wiki/Muhafazah ). if anyone knows the technical method we could make a trial instead of the great mess of dialect Wikipedias. I'm not too sure about this compromise yet. If there're clear (algoritmic) rules for that, it can be done. See at http://zh.wikipedia.org/ how it can be viewed on seven! different variants. The Chinese variants just use conversion tables, not an algorithm. That's the only kind of conversion that can be done by the current software. If literacy is the aim of this Egyptian Arabic project, then perhaps a useful first step would be to implement a de-vocalising filter. That should be possible with the current software. Then, with the filter on by default, editors can add vocalic marking in the edit box without annoying too many people. That's the approach that seems to be indicated by pages 7-12 of this paper: http://papers.ldc.upenn.edu/EALL/ArabicLiteracy.pdf Like zh-min-nan, we'd probably be accused of encouraging baby-talk, but if the community was behind it then it could go ahead. -- Tim Starling _______________________________________________ foundation-l mailing list foun ... @lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l