1
00:00:05,708 --> 00:00:07,130
This talk will be in French,

2
00:00:07,331 --> 00:00:08,239
so I apologize

3
00:00:09,960 --> 00:00:12,480
After much debate, we decided to
settle to French

4
00:00:12,698 --> 00:00:16,023
because we present the French
localization

5
00:00:16,628 --> 00:00:20,860
but I can announce right now

6
00:00:21,167 --> 00:00:24,689
that I will subtitle and translate
this talk

7
00:00:24,790 --> 00:00:27,615
as soon as possible, so
if you’re interested

8
00:00:29,428 --> 00:00:32,956
come check in a few days and
you'll have subtitles.

9
00:00:35,407 --> 00:00:37,120
Now I can switch back
to French.

10
00:00:39,241 --> 00:00:43,383
We're going to introduce to you how
we localize Debian.

11
00:00:44,105 --> 00:00:46,521
First, I will explain
what localization is.

12
00:00:47,738 --> 00:00:50,666
It's a word that we do not
hear often

13
00:00:51,277 --> 00:00:53,087
except when you actually do
localization.

14
00:00:53,689 --> 00:00:56,326
Roughly, it's the same as
translation

15
00:00:56,629 --> 00:01:02,089
but it's a little more than just
translation.

16
00:01:02,403 --> 00:01:05,327
Besides simply translating…

17
00:01:05,932 --> 00:01:08,553
[mic stops working]

18
00:01:15,208 --> 00:01:15,812
Thanks.

19
00:01:16,215 --> 00:01:17,934
So, where was I? Ah yes!

20
00:01:18,035 --> 00:01:21,059
We do not simply translate
in a litteral manner

21
00:01:21,361 --> 00:01:26,504
from English, in this case, since
it's the original version,

22
00:01:26,813 --> 00:01:28,021
to French

23
00:01:28,323 --> 00:01:29,432
we also try to adapt

24
00:01:29,756 --> 00:01:36,206
to the french, or French speaking,
context and culture.

25
00:01:37,637 --> 00:01:39,956
It's abbreviated in l10n

26
00:01:40,158 --> 00:01:43,890
That is localization, one "L",
10 letters, then a "N".

27
00:01:46,013 --> 00:01:49,040
So don't be surprised
if you see this.

28
00:01:49,448 --> 00:01:54,485
This concept is really close to the
internationalisation, or i18n,

29
00:01:55,693 --> 00:02:00,733
which consists in preparing content
so it is

30
00:02:00,935 --> 00:02:04,865
easy to be translated, localized,
in other languages.

31
00:02:11,090 --> 00:02:12,365
So, why do we do that?

32
00:02:15,591 --> 00:02:19,034
Simply because it allows Debian

33
00:02:19,641 --> 00:02:24,077
to be accessible to users
who don't necessarily

34
00:02:24,384 --> 00:02:25,493
speak English.

35
00:02:25,897 --> 00:02:28,628
It's a good thing, since as the
Social Contract says,

36
00:02:28,830 --> 00:02:31,348
users are Debian's priority

37
00:02:31,959 --> 00:02:34,075
but we also forget to say that
it means

38
00:02:34,192 --> 00:02:35,604
current and future users.

39
00:02:35,908 --> 00:02:37,827
Yet, to attract new users,

40
00:02:38,035 --> 00:02:40,759
there is nothing worse for
mainstream users than to bump into

41
00:02:40,860 --> 00:02:42,379
a system in English.

42
00:02:43,086 --> 00:02:44,297
You may know the saying:

43
00:02:44,500 --> 00:02:46,412
When a computer is pissed off,
it speaks to you in English.

44
00:02:47,319 --> 00:02:49,338
We know that it is not the case,
but for a mainstream audience it is,

45
00:02:49,438 --> 00:02:51,558
so it's important for us to have
a system

46
00:02:51,660 --> 00:02:55,095
as internationalized as possible,
and so in French as well.

47
00:02:55,800 --> 00:02:57,617
It has also benefits for yourself

48
00:02:58,224 --> 00:03:00,454
and I believe it's important
to state that

49
00:03:00,554 --> 00:03:02,669
for those who would want to
contribute

50
00:03:03,380 --> 00:03:07,108
because it allows all contributors

51
00:03:07,215 --> 00:03:08,638
to learn new things

52
00:03:09,141 --> 00:03:12,164
by discovering all the aspects of
the Debian Project

53
00:03:12,264 --> 00:03:15,390
because the translation work is really
diversified, as we'll see later.

54
00:03:15,805 --> 00:03:17,934
It also allows you to discover
upstream projects

55
00:03:18,041 --> 00:03:19,351
and how they work

56
00:03:19,609 --> 00:03:22,631
and it allows you to contribute
at your own pace, because

57
00:03:22,831 --> 00:03:27,064
you can participate calmly
to this or that thing

58
00:03:27,264 --> 00:03:31,189
without doing it continuously
at the beginning, and keep your pace.

59
00:03:31,289 --> 00:03:33,812
Last but not least, you can
improve your english

60
00:03:34,820 --> 00:03:37,742
because when you translate,
your English can becomes a little better

61
00:03:37,843 --> 00:03:38,953
in the end

62
00:03:39,155 --> 00:03:40,566
at least when it comes to write and
understand it.

63
00:03:41,393 --> 00:03:45,333
So you can improve your English,
which is not negligible.

64
00:03:45,939 --> 00:03:49,869
And all of this is thanks to
the vast scope of translations

65
00:03:49,970 --> 00:03:51,985
as we will see now.

66
00:03:53,398 --> 00:03:54,707
So, what is our scope.

67
00:03:55,919 --> 00:03:57,028
First, packages.

68
00:03:57,355 --> 00:03:59,070
It makes sense, as it's at the core
of Debian.

69
00:03:59,273 --> 00:04:01,085
We translate native packages
developed

70
00:04:01,185 --> 00:04:04,312
by and for Debian,
like dpkg, aptitude,

71
00:04:04,513 --> 00:04:06,630
all those packages.

72
00:04:09,854 --> 00:04:11,467
We also work on debconf
configuration screens,

73
00:04:11,769 --> 00:04:13,783
screens when you install packages,

74
00:04:13,988 --> 00:04:15,597
for instance, with exim.

75
00:04:16,001 --> 00:04:19,137
When you install this package,
this screen is prompted

76
00:04:19,338 --> 00:04:20,647
to ask you

77
00:04:20,071 --> 00:04:25,007
« Do you want local alerts? » etc.

78
00:04:25,409 --> 00:04:28,231
This configuration is by default
in English.

79
00:04:28,433 --> 00:04:30,755
What we do is translate it.

80
00:04:31,864 --> 00:04:33,473
You can notice that it's…

81
00:04:33,696 --> 00:04:36,318
Here, the English text spans on 3 lines

82
00:04:36,725 --> 00:04:38,338
and once translated into French,

83
00:04:38,551 --> 00:04:39,960
it spreads on 4 lines,

84
00:04:40,165 --> 00:04:41,676
because French is very rich (and verbose)

85
00:04:41,983 --> 00:04:44,298
so it will take more place

86
00:04:44,503 --> 00:04:45,510
on the configuration screens.

87
00:04:45,724 --> 00:04:48,144
So, sorry if they're too big, we try
as much as possible

88
00:04:48,245 --> 00:04:51,671
to keep them short, but we want to remain
faithful to the source.

89
00:04:53,712 --> 00:04:55,020
We also translate announcements.

90
00:04:55,432 --> 00:04:57,547
All the announcements sent to the

91
00:04:57,648 --> 00:04:59,157
debian-news-french
mailing list

92
00:04:59,358 --> 00:05:02,086
such as Debian releases, DPNs

93
00:05:02,288 --> 00:05:04,003
and all other announcements.

94
00:05:04,710 --> 00:05:07,533
Evething that you see on the list
goes through the team

95
00:05:09,851 --> 00:05:11,178
Also, the web site.

96
00:05:11,380 --> 00:05:12,790
There are 10,000 pages
on the web site.

97
00:05:12,992 --> 00:05:15,411
That's a lot

98
00:05:15,713 --> 00:05:17,231
and 90% of it is translated
(in French).

99
00:05:18,036 --> 00:05:21,865
Some big contributors to it are
in the room.

100
00:05:22,682 --> 00:05:25,807
There is the static part of the website,
the one we usually see,

101
00:05:26,009 --> 00:05:29,436
the homepage and all the pages
that do not change very often,

102
00:05:30,041 --> 00:05:36,389
but there are also the publicity announcements,
security (DSA and DLA) advisories

103
00:05:36,691 --> 00:05:37,801
and that makes a lot of pages

104
00:05:38,006 --> 00:05:40,223
We discussed this topic yesterday during
the l10n team sprint,

105
00:05:40,432 --> 00:05:42,953
that's between 300 and 600
new pages per year

106
00:05:43,664 --> 00:05:45,681
so it's quite big, one or two pages
per day.

107
00:05:46,206 --> 00:05:49,830
This work could be a little tedious

108
00:05:50,838 --> 00:05:54,267
so we try to find some novelty
when doing

109
00:05:54,569 --> 00:05:55,879
those translations.

110
00:05:56,487 --> 00:05:59,916
Recently, we also translated
the DPL canditates platforms.

111
00:06:00,922 --> 00:06:02,943
It was like a mini sprint for the team

112
00:06:03,747 --> 00:06:06,164
several members contributed
for this

113
00:06:06,474 --> 00:06:08,689
to try to provide all contributors

114
00:06:08,789 --> 00:06:11,409
people who can vote in Debian,

115
00:06:11,815 --> 00:06:14,134
a French version of the platforms

116
00:06:14,660 --> 00:06:16,180
and also the results at the end
of the vote.

117
00:06:16,390 --> 00:06:20,322
That's a pretty intense work during
a very short period of time.

118
00:06:24,657 --> 00:06:27,680
We also translate the documentation

119
00:06:27,917 --> 00:06:30,839
because it's really important
for users.

120
00:06:31,266 --> 00:06:36,105
Of course, we translate the documentation
which comes with

121
00:06:36,318 --> 00:06:37,828
Debian-specific software.

122
00:06:39,439 --> 00:06:42,968
An other subject that will soon be topical,

123
00:06:43,076 --> 00:06:45,095
we're currently translating
the release notes.

124
00:06:47,615 --> 00:06:50,133
Everything you will find
when installing Buster,

125
00:06:51,946 --> 00:06:54,163
if you're interesting in having
a preview of what to expect,

126
00:06:54,566 --> 00:06:55,776
you can come help us.

127
00:06:55,877 --> 00:06:58,802
I, for instance, know all the potential
issues I'll encounter

128
00:06:59,003 --> 00:07:03,335
when I will migrate, and that's interesting
to have such a head start.

129
00:07:04,745 --> 00:07:09,181
But we also do all other docs,
like the Debian Developer's Reference.

130
00:07:10,792 --> 00:07:14,420
It's a good way to learn more
about

131
00:07:14,722 --> 00:07:18,145
how packages are built and what
you can do.

132
00:07:22,175 --> 00:07:25,803
Also, I've been told that
there are package in Debian

133
00:07:26,408 --> 00:07:28,422
that's a lot (bad pun in French)

134
00:07:29,644 --> 00:07:31,357
And those packages have a description.

135
00:07:31,458 --> 00:07:33,374
Before installing something,
you can look at

136
00:07:33,477 --> 00:07:35,901
what to install

137
00:07:37,010 --> 00:07:38,922
you type "apt search",

138
00:07:39,341 --> 00:07:40,753
have some results that interest you

139
00:07:40,965 --> 00:07:42,173
"apt show" to look what it is.

140
00:07:42,381 --> 00:07:45,707
And then, you have a short description
and a longer one.

141
00:07:47,924 --> 00:07:53,564
What we try to do, more or less
successfully

142
00:07:54,070 --> 00:07:56,185
is to translate all those descriptions.

143
00:07:56,691 --> 00:08:00,726
As you can see, there are currently
about 59,000 descriptions.

144
00:08:03,146 --> 00:08:07,577
In French, we have… 18000

145
00:08:07,983 --> 00:08:10,108
Well, about 19,000.

146
00:08:10,249 --> 00:08:13,072
There's still work to do, because like
for the web site,

147
00:08:13,172 --> 00:08:17,905
It's a moving target, because
when packages are uptated,

148
00:08:18,117 --> 00:08:22,153
their descriptions can get updated
as well.

149
00:08:22,355 --> 00:08:24,874
Currently it's a little calmer
because of the freeze

150
00:08:24,974 --> 00:08:26,988
so there are less updates

151
00:08:27,491 --> 00:08:29,308
but we know that as soon as
Buster is released

152
00:08:29,509 --> 00:08:31,425
everybody will restart to send
stuff to unstable

153
00:08:31,626 --> 00:08:33,238
and we'll be completely overwhelmed.

154
00:08:35,986 --> 00:08:41,226
We'll show you the translation and
review process later

155
00:08:43,039 --> 00:08:44,862
but we give details here for
package descriptions because

156
00:08:45,168 --> 00:08:46,378
it's done somewhere else.

157
00:08:47,001 --> 00:08:51,832
There's a tool for that, DDTP, and its
web interface, DDTSS.

158
00:08:52,535 --> 00:08:55,960
That's a thing for which you can
spend only

159
00:08:56,162 --> 00:08:57,472
5 or 10 minutes a day.

160
00:08:58,795 --> 00:09:02,319
You register, go check translations
in progress,

161
00:09:03,124 --> 00:09:04,234
review one or two of them,

162
00:09:04,435 --> 00:09:06,655
say "Yep, it's ok",
"Nope, forgot a semicolon there"

163
00:09:07,378 --> 00:09:09,594
and you're done.
Then, if you're motivated

164
00:09:09,701 --> 00:09:12,827
you can spend more time on it,
as you wish.

165
00:09:15,860 --> 00:09:19,381
Even if we'd like to, we do not
translate everything

166
00:09:20,996 --> 00:09:23,412
and we do not try to achive that,
in particular

167
00:09:24,318 --> 00:09:28,045
we do not work on software already
translated upstream

168
00:09:28,857 --> 00:09:30,678
because that would be redundant

169
00:09:31,001 --> 00:09:34,831
and we're already quite busy with
what we translate.

170
00:09:36,351 --> 00:09:40,596
That's the kind of software not
translated by us

171
00:09:40,928 --> 00:09:46,384
mutt, firefox, wget…
That's a lot, actually.

172
00:09:46,889 --> 00:09:51,629
But, sometimes, there are
exceptions to this rule

173
00:09:52,333 --> 00:09:54,054
for instance, "anattended"

174
00:09:54,477 --> 00:09:57,397
It's not a native Debian package,

175
00:09:58,028 --> 00:09:59,850
it's hosted on Github.

176
00:10:00,370 --> 00:10:03,998
Recently, I uploaded its translation
directly in Github.

177
00:10:04,319 --> 00:10:07,352
In this case, we bypassed the usual

178
00:10:07,779 --> 00:10:09,995
Debian process.

179
00:10:10,326 --> 00:10:12,844
We, translators, still used the mailing list

180
00:10:13,075 --> 00:10:16,197
for coordination, reviews
and so on,

181
00:10:16,601 --> 00:10:19,120
but after that, we do not develop
those packages

182
00:10:19,323 --> 00:10:21,240
We're happy to use them in Debian

183
00:10:22,345 --> 00:10:26,376
Manpages is also a good example, because
there's a lot of work

184
00:10:27,091 --> 00:10:28,602
for manuals.

185
00:10:29,508 --> 00:10:31,725
To give you some details about the
manpages,

186
00:10:32,147 --> 00:10:36,494
a cross-distribution project, called
perkamon

187
00:10:36,916 --> 00:10:41,248
aims at translating the manpages
into French

188
00:10:41,664 --> 00:10:44,885
It had less success recently

189
00:10:45,087 --> 00:10:46,497
it has been a lot less active

190
00:10:47,009 --> 00:10:52,049
and one member from our team

191
00:10:52,250 --> 00:10:53,861
reached out to them and asked

192
00:10:54,086 --> 00:10:57,117
"How is it going? Do you need help?"

193
00:10:57,320 --> 00:11:02,461
And I believe that they simply gave him
control over the git repo

194
00:11:02,861 --> 00:11:03,773
and that's it.

195
00:11:04,184 --> 00:11:05,297
And since I helped him a little.

196
00:11:05,599 --> 00:11:07,209
He also gave me access to the
git repo

197
00:11:07,411 --> 00:11:09,829
and so, without really wanting it,
we became our own upstream.

198
00:11:11,138 --> 00:11:11,944
This kind of things happen

199
00:11:12,346 --> 00:11:14,661
so be careful when you asked people
for news,

200
00:11:14,710 --> 00:11:16,935
sometimes they just give you the keys.

201
00:11:21,468 --> 00:11:23,684
If only it was the only difficulty…
but there are more

202
00:11:23,888 --> 00:11:25,499
That's one of them, indeed,

203
00:11:25,701 --> 00:11:27,918
that a l10n can encounter

204
00:11:29,025 --> 00:11:31,848
If fact, this topic of scope,
where to start, where to stop

205
00:11:32,052 --> 00:11:33,767
is a first difficulty

206
00:11:34,169 --> 00:11:36,287
Another one is also the debates about

207
00:11:36,489 --> 00:11:38,808
the cohesion of translation

208
00:11:39,009 --> 00:11:41,947
because, of course, since we're a lot…
well, not that much

209
00:11:42,147 --> 00:11:43,859
but still, several people

210
00:11:44,162 --> 00:11:49,400
everybody translates with their own
sensitivity

211
00:11:50,006 --> 00:11:52,925
and there are also some heated
discussions about rules in French

212
00:11:53,126 --> 00:11:55,444
where to put dashes, where to
put non breakable spaces,

213
00:11:55,646 --> 00:11:57,961
medium dots, and so on.

214
00:11:58,365 --> 00:12:01,691
Of course, every time the team
settles on something

215
00:12:02,096 --> 00:12:05,217
it also means working to keep
the whole consistent

216
00:12:06,022 --> 00:12:08,647
So cohesion of translations is
a real issue

217
00:12:08,948 --> 00:12:13,278
in particular with the review
processes

218
00:12:13,681 --> 00:12:15,695
and the number of things that
we have to translate

219
00:12:15,897 --> 00:12:17,309
it's a real challenge.

220
00:12:18,720 --> 00:12:20,736
For instance, when we translate packages

221
00:12:21,746 --> 00:12:23,271
a "fun" thing to do is

222
00:12:23,473 --> 00:12:26,090
to make the jargon of specific fields
your own.

223
00:12:26,694 --> 00:12:28,823
For instance, it's really nice
to translate packages about

224
00:12:28,923 --> 00:12:31,448
astronomy, maths, biology, etc.

225
00:12:31,549 --> 00:12:33,880
It's especially nice when you have
never seen that in your life

226
00:12:33,981 --> 00:12:34,889
you read things…

227
00:12:35,112 --> 00:12:37,838
In OpenSSL, I read something,
"elliptic curve"

228
00:12:39,657 --> 00:12:41,987
Interesting, it's translated
"courbe elliptique", apparently.

229
00:12:42,188 --> 00:12:44,003
Don't ask me what it means,
I have no clue.

230
00:12:44,506 --> 00:12:45,521
But at least we translate.

231
00:12:45,823 --> 00:12:49,349
And there is also a real challenge
about the scope of translations

232
00:12:49,660 --> 00:12:53,186
in the coordination part,
because there can be

233
00:12:53,287 --> 00:12:55,003
a gab, from time to time

234
00:12:55,203 --> 00:12:57,217
between the translator

235
00:12:57,525 --> 00:13:01,053
the package maintainer in Debian

236
00:13:01,154 --> 00:13:03,883
who does not necessarily care
about its localization

237
00:13:04,288 --> 00:13:07,817
and upstream developers who
can also expercience a mismatch

238
00:13:07,917 --> 00:13:10,751
between the upstream version,
the version in Debian

239
00:13:10,958 --> 00:13:12,471
and the version translated
by the translator.

240
00:13:12,775 --> 00:13:16,010
All of this requires coordination
on many levels

241
00:13:16,312 --> 00:13:19,737
and this is not always
an easy task.

242
00:13:21,249 --> 00:13:24,589
That's it for the difficulties that
we handle mainly by e-mail

243
00:13:24,995 --> 00:13:27,931
That's how we keep track
of everything.

244
00:13:28,333 --> 00:13:32,972
We have a bot which analyses
e-mails subjects

245
00:13:33,073 --> 00:13:34,987
that's why they have a specific
syntax

246
00:13:35,087 --> 00:13:36,304
that we'll see later.

247
00:13:37,413 --> 00:13:40,435
We have to monitor translations,

248
00:13:40,663 --> 00:13:43,886
know at which stage of the review
process they are,

249
00:13:44,897 --> 00:13:46,005
that's the purpose of the bot.

250
00:13:46,422 --> 00:13:50,259
It shows us when a translation
needs to be updated,

251
00:13:51,066 --> 00:13:54,693
that's why we communicate
using a language that

252
00:13:54,796 --> 00:13:58,426
it understands, it allows us
to track translations more easily

253
00:13:58,531 --> 00:13:59,845
from our mailbox

254
00:13:59,957 --> 00:14:01,569
which is very convenient

255
00:14:01,889 --> 00:14:04,812
and to remember the status
of our own translations.

256
00:14:05,535 --> 00:14:09,160
It requires a series of steps
that we can detail

257
00:14:09,664 --> 00:14:12,687
that translate into some kind
of codification

258
00:14:13,807 --> 00:14:15,136
which looks a little complex,
at first sight

259
00:14:15,250 --> 00:14:18,085
but then, let's look at it together,
it's not that hard.

260
00:14:18,486 --> 00:14:19,997
All you need to know

261
00:14:20,204 --> 00:14:22,019
is that there are several
stages in the process,

262
00:14:23,028 --> 00:14:24,731
one where we say…

263
00:14:27,074 --> 00:14:27,978
Ok, do it

264
00:14:29,085 --> 00:14:30,504
Alban is switching screen, there.

265
00:14:30,707 --> 00:14:34,234
Here's an excerpt of what
happened on the list in April

266
00:14:34,939 --> 00:14:35,846
I think… yep that's it.

267
00:14:36,855 --> 00:14:40,478
At first, we had a slide to explain

268
00:14:40,579 --> 00:14:42,298
the meaning of all this,

269
00:14:44,212 --> 00:14:46,730
the codes that you can see at
the beginning of subjects.

270
00:14:46,936 --> 00:14:49,356
And then we thought
"It's too much, we're going to scare them away."

271
00:14:49,770 --> 00:14:51,280
"Let's show them the list instead."

272
00:14:51,920 --> 00:14:54,343
On second thoughts, I'm not sure if…

273
00:14:55,048 --> 00:14:56,258
It's worst, actually.

274
00:15:00,301 --> 00:15:01,611
Typically…

275
00:15:03,323 --> 00:15:04,429
There, you have a simple one.

276
00:15:04,732 --> 00:15:05,338
There we go.

277
00:15:06,055 --> 00:15:11,999
So, usually, the review process
starts with a subject

278
00:15:12,302 --> 00:15:18,161
in RFR, Request for Review,
and in this one,

279
00:15:18,475 --> 00:15:23,912
Jean-Paul said "I've just updated
the translation of ddp.wml"

280
00:15:24,114 --> 00:15:28,042
so, a page about documentation

281
00:15:29,365 --> 00:15:30,876
"What do you think of it?"

282
00:15:31,290 --> 00:15:36,527
In this case, he didn't have an answer,
so he sent a LCFC later

283
00:15:36,760 --> 00:15:39,380
a Last Call for Comments, saying

284
00:15:39,699 --> 00:15:43,427
"I'm going to stop this review soon
if nobody has comments."

285
00:15:43,540 --> 00:15:45,571
And since nobody did, he concluded
"I consider it's ok,

286
00:15:45,890 --> 00:15:48,814
so this review is DONE and I stop
this thread,

287
00:15:48,915 --> 00:15:51,043
the translation has been approved."

288
00:15:51,551 --> 00:15:56,414
Just to reassure you, maybe nobody
answered him

289
00:15:56,514 --> 00:15:59,435
but usually, when we do not spot
errors during review,

290
00:15:59,536 --> 00:16:01,855
we answer off-list, to not add
to the already large volume of messages

291
00:16:01,955 --> 00:16:03,264
and say "It's ok for me."

292
00:16:05,981 --> 00:16:09,706
An example a little more…
Oh wait, it's the same.

293
00:16:10,225 --> 00:16:12,360
What did happen? Was there a problem
with the pseudo-URL?

294
00:16:12,965 --> 00:16:13,982
You've got two there.

295
00:16:15,090 --> 00:16:16,903
Ok, no big deal, let's pretend
it's a different thread

296
00:16:17,807 --> 00:16:18,816
it works the same.

297
00:16:20,232 --> 00:16:23,555
So, RFR again, "I translated this
or updated this translation,

298
00:16:23,655 --> 00:16:24,565
what's your opinion on this?"

299
00:16:24,874 --> 00:16:26,485
There, an other contributor
answers

300
00:16:26,899 --> 00:16:30,834
"You forgot an 's' here" or
"You used a dot instead

301
00:16:31,037 --> 00:16:32,849
of a semi-colon." or something
similar.

302
00:16:33,859 --> 00:16:35,969
The answer is then
"Yes indeed,

303
00:16:36,172 --> 00:16:39,196
here is an update of the
translation

304
00:16:40,002 --> 00:16:41,929
this is a new call for review."

305
00:16:42,132 --> 00:16:43,442
Someone else says

306
00:16:43,644 --> 00:16:45,457
"Wait, you missed something else."

307
00:16:46,165 --> 00:16:49,690
And so on, until after a few days

308
00:16:49,891 --> 00:16:51,807
we think we waited long enough

309
00:16:51,925 --> 00:16:53,234
or got enough feedback

310
00:16:53,965 --> 00:16:57,692
so LCFC and then the process
is complete.

311
00:16:58,400 --> 00:17:00,230
Could you find a MAJ?

312
00:17:03,262 --> 00:17:06,284
In this case, when the thread
starts with a RFR,

313
00:17:06,614 --> 00:17:12,959
it means the translator took the initiative
to look at what was missing

314
00:17:14,068 --> 00:17:17,998
and said "Well, this package, this page
that I maintain is outdated."

315
00:17:18,217 --> 00:17:22,159
or "This announcement has been published,
I'll handle its translation

316
00:17:22,265 --> 00:17:23,575
and do it right now."

317
00:17:24,405 --> 00:17:26,320
But sometimes, like here

318
00:17:28,030 --> 00:17:28,936
It's actually a "Re:" for a MAJ.

319
00:17:29,144 --> 00:17:30,959
No, it's ok, we can see it.

320
00:17:32,077 --> 00:17:33,994
We also do coordination, and
from time to time

321
00:17:34,313 --> 00:17:36,229
we send MAJ messages so say

322
00:17:36,430 --> 00:17:42,679
"Hey, you maintain this page
or this package or this doc.

323
00:17:43,690 --> 00:17:45,507
I noticed that it's not
up to date anymore,

324
00:17:46,111 --> 00:17:49,335
so here's the new version to translate.
Do you want to take care of it?"

325
00:17:50,342 --> 00:17:54,978
Then, the person either sends an ITT,
Intent to Translate,

326
00:17:55,389 --> 00:17:59,829
"Yes, I'm willing to pass the
torch to… well, myself actually.

327
00:18:00,636 --> 00:18:03,359
Give me some time, I'll update
the translation."

328
00:18:03,764 --> 00:18:06,687
A little while after, a RFR is sent
to start a new thread

329
00:18:06,916 --> 00:18:07,923
and so on.

330
00:18:08,427 --> 00:18:09,948
If the maintainer can't do that, he
simply answers "I can't."

331
00:18:10,154 --> 00:18:14,793
and the translation is available for
someone else to pick up.

332
00:18:18,517 --> 00:18:22,345
All the rest here is a complicated
pseudo-URL.

333
00:18:24,065 --> 00:18:26,682
I think that now we all manage
to understand them.

334
00:18:27,011 --> 00:18:29,528
It's mainly to help the bot
which crawls the list

335
00:18:29,840 --> 00:18:32,156
and updates coordination pages
to say

336
00:18:32,366 --> 00:18:38,110
"This page, this manpage is currently
under review."

337
00:18:38,331 --> 00:18:41,271
That way, we can have
a good overview

338
00:18:41,786 --> 00:18:45,411
and not interfere in
ongoing translations.

339
00:18:46,732 --> 00:18:49,149
What's interesting with MAJs,

340
00:18:49,753 --> 00:18:51,969
is that we do not
necessarily send them

341
00:18:52,070 --> 00:18:53,686
to team members that we know

342
00:18:53,787 --> 00:18:55,404
and who contribute on a
regular basis,

343
00:18:55,705 --> 00:18:57,215
we'll send them a ping,
a short message

344
00:18:57,336 --> 00:18:59,470
"Hey, don't forget to update
this and this packages."

345
00:19:01,426 --> 00:19:03,945
Here, it's really for people
who have stopped

346
00:19:04,166 --> 00:19:06,380
or are just MIA.

347
00:19:06,595 --> 00:19:11,830
Like Thomas said, this MAJ is
the ping and a waiting period.

348
00:19:12,845 --> 00:19:16,275
It allows us, in the
statistics pages,

349
00:19:16,389 --> 00:19:18,511
to know which translation
needs to be adopted.

350
00:19:18,723 --> 00:19:21,141
We reached the maintainer
once, twice,

351
00:19:21,341 --> 00:19:22,656
usually it's at least twice

352
00:19:22,857 --> 00:19:24,672
and then we know that this
translation is available for adoption.

353
00:19:25,984 --> 00:19:29,108
There's also an interesting
detail here.

354
00:19:29,259 --> 00:19:32,380
There's a DONE to close
a thread.

355
00:19:33,185 --> 00:19:35,303
The DONE is because we are going to,

356
00:19:35,408 --> 00:19:39,338
well, the person who sent it,
will push the revision themselves.

357
00:19:39,540 --> 00:19:42,258
There, it's wml, so it goes directly
on Salsa.

358
00:19:42,988 --> 00:19:46,047
The file has been pushed directly
on Salsa by Jean-Pierre.

359
00:19:47,176 --> 00:19:49,995
When we do not have the needed
permissions to do the upload

360
00:19:50,600 --> 00:19:52,211
we close the thread with a BTS.

361
00:19:52,544 --> 00:19:56,482
Here, Quentin, who's in the back of the room,
sent a BTS

362
00:19:56,886 --> 00:20:01,317
because he sent his package, his .po file
in a bug report

363
00:20:01,628 --> 00:20:03,744
directly on the po-debconf package

364
00:20:03,948 --> 00:20:07,474
and then, it's up to the package maintainer
to include it

365
00:20:07,700 --> 00:20:10,427
into its archive.

366
00:20:10,932 --> 00:20:14,358
It's a small nuance in the way
to close threads,

367
00:20:14,563 --> 00:20:15,977
it's either a DONE or a BTS.

368
00:20:16,293 --> 00:20:20,121
Either we do it ourselves or we delegate
it through a bug report.

369
00:20:27,988 --> 00:20:29,199
So, how to contribute.

370
00:20:30,215 --> 00:20:31,826
Do not worry, it's very simple.

371
00:20:32,230 --> 00:20:33,245
First of all,

372
00:20:33,463 --> 00:20:36,182
if you see a mistake
in a translation,

373
00:20:36,405 --> 00:20:37,615
really anywhere,

374
00:20:37,943 --> 00:20:41,569
please report it to us, or if
a translation is missing

375
00:20:42,098 --> 00:20:44,819
while it would be really useful
for users

376
00:20:45,025 --> 00:20:46,034
if it was translated.

377
00:20:46,337 --> 00:20:47,446
We try to do our best.

378
00:20:48,164 --> 00:20:49,384
The goal is really to have

379
00:20:49,804 --> 00:20:52,621
a base installation as accessible
as possible

380
00:20:52,929 --> 00:20:54,742
translation-wise.

381
00:20:55,168 --> 00:20:57,787
So, if you do a fresh install,

382
00:20:58,219 --> 00:20:59,930
the ideal result is to have
everything translated.

383
00:21:00,242 --> 00:21:01,652
If things are missing, please
let us know.

384
00:21:02,255 --> 00:21:04,675
Also, if you see mistakes,

385
00:21:05,180 --> 00:21:07,202
send us a message on
the mailing list

386
00:21:07,622 --> 00:21:09,238
debian-l10n-french@lists.debian.org

387
00:21:09,452 --> 00:21:11,063
you'll have an answer
very quickly

388
00:21:11,228 --> 00:21:13,542
or use IRC, we'll answer
even faster.

389
00:21:14,650 --> 00:21:18,477
In any case, there are quite a number
of active people.

390
00:21:19,584 --> 00:21:21,096
Within a day, you're sure to have
an answer,

391
00:21:21,299 --> 00:21:23,827
at least to say
"We'll handle that."

392
00:21:24,331 --> 00:21:25,746
And it really helps us.

393
00:21:26,458 --> 00:21:28,182
It really is an important contribution.

394
00:21:30,099 --> 00:21:34,429
Otherwise, to really play a role
in translations themselves

395
00:21:35,262 --> 00:21:37,175
subscribe to the mailing list

396
00:21:38,794 --> 00:21:39,904
and once you did it,

397
00:21:40,211 --> 00:21:43,634
you can start to read and proofread
all the messages.

398
00:21:44,248 --> 00:21:47,880
All the subjects that Thomas showed
earlier

399
00:21:48,289 --> 00:21:49,697
will start to make sense to you.

400
00:21:50,099 --> 00:21:51,609
At first, I agree that it's not obvious.

401
00:21:51,709 --> 00:21:54,530
Some web pages explain that
really well.

402
00:21:55,750 --> 00:21:58,267
But when you get it, you get it.

403
00:21:58,677 --> 00:22:01,199
When people start and do not know,
it happened,

404
00:22:02,128 --> 00:22:03,845
it's always difficult at first.

405
00:22:04,876 --> 00:22:07,811
So, proofreading, following what
happens on the list

406
00:22:08,214 --> 00:22:09,725
will help you to get a grasp
of how it works

407
00:22:11,535 --> 00:22:13,563
and then you'll be able to
review translations

408
00:22:14,076 --> 00:22:17,399
take someone's translation,
have a look at it

409
00:22:17,803 --> 00:22:20,424
fixing mistakes, if any,

410
00:22:20,726 --> 00:22:21,934
directly in the file

411
00:22:22,249 --> 00:22:24,775
make a diff, send it to
the list

412
00:22:25,594 --> 00:22:28,413
and then, the translator who
started the thread

413
00:22:28,616 --> 00:22:31,640
will apply your patch to
the translation

414
00:22:31,762 --> 00:22:35,696
and send it in a RFR2
to start a new review process.

415
00:22:36,810 --> 00:22:39,544
Or you can also translate
package descriptions

416
00:22:39,768 --> 00:22:43,094
on the DDTSS site.

417
00:22:43,700 --> 00:22:45,614
So it's either the list or that,

418
00:22:45,922 --> 00:22:47,636
but the list is kind of cool,
because

419
00:22:47,737 --> 00:22:50,564
you communicate with people,
see who's in the list,

420
00:22:51,167 --> 00:22:52,982
really nice people.

421
00:22:54,110 --> 00:22:57,732
It's nice, it's the first time we were
so many to meet, yesterday.

422
00:22:58,458 --> 00:22:59,665
It's interesting.

423
00:23:00,976 --> 00:23:02,487
So, proofread, and of course
translate.

424
00:23:03,008 --> 00:23:05,829
It's ok to wait a little to see
how it works

425
00:23:06,662 --> 00:23:09,582
see the little habits to have

426
00:23:09,792 --> 00:23:12,819
where to put non-breakable spaces,
before question marks

427
00:23:13,022 --> 00:23:14,030
colons, and so on.

428
00:23:14,332 --> 00:23:16,651
All these small details really
disturbed me at first

429
00:23:17,355 --> 00:23:19,066
it's indeed difficult,
or

430
00:23:19,193 --> 00:23:21,811
"No, don't use this wording, because
if you do it here,

431
00:23:22,015 --> 00:23:25,134
we'll have to change it in 40,000
other packages. So please don't."

432
00:23:26,162 --> 00:23:29,383
So look at things from a distance
at the beginning,

433
00:23:30,315 --> 00:23:33,139
help by doing proofreads, that's
a really good start,

434
00:23:33,540 --> 00:23:34,747
it helps a lot.

435
00:23:35,477 --> 00:23:37,894
And after a while, when you'll
see TAFs

436
00:23:38,931 --> 00:23:41,452
you'll throw yourself into it
and say

437
00:23:41,777 --> 00:23:43,086
"Ok, I'm ready."

438
00:23:43,389 --> 00:23:46,207
If no TAFs are sent, which
can happen

439
00:23:46,413 --> 00:23:49,036
when there is no update
or we don't

440
00:23:49,141 --> 00:23:50,355
propose such updates,

441
00:23:50,558 --> 00:23:52,878
feel free to declare yourself
on the mailing list and say

442
00:23:53,080 --> 00:23:56,503
"I'd like to help, how can I do?"

443
00:23:56,913 --> 00:23:59,128
We're here to help you

444
00:23:59,632 --> 00:24:01,445
and it's with great pleasure.

445
00:24:02,049 --> 00:24:05,977
If you're more interested in
short term contribution

446
00:24:06,099 --> 00:24:10,848
or less time consuming
contributions,

447
00:24:11,154 --> 00:24:14,478
packages description can be
a good start.

448
00:24:14,584 --> 00:24:16,900
I've never done it yet

449
00:24:17,018 --> 00:24:19,840
we talked about that yesterday, and also
did a while ago.

450
00:24:27,371 --> 00:24:29,686
Let's finish quickly.

451
00:24:31,119 --> 00:24:34,744
Just for posterity, when you'll watch
these slides and wonder

452
00:24:34,845 --> 00:24:36,567
"How can I contribute?"

453
00:24:38,282 --> 00:24:41,202
here are some links to
monitoring pages.

454
00:24:41,404 --> 00:24:45,939
Those are basically the result of what
the bot sees on the list.

455
00:24:46,542 --> 00:24:48,154
Do you want me to show one?

456
00:24:48,218 --> 00:24:49,654
Yes, you can show one as an example.

457
00:24:50,357 --> 00:24:52,577
Don't be scared, it's really
colorful.

458
00:24:53,282 --> 00:24:55,305
Debconf screens for instance,
it's really simple.

459
00:24:56,214 --> 00:24:58,836
And it's a good news, because
it's often from there

460
00:24:59,037 --> 00:25:02,163
that you'll intuitively get the
pseudo-URLs you just saw

461
00:25:02,370 --> 00:25:04,383
in the mailing list, they are
actually here.

462
00:25:04,685 --> 00:25:06,107
So no need to rack you brain
more than that.

463
00:25:06,419 --> 00:25:09,744
It's not done by the coordinator
using the attachment,

464
00:25:09,946 --> 00:25:11,665
it's done via the mail subject
that he wrote,

465
00:25:11,867 --> 00:25:16,603
and you can see what match with
the URLs

466
00:25:17,712 --> 00:25:20,446
that go after RFR, TAF, ITT, etc.

467
00:25:21,758 --> 00:25:26,095
What you can see on this example
is that we're mainly in the green

468
00:25:26,700 --> 00:25:32,553
and that for two out of the three
examples that are not green,

469
00:25:32,866 --> 00:25:34,277
we're already on it.

470
00:25:34,695 --> 00:25:37,518
The grey one, down below,
is 0% translated

471
00:25:37,720 --> 00:25:39,940
just because it's a new screen

472
00:25:40,372 --> 00:25:43,011
and there's already a bug report

473
00:25:43,224 --> 00:25:47,259
with the new translation,
and for the one at the top,

474
00:25:47,460 --> 00:25:49,275
there's also an open bug report

475
00:25:49,476 --> 00:25:51,492
so we just need to take care
of x2goserver,

476
00:25:53,633 --> 00:25:55,545
Jean-Pierre (x2go's translator, in the room),
we're waiting!

477
00:25:55,882 --> 00:26:01,818
To contact us, you can send
an e-mail to this address

478
00:26:02,360 --> 00:26:04,174
you can come on IRC, obviously.

479
00:26:05,197 --> 00:26:08,018
Soon, maybe, you'll even be able
to report bugs against a metapackage

480
00:26:08,321 --> 00:26:11,745
we're thinking about making one
for french localization

481
00:26:12,348 --> 00:26:16,074
to make bug reporting easier
for you

482
00:26:16,697 --> 00:26:19,231
when you use Debian in French.

483
00:26:19,936 --> 00:26:23,968
And because we're aware of the real
stake about humanization,

484
00:26:24,270 --> 00:26:26,992
that is, it's really hard to put
you into documentation by yourself.

485
00:26:27,193 --> 00:26:30,921
In Debian, we're used to that,
but some people cannot.

486
00:26:31,726 --> 00:26:32,934
Some of them take 15 years
to make it.

487
00:26:33,852 --> 00:26:35,377
I'm not thinking of anyone
right now.

488
00:26:38,306 --> 00:26:40,523
What often unlocks the situation
is to meet in real life

489
00:26:40,754 --> 00:26:41,664
like what we're doing here,

490
00:26:41,988 --> 00:26:45,513
or on Debian France booths
at FLOSS events

491
00:26:45,729 --> 00:26:47,850
where it's often the l10n team
who comes,

492
00:26:48,377 --> 00:26:50,292
and so it's often a nice
entry point.

493
00:26:50,800 --> 00:26:52,613
Come talk to us, ask us
how it works.

494
00:26:52,918 --> 00:26:54,541
Come ask us to explain
this jargon

495
00:26:55,048 --> 00:26:56,066
because we have our own.

496
00:26:56,569 --> 00:26:59,491
It will be with great pleasure and
since we're here today and tomorrow,

497
00:26:59,902 --> 00:27:02,016
come, do not hesitate,
come, come

498
00:27:02,519 --> 00:27:05,345
and we'll answer to all your questions
with great pleasure.

499
00:27:05,547 --> 00:27:09,279
Now you know that there are
tens of thousands,

500
00:27:09,482 --> 00:27:11,717
maybe hundreds of thousands
of things to translate in Debian.

501
00:27:12,435 --> 00:27:14,047
So every contribution is welcome

502
00:27:14,249 --> 00:27:17,778
because the team is only made
of a dozen of people,

503
00:27:18,186 --> 00:27:25,236
5 of which are really active.

504
00:27:25,843 --> 00:27:29,973
So, clearly, every support,
whatever how small,

505
00:27:30,187 --> 00:27:32,013
even one package description
or two,

506
00:27:32,214 --> 00:27:34,633
even simple reviews, it's…

507
00:27:35,036 --> 00:27:36,345
Every support is welcome.

508
00:27:36,953 --> 00:27:39,169
Don't forget that there are other
translators in the room,

509
00:27:39,471 --> 00:27:42,592
they're hiding, but they're here with us.

510
00:27:42,814 --> 00:27:45,133
Some of them are among the most
active ones.

511
00:27:49,061 --> 00:27:50,875
That's it, thanks.

512
00:28:01,374 --> 00:28:03,386
We have time for some questions.

513
00:28:04,336 --> 00:28:07,219
We also take questions in English
if you want.

514
00:28:17,502 --> 00:28:22,650
[Question] How much time does it take to…
say, immerse yourself

515
00:28:22,973 --> 00:28:25,491
and be able to start small
translations, at the beginning?

516
00:28:27,304 --> 00:28:28,412
[Jean-Phillipe] 15 years?

517
00:28:29,837 --> 00:28:32,254
[Alban] If you don't dare come to the list,

518
00:28:32,560 --> 00:28:33,971
it can take 15 years, indeed.

519
00:28:34,274 --> 00:28:38,016
But if you go to the list,
come meet people,

520
00:28:38,231 --> 00:28:39,037
talk to them,

521
00:28:39,238 --> 00:28:41,151
even send an e-mail to
introduce yourself,

522
00:28:41,462 --> 00:28:42,773
say "Hey, I'm here."

523
00:28:42,996 --> 00:28:44,103
I didn't do it at first,

524
00:28:44,334 --> 00:28:45,652
I didn't introduce myself when
I subscribed

525
00:28:45,961 --> 00:28:48,379
so I followed the list
for several months.

526
00:28:49,608 --> 00:28:51,019
I was very quiet, wondering

527
00:28:51,226 --> 00:28:53,544
"Should I do a review?"

528
00:28:53,848 --> 00:28:55,962
Then I threw myself in,
started my first review.

529
00:28:56,383 --> 00:28:59,504
You learn how it works,
bit by bit,

530
00:29:00,008 --> 00:29:03,936
and the faster you make contact,
the better.

531
00:29:05,951 --> 00:29:09,886
[Jean-Philippe] When you proofread,
once you've understood

532
00:29:10,124 --> 00:29:11,840
the e-mail subjects syntax
for the bot

533
00:29:12,248 --> 00:29:15,270
and after a few reviews,
for a couple of weeks

534
00:29:15,472 --> 00:29:17,082
you can quickly become
operational

535
00:29:17,305 --> 00:29:19,136
be it only by doing a
package description.

536
00:29:19,454 --> 00:29:21,772
You get reviews and then
you're good to go.

537
00:29:23,499 --> 00:29:25,328
It depends on yourself and the time
you want to invest in it.

538
00:29:27,582 --> 00:29:30,205
In my case, I started with
debconf screens

539
00:29:30,529 --> 00:29:32,242
which are really simple.

540
00:29:32,443 --> 00:29:34,761
It's really short, files are
easy to translate.

541
00:29:35,276 --> 00:29:37,923
It's really good for a start

542
00:29:38,547 --> 00:29:42,168
whereas take a full package,
or the full translation

543
00:29:42,600 --> 00:29:47,837
of the platform of a DPL candidate,

544
00:29:48,145 --> 00:29:49,571
might not be a great idea.

545
00:29:51,383 --> 00:29:54,623
[Jean-Pierre] Juste to complete,
what we totally forgot

546
00:29:54,934 --> 00:29:59,465
while preparing this talk, is that
we also translate the wiki,

547
00:30:00,591 --> 00:30:01,902
and we didn't mention it.

548
00:30:02,707 --> 00:30:05,545
There's a lot of work to
localize the wiki.

549
00:30:05,755 --> 00:30:09,083
It's not monitored, it's a wiki,
you just go and edit.

550
00:30:09,902 --> 00:30:13,528
Nothing is reviewed.
There has been one or two pages

551
00:30:13,737 --> 00:30:18,272
that went through our review process,
but otherwise there are

552
00:30:18,372 --> 00:30:20,388
hundreds of pages to translate

553
00:30:20,800 --> 00:30:23,017
if you think that they'll be useful
and clear

554
00:30:23,227 --> 00:30:25,346
once in the appropriate language.

555
00:30:27,061 --> 00:30:27,866
It's a lot of work.

556
00:30:28,689 --> 00:30:31,309
That's how I started, doing
wiki, wiki, wiki

557
00:30:31,647 --> 00:30:34,072
because it was open,
maybe less intimidating.

558
00:30:35,180 --> 00:30:36,792
There's no proofreading,
it's even less intimidating.

559
00:30:38,206 --> 00:30:39,829
There are only revisions, which
are not the same.

560
00:30:40,139 --> 00:30:42,456
[Alban] The first time I edited the wiki,
I found it interesting

561
00:30:42,988 --> 00:30:45,813
to see and update.

562
00:30:46,115 --> 00:30:48,632
Because you take the source, first,

563
00:30:48,938 --> 00:30:52,261
instead of just translating,
you test the wiki page, read it,

564
00:30:52,463 --> 00:30:54,377
notice mistakes.

565
00:30:54,599 --> 00:30:56,917
Then you fix the upstream version

566
00:30:57,244 --> 00:30:59,374
and translate it afterwards.

567
00:31:07,643 --> 00:31:18,533
Thanks a lot.