@@ -59,15 +59,16 @@ Once most diagnostic messages have been ported to the new infrastructure, then
59
59
the diagnostics working group will start creating a workflow for translation
60
60
teams to translate all of the diagnostic messages to different languages.
61
61
62
- Every pull request related to diagnostic translation is listed [ in this
63
- document ] ( https://hackmd.io/@davidtwco/rkXSbLg95 ) .
62
+ Every pull request related to diagnostic translation is tagged with
63
+ [ ` A-translation ` ] [ A-translation ] .
64
64
65
65
## Getting involved
66
66
There's a lot of work to do on diagnostic translation, but the good news is that
67
67
lots of the work can be done in parallel, and it doesn't require background in
68
68
compiler development or familiarity with ` rustc ` to contribute!
69
69
70
- If you are interested, feel free to just get started! You can ask for help in
70
+ ** If you are interested in getting involved, take a look at [ #100717 ] to find
71
+ out where to get started!** You can ask for help in
71
72
[ ` #t-compiler/wg-diagnostics ` ] or reach out to [ ` @davidtwco ` ] .
72
73
73
74
** Note:** This post isn't going to be updated as the working group iterates on
@@ -299,6 +300,7 @@ r? rust-lang/diagnostics
299
300
300
301
Even if you aren't sure exactly how to proceed, give it a go and you can ask
301
302
for help in [ ` #t-compiler/wg-diagnostics ` ] or reach out to [ ` @davidtwco ` ] .
303
+ Check out [ #100717 ] for guidance on where to get started!
302
304
303
305
## FAQ
304
306
@@ -334,3 +336,4 @@ decided yet.
334
336
[ diag_translation ] : https://rustc-dev-guide.rust-lang.org/diagnostics/translation.html
335
337
[ fluent ] : http://projectfluent.org/
336
338
[ A-translation ] : https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3AA-translation+sort%3Aupdated-desc
339
+ [ #100717 ] : https://github.com/rust-lang/rust/issues/100717
0 commit comments