diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101025/002640.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101025/002640.html | 178 |
1 files changed, 178 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101025/002640.html b/zarb-ml/mageia-discuss/20101025/002640.html new file mode 100644 index 000000000..f38a821b4 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101025/002640.html @@ -0,0 +1,178 @@ +<!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=%3C4CC5AE4F.1050701%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002654.html"> + <LINK REL="Next" HREF="002643.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=%3C4CC5AE4F.1050701%40laposte.net%3E" + TITLE="[Mageia-discuss] Suggestions">andr55 at laposte.net + </A><BR> + <I>Mon Oct 25 18:20:31 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002654.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002643.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2640">[ date ]</a> + <a href="thread.html#2640">[ thread ]</a> + <a href="subject.html#2640">[ subject ]</a> + <a href="author.html#2640">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer a écrit : +><i> Le dimanche 24 octobre 2010 à 09:21 +0200, Wolfgang Bornath a écrit : +</I>><i> +</I>><i> +</I>>><i> 2. What can we do to improve the package description in the +</I>>><i> "Individual package selection during system installation? Most +</I>>><i> descriptions there only say "Important" or "Comfortable" or some other +</I>>><i> nonsense like that. I really wonder who on earth had that idea! +</I>>><i> We need descriptions of the package, what it does. The description +</I>>><i> should be available for translation, so that according to the set +</I>>><i> language the user sees the package description in his language. +</I>>><i> +</I>><i> Yup, but that's not trivial, from a technical point of view. +</I>><i> +</I>><i> Rpm allow to have translation in spec file, but that's not .po, that's +</I>><i> more "let's translators edit the source code directly", which is +</I>><i> unintegrated with translators tools, do not take care of fuzzy string +</I>><i> and may break software build due to subtilities in specs ( like the +</I>><i> usage of % for macros, etc ). +</I>><i> +</I>><i> More ever, everything will appear in the packages indexes, which mean : +</I>><i> - more memory used for all installation +</I>><i> - bigger indexes to download +</I>><i> - longer time to load from disk, which mean longer rpmdrake startup +</I>><i> - less space on cd and or dvd. +</I>><i> +</I>><i> So we need to find a better way. +</I>><i> +</I>><i> Better in two points : +</I>><i> - better way to distribute it +</I>><i> - better way to translate it +</I>><i> +</I>><i> The distribution part is IMHO the easiest now we have the control of the +</I>><i> main mirror. We can just split the hdlist in 2, one for the description, +</I>><i> for each languages, one for the metadata, and let urpmi/whatever combine +</I>><i> this into a regular hdlist and use this. We can even maybe find a way +</I>><i> that will not break smart and others. +</I>><i> +</I>><i> The translation part is more tricky, we tried in the past with the +</I>><i> CVS-po project, but it didn't work, maybe someone who as around that +</I>><i> time could tell us. Anne know for sure, Wolfgang is likely to know too. +</I>><i> +</I>><i> Basically, the idea was to extract the summary and description from the +</I>><i> packages indexes, and then convert this as .po file. There is a small +</I>><i> problem however. If we use .po per package, then it will be hellish for +</I>><i> translators to open 10000 files ( imho, maybe I am wrong ). If we use +</I>><i> one .po for repository, then the files are huge and maybe consume too +</I>><i> much ressources ( even if nowadays, laptops are provided with more +</I>><i> memory than the server we use at PLF for everything). +</I>><i> +</I>><i> Maybe we can group rpm .po, like 1 file for 100 rpms description, but I +</I>><i> fear this will bring problem too. +</I>><i> +</I>><i> Then we also have to write a software that goes from .po to hdlist, of +</I>><i> course, which may e non trivial ( as it requires both intimate knowledge +</I>><i> about rpm and gettext ). +</I>><i> +</I>><i> +</I>>><i> 3. The same is needed in rpmdrake. +</I>>><i> +</I>>><i> In other words: +</I>>><i> We need a way to add descriptions to packages. These descriptions must +</I>>><i> be available for the installer in "Individual package selecteion" and +</I>>><i> there must be a way to have .po files for the translators. +</I>>><i> +</I>><i> Yup. +</I>><i> +</I>><i> +</I>>><i> Is there something which can be done without passing the ball to and +</I>>><i> fro like a tennis match? +</I>>><i> +</I>><i> On the translation side, it is work. On the improve description side, I +</I>><i> suggest to organize day dedicated to the task, like the bug days. See my +</I>><i> other mail on the thread about it. +</I>><i> +</I>There are some ideas fomenting here ... +What about an online tool, with the descriptions by package, where +anyone (with the appropriate account) can contribute, seeing the current +description, and suggest changes. The packager (or authorised person) +will confirm any changes, so this evolves dynamically. + +Translators access the confirmed description on line, and similarly make +changes for their language, with a similar confirmation process. +Any changes to the base description are automatically signalled for +translators. + +During the cauldron period, maybe the translations are not necessarily +included, but for release time (at least), the base description and +confirmed translations are automatically included in the package, by +whatever tool is necessary. + +1) By having the description changes and translations made online, they +are easier to implement in a timely manner. + +2) There should be a way of doing it offline and posting changes online +as well. + +3) I don't know what software would be appropriate, but LibreOffice is +thinking of using Pootle, which seems to be appropriate from their +discussions. +See : <A HREF="http://translate.sourceforge.net/wiki/pootle/index">http://translate.sourceforge.net/wiki/pootle/index</A> +and : <A HREF="http://en.wikipedia.org/wiki/Pootle">http://en.wikipedia.org/wiki/Pootle</A> + +If we get something like this implemented, it will be a big improvement +over Mandriva, and probably most other distros. Which should in turn +lead to their improvement as well. + +my 2 cents :) +- André + +</PRE> + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002654.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002643.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2640">[ date ]</a> + <a href="thread.html#2640">[ thread ]</a> + <a href="subject.html#2640">[ subject ]</a> + <a href="author.html#2640">[ 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> |