blob: cc37cc41f876243dca5faaa0dbfffbaced33f14c (
plain)
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-i18n] Translation -structure
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20Translation%20-structure&In-Reply-To=%3Ci7so3j%24gmo%241%40dough.gmane.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000052.html">
<LINK REL="Next" HREF="000060.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-i18n] Translation -structure</H1>
<B>Adrian Marcinkowski</B>
<A HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20Translation%20-structure&In-Reply-To=%3Ci7so3j%24gmo%241%40dough.gmane.org%3E"
TITLE="[Mageia-i18n] Translation -structure">amfidiusz at gmail.com
</A><BR>
<I>Tue Sep 28 14:46:34 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000052.html">[Mageia-i18n] [Mageia-discuss] Translation -structure
</A></li>
<LI>Next message: <A HREF="000060.html">[Mageia-i18n] [Mageia-discuss] Translation -structure
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#56">[ date ]</a>
<a href="thread.html#56">[ thread ]</a>
<a href="subject.html#56">[ subject ]</a>
<a href="author.html#56">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>W dniu 2010-09-28 14:17, Lombard Marianne pisze:
>><i> The suggestion, that i wanted to run by someone before putting on the
</I>>><i> mailist, is that each country community starts a section (a wiki for
</I>>><i> example) where all the members of that community are able to translate
</I>
I'm definitely against using wiki for translation purposes or giving
access to i18n tools to everybody. First of all, localization needs to
be consistent. If everybody starts giving different names for same
features, it will be a mess. Of course, there could be supervisors
checking every single word but that structure will not work in smaller
communities where HR capacity is limited. There also need to be a
extensive guideline for all translators - and if we cannot force the
community not to top-post on the mailing lists, I doubt we can reach
concensus on the matter of proper phrases localization. I don't want to
say that many of Mageia users will do the bad job on purpose but huge
amount of them is not either fluent in English or their own language to
be a translator.
What I see as a perfect solution, is - discussed earlier - transifex. It
will allow us to manage files easily and to create skillful and devoted
localization teams. Of course, everybody would be able to join but the
selection of candidates should appear in order not to do the same job twice.
Regards,
Adrian
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000052.html">[Mageia-i18n] [Mageia-discuss] Translation -structure
</A></li>
<LI>Next message: <A HREF="000060.html">[Mageia-i18n] [Mageia-discuss] Translation -structure
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#56">[ date ]</a>
<a href="thread.html#56">[ thread ]</a>
<a href="subject.html#56">[ subject ]</a>
<a href="author.html#56">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-i18n">More information about the Mageia-i18n
mailing list</a><br>
</body></html>
|
