diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101028/002712.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101028/002712.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101028/002712.html b/zarb-ml/mageia-discuss/20101028/002712.html new file mode 100644 index 000000000..4595b5b2f --- /dev/null +++ b/zarb-ml/mageia-discuss/20101028/002712.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Suggestions + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C4CC8C207.8070206%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002710.html"> + <LINK REL="Next" HREF="002716.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Suggestions</H1> + <B>andre999</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C4CC8C207.8070206%40laposte.net%3E" + TITLE="[Mageia-discuss] Suggestions">andr55 at laposte.net + </A><BR> + <I>Thu Oct 28 02:21:27 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002710.html">[Mageia-discuss] Mageia-discuss Digest, Vol 2, Issue 133 +</A></li> + <LI>Next message: <A HREF="002716.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2712">[ date ]</a> + <a href="thread.html#2712">[ thread ]</a> + <a href="subject.html#2712">[ subject ]</a> + <a href="author.html#2712">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré a écrit : +><i> +</I>><i> Le 2010-10-26 01:33, andre999 a écrit : +</I>>><i> Juergen Harms a écrit : +</I>>>><i> +</I>>>><i> A couple of loose ideas that come when following the discussion: +</I>>>><i> +</I>>>><i> 1. Have packages pass "description QA" reading, done by non-technical +</I>>>><i> users (if implemented, easy with packages that are new or underwent a +</I>>>><i> major new release, how also catch packages that just "are around")? +</I>>>><i> +</I>>>><i> 2. As an alternative to direct mail to developpers, create some kind +</I>>>><i> of "fast-track" mailbox - rules to be defined - with a triage team to +</I>>>><i> make the link to the developpers (maybe not even with developpers, but +</I>>>><i> with "writers")? - would also allow to keep track of what is going on, +</I>>>><i> and serve as a "filter". +</I>>>><i> +</I>>>><i> 3. I suggest to separate the question of translation and of the +</I>>>><i> quality of descriptions - they have different priorities and +</I>>>><i> implications. +</I>>><i> +</I>>><i> Normally translation is made on the current source text, and often in +</I>>><i> real time. That is, as soon as a change is made in the text, it is +</I>>><i> immediately available for translation. This process is used by +</I>>><i> Openoffice and Mozilla (Firefox, Seamonkey, Thunderbird), for example, +</I>>><i> So for package description, as soon as any description (or change) is +</I>>><i> posted, it would be immediately available for translation, by the +</I>>><i> various localisation groups. +</I>>><i> +</I>><i> +</I>><i> So would this be possible to do with Mageia? We should be able to +</I>><i> manage this. +</I>><i> +</I>><i> Marc +</I> +I and others have already suggested this in various posts, and I sure +hope that we implement this. It is very doable. + +Since Mozilla started it, it has dramatically improved the completeness +of French translations, in which I was involved, even though many +translators at first complained about having to react in real time. +Virtually all localisations - except EN-US :) - showed significant +improvements in completeness, a number reaching 100%. A rare feat before. + +The new LibreOffice is using this method, as was done under OpenOffice. +Because of restrictions by Sun (continued by Oracle), LibreOffice has to +redo all the translations. +A big job, but this method really helps. Sun insisted that all +contributors had to submit a hard-copy signed contract to assign their +copyright to Sun, which severely limited contributions, including my own. +LibreOffice is initially using about the same organisation, but no +copyright assignment. +Interestingly, much like Mageia, LibreOffice has attracted most of the +key contributors. But surprisingly, Oracle is insisting that +contributors decide : OpenOffice or LibreOffice, but not both. Note +that most of the development work on OpenOffice has been done by +contributors paid by Sun/Oracle, unlike the situation with Mandriva. + +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002710.html">[Mageia-discuss] Mageia-discuss Digest, Vol 2, Issue 133 +</A></li> + <LI>Next message: <A HREF="002716.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2712">[ date ]</a> + <a href="thread.html#2712">[ thread ]</a> + <a href="subject.html#2712">[ subject ]</a> + <a href="author.html#2712">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |