summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-i18n/2013-April/004201.html
blob: 11847a94eef1bcb9dd5f35837d9e19c2d0c6088c (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
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-i18n] What was wrong with Transifex?
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20What%20was%20wrong%20with%20Transifex%3F&In-Reply-To=%3CCABS0%3D2QEC6CMiTjmzACW5ijsa9jrsr%3DKcnpf9Q9%2BKWk97x2bbw%40mail.gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="004199.html">
   <LINK REL="Next"  HREF="004203.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-i18n] What was wrong with Transifex?</H1>
    <B>atilla ontas</B> 
    <A HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20What%20was%20wrong%20with%20Transifex%3F&In-Reply-To=%3CCABS0%3D2QEC6CMiTjmzACW5ijsa9jrsr%3DKcnpf9Q9%2BKWk97x2bbw%40mail.gmail.com%3E"
       TITLE="[Mageia-i18n] What was wrong with Transifex?">tarakbumba at gmail.com
       </A><BR>
    <I>Thu Apr  4 20:43:08 CEST 2013</I>
    <P><UL>
        <LI>Previous message: <A HREF="004199.html">[Mageia-i18n] What was wrong with Transifex?
</A></li>
        <LI>Next message: <A HREF="004203.html">[Mageia-i18n] What was wrong with Transifex?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4201">[ date ]</a>
              <a href="thread.html#4201">[ thread ]</a>
              <a href="subject.html#4201">[ subject ]</a>
              <a href="author.html#4201">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>2013/4/4 Oliver Burger &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-i18n">oliver.bgr at gmail.com</A>&gt;

&gt;<i> Well, it doesn't matter if the translations are in a separate
</I>&gt;<i> repository or not and I'm not sure, what it woudl mean for the devs,
</I>&gt;<i> to separate them.
</I>&gt;<i> The problem with tx is - or at least was - the manual work involved
</I>&gt;<i> upon string changes.
</I>&gt;<i>
</I>&gt;<i> As an example:
</I>&gt;<i> When uploading a file into tx, it parses that file and adds the
</I>&gt;<i> strings into the database. When the string changes in the original pot
</I>&gt;<i> (even it's only a typo), and you reupload the pot file, tx will parse
</I>&gt;<i> it and see a new string and one string missing and it will act
</I>&gt;<i> accordingly:
</I>&gt;<i> It will remove the translations for the old string from its database
</I>&gt;<i> and it will add the new untranslated string, since it can not know,
</I>&gt;<i> that this was only a string change.
</I>&gt;<i> So the task for us (mostly me) was:
</I>&gt;<i> - Tell you not to touch certain translation resources in a certain time
</I>&gt;<i> span
</I>&gt;<i> - Download all files from this resource from tx
</I>&gt;<i> - merge them manually with the changed po files (it couldn't be
</I>&gt;<i> automated, since TX also had problems fuzzying strings correctly)
</I>&gt;<i> - reupload all files to tx and tell you to check
</I>&gt;<i>
</I>&gt;<i> I would rather have a solution without the need to do so....
</I>&gt;<i>
</I>&gt;<i> Cheers,
</I>&gt;<i>
</I>&gt;<i> Oliver
</I>&gt;<i>
</I>Hi again. I think most of the problems you mentioned are past day problems.
-Tx can be locked for certain resources to not accept new translations.
See: <A HREF="https://www.transifex.com/projects/p/chakra-project/language/tr/">https://www.transifex.com/projects/p/chakra-project/language/tr/</A>
Resources wtih red dot mark locked.

- As i mentioned earlier even a bash script can automate pulling from tx
process on server side. &#304;s it so hard to do? I really do not know...

- Merging should be done in tx. Say, use hourly cron job to pull from and
push to tx. Than tx should care of translations and resources merging?

- As i mentioned earlier again, i can tell tx can automatically pull
resources and transations from svn from what i read.

- Tx do not mess up translator information anymore. It has been fixed as i
know.

- For the fuzzy strings, tx still adds them into database as suggestions
and every tx translator can see and if possible use them in online
translation.
My 2 cents.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: &lt;/pipermail/mageia-i18n/attachments/20130404/f6dd94d9/attachment.html&gt;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="004199.html">[Mageia-i18n] What was wrong with Transifex?
</A></li>
	<LI>Next message: <A HREF="004203.html">[Mageia-i18n] What was wrong with Transifex?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#4201">[ date ]</a>
              <a href="thread.html#4201">[ thread ]</a>
              <a href="subject.html#4201">[ subject ]</a>
              <a href="author.html#4201">[ 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>