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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-i18n] Workflow for i18n translators
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20Workflow%20for%20i18n%20translators&In-Reply-To=%3C1292852100.24222.5.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="000469.html">
<LINK REL="Next" HREF="000450.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-i18n] Workflow for i18n translators</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20Workflow%20for%20i18n%20translators&In-Reply-To=%3C1292852100.24222.5.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-i18n] Workflow for i18n translators">misc at zarb.org
</A><BR>
<I>Mon Dec 20 14:35:00 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000469.html">[Mageia-i18n] Workflow for i18n translators
</A></li>
<LI>Next message: <A HREF="000450.html">[Mageia-i18n] Workflow for i18n translators
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#470">[ date ]</a>
<a href="thread.html#470">[ thread ]</a>
<a href="subject.html#470">[ subject ]</a>
<a href="author.html#470">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 18 décembre 2010 à 09:49 +0800, Funda Wang a écrit :
><i> 2010/12/18 Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-i18n">molch.b at googlemail.com</A>>:
</I>><i> > We already have 2 major points which (according to what I read so far)
</I>><i> > are important:
</I>><i> > - online and offline work should be possible.
</I>><i> > - only 2 or 3 translators of each language should be able to commit
</I>><i> > (which implies collaboration)
</I>><i> FYI, since transifex 1.0, it provides a nice CLI toolkit for both
</I>><i> translators and developers. Translators could sync and commit po file
</I>><i> directly to transifex platform via this toolkit, without any web
</I>><i> interface.
</I>
Yup, and I packaged this tool.
For more information :
<A HREF="http://help.transifex.net/user-guide/client/client-0.3.html">http://help.transifex.net/user-guide/client/client-0.3.html</A>
><i> And, the task of commit translation to VCS becomes the duty of
</I>><i> developer, not the transifex robot anymore. We might want to improve
</I>><i> our mgasys tool, so that something like "mgasys tag urpmi 4.0" would
</I>><i> commit translations from transifex to our VCS, then tag it into
</I>><i> soft/urpmi/tags/4.0, and finally generate a urpmi-4.0.tar.xz in the
</I>><i> developers harddisk.
</I>
That's not really the goal of mdvsys to manage anything else than rpms.
Ie, for software, I would push this either in generic tools ( like
moap ), specific tools ( like dist:zilla ), or directly in plain old
makefile.
Another solution is a simple cronjob that run transifex command line
tool with proper svn acl management on languages file.
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000469.html">[Mageia-i18n] Workflow for i18n translators
</A></li>
<LI>Next message: <A HREF="000450.html">[Mageia-i18n] Workflow for i18n translators
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#470">[ date ]</a>
<a href="thread.html#470">[ thread ]</a>
<a href="subject.html#470">[ subject ]</a>
<a href="author.html#470">[ 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>
|
