1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
<!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=%3C1287912731.22938.259.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="002599.html">
<LINK REL="Next" HREF="002597.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-discuss] Suggestions</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C1287912731.22938.259.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-discuss] Suggestions">misc at zarb.org
</A><BR>
<I>Sun Oct 24 11:32:11 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="002599.html">[Mageia-discuss] Suggestions
</A></li>
<LI>Next message: <A HREF="002597.html">[Mageia-discuss] Suggestions
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2604">[ date ]</a>
<a href="thread.html#2604">[ thread ]</a>
<a href="subject.html#2604">[ subject ]</a>
<a href="author.html#2604">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le dimanche 24 octobre 2010 à 09:21 +0200, Wolfgang Bornath a écrit :
><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>
Yup, but that's not trivial, from a technical point of view.
Rpm allow to have translation in spec file, but that's not .po, that's
more "let's translators edit the source code directly", which is
unintegrated with translators tools, do not take care of fuzzy string
and may break software build due to subtilities in specs ( like the
usage of % for macros, etc ).
More ever, everything will appear in the packages indexes, which mean :
- more memory used for all installation
- bigger indexes to download
- longer time to load from disk, which mean longer rpmdrake startup
- less space on cd and or dvd.
So we need to find a better way.
Better in two points :
- better way to distribute it
- better way to translate it
The distribution part is IMHO the easiest now we have the control of the
main mirror. We can just split the hdlist in 2, one for the description,
for each languages, one for the metadata, and let urpmi/whatever combine
this into a regular hdlist and use this. We can even maybe find a way
that will not break smart and others.
The translation part is more tricky, we tried in the past with the
CVS-po project, but it didn't work, maybe someone who as around that
time could tell us. Anne know for sure, Wolfgang is likely to know too.
Basically, the idea was to extract the summary and description from the
packages indexes, and then convert this as .po file. There is a small
problem however. If we use .po per package, then it will be hellish for
translators to open 10000 files ( imho, maybe I am wrong ). If we use
one .po for repository, then the files are huge and maybe consume too
much ressources ( even if nowadays, laptops are provided with more
memory than the server we use at PLF for everything).
Maybe we can group rpm .po, like 1 file for 100 rpms description, but I
fear this will bring problem too.
Then we also have to write a software that goes from .po to hdlist, of
course, which may e non trivial ( as it requires both intimate knowledge
about rpm and gettext ).
><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>
Yup.
><i> Is there something which can be done without passing the ball to and
</I>><i> fro like a tennis match?
</I>
On the translation side, it is work. On the improve description side, I
suggest to organize day dedicated to the task, like the bug days. See my
other mail on the thread about it.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002599.html">[Mageia-discuss] Suggestions
</A></li>
<LI>Next message: <A HREF="002597.html">[Mageia-discuss] Suggestions
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2604">[ date ]</a>
<a href="thread.html#2604">[ thread ]</a>
<a href="subject.html#2604">[ subject ]</a>
<a href="author.html#2604">[ 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>
|
