diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101025/002653.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101025/002653.html | 124 |
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101025/002653.html b/zarb-ml/mageia-discuss/20101025/002653.html new file mode 100644 index 000000000..6db71bb8b --- /dev/null +++ b/zarb-ml/mageia-discuss/20101025/002653.html @@ -0,0 +1,124 @@ +<!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=%3C4CC5F3F1.8040009%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" 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=%3C4CC5F3F1.8040009%40laposte.net%3E" + TITLE="[Mageia-discuss] Suggestions">andr55 at laposte.net + </A><BR> + <I>Mon Oct 25 23:17:37 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002643.html">[Mageia-discuss] Suggestions +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2653">[ date ]</a> + <a href="thread.html#2653">[ thread ]</a> + <a href="subject.html#2653">[ subject ]</a> + <a href="author.html#2653">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frank Griffin a écrit : +><i> Michael Scherer wrote: +</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> +</I>>><i> +</I>><i> Maybe the problem is trying to use rpm as the management tool for +</I>><i> descriptions. +</I>><i> +</I>><i> Long, long, ago I had to write an order processing system for an IBM +</I>><i> 5100, which supported 2 languages - APL and Basic - both of which were +</I>><i> interpreted, meaning the source code had to fit into memory, which was 32K. +</I>><i> +</I>><i> This made it virtually impossible to comment the code in any meaningful +</I>><i> way, since the comments took up memory needed for code. +</I>><i> +</I>><i> What I finally settled upon was to tag blocks of code with a 4-or-5 +</I>><i> character comment which was basically an index key into a typewritten +</I>><i> document which contained the program comments. The same thing might +</I>><i> work here. +</I>><i> +</I>><i> Change the rpm description to a database table partial key which +</I>><i> corresponds to the package. Then set up a database table keyed by that +</I>><i> partial key plus a language ID, and place the description in that +</I>><i> language there. Change tools which display package descriptions to use +</I>><i> the rpm value as a key into the database combined with the locale language. +</I>><i> +</I>><i> This shifts the space requirement from the package rpm SPEC to the +</I>><i> database, and means that description maintainers can just have access to +</I>><i> the database rather than the source tree. Since most uses of rpm don't +</I>><i> make use of the description, bandwidth for normal maintenance goes +</I>><i> down. For things like the install, you include a copy of the database +</I>><i> on the media, or conditionally on the user's system for rpmdrake (much +</I>><i> as they get to choose between hdlist and synthesis today). +</I>><i> +</I>><i> This would allow much more flexible queries, and would allow translators +</I>><i> to extract all descriptions in their own language as a single result +</I>><i> set, identify all packages which do not have a description in a given +</I>><i> language, and so forth. +</I>><i> +</I>><i> If the central database were managed by JEE/EJB with role-based security +</I>><i> tied to the new LDAP database, user maintenance would be fairly simple. +</I>><i> Obviously, for use in captive form (e.g. in the install or on a user's +</I>><i> system), an extract in some other form would be used to avoid the need +</I>><i> for JEE. +</I>><i> +</I>><i> WDYT ? +</I>><i> +</I> +Interesting idea. As I understand, descriptions are stored in local the +database of already installed packages, so this would be a pre-install +equivalent. +However there is the problem of keeping everything in sync, if the +documentation is not included in the rpms. + +If in the development process the descriptions were kept in such a +central database, along with their localisations, they could be +automatically extracted from the database for insertion in the package +when the package is generated. +That won't reduce the size of the Rpms, but it would ensure that the +description, with localisations, is always included in the Rpm. +Since last minute changes before packaging are much less likely to +change displayed text (or documentation), the localisations risk being +up to date. + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002643.html">[Mageia-discuss] Suggestions +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#2653">[ date ]</a> + <a href="thread.html#2653">[ thread ]</a> + <a href="subject.html#2653">[ subject ]</a> + <a href="author.html#2653">[ 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> |