- 14 Aug, 2020 1 commit
-
-
emmapeel authored
Currently translated at 93.2% (68 of 73 strings)
-
- 02 Jul, 2020 1 commit
-
-
cbrownstein authored
-
- 15 Apr, 2020 1 commit
-
-
anonym authored
I used this hacky approach: git diff 6b9e13f1^..origin/master -- *.po > lots-of-fuzzy.patch patch -R -p1 < lots-of-fuzzy.patch git commit So I undid all the PO changes of #17005. The idea is to unfuzzy lots-of-fuzzy.patch and then apply this patch instead, and then squash those changes into the "revert" commit we made above, turning it into the commit I'm writing right now. The fuzzy cases I care aboute looke like this: -#, no-wrap -msgid "Online anonymity and censorship circumvention\n" +#, fuzzy, no-wrap +#| msgid "Online anonymity and censorship circumvention\n" +msgid "Online anonymity and censorship circumvention" msgstr "Onlineanonymität und Zensurumgehung\n" and should be transformed into this: #, no-wrap -msgid "Online anonymity and censorship circumvention\n" +msgid "Online anonymity and censorship circumvention" -msgstr "Onlineanonymität und Zensurumgehung\n" +msgstr "Onlineanonymität und Zensurumgehung" Behold this ugly state machine (my favored way of solving these kind of problems in small steps without having to think much about the whole problem): out = open('unfuzzy.patch', 'w') state = 0 fuzzy_buf = '' unfuzzy_buf = '' File.read('lots-of-fuzzy.patch').each_line do |line| line = line.chomp fuzzy_buf += line + "\n" if state == 0 && line == '-#, no-wrap' state = 1 unfuzzy_buf += " #, no-wrap\n" elsif state == 1 && /^-msgid ".*\\n"/.match(line) state = 2 unfuzzy_buf += line + "\n" elsif state == 1 && line == '-msgstr ""' ; elsif state == 2 && line == '+#, fuzzy, no-wrap' state = 3 elsif state == 3 && /^\+#| msgid ".*\\n"/.match(line) state = 4 elsif state == 4 && /^\+msgid ".*"/.match(line) state = 5 unfuzzy_buf += line + "\n" elsif state == 5 && /^ msgstr ".*\\n"/.match(line) state = 6 unfuzzy_buf += "-" + line[1..] + "\n" unfuzzy_buf += "+" + line[1..-4] + '"' + "\n" elsif state == 6 && /^\s*$/.match(line) state = 0 # Eh, so in total the above transformations mean that our hunk # results in one less line, so the diff offset is off by one => # bad patch! So we just add a line that we easily can remove # later. :) unfuzzy_buf += "+########sdf9s7d87fyusdf98sd7f098sd7f09sduf09uj######\n" unfuzzy_buf += line + "\n" out.write(unfuzzy_buf) fuzzy_buf = '' unfuzzy_buf = '' else state = 0 out.write(fuzzy_buf) fuzzy_buf = '' unfuzzy_buf = '' end end Then I applied unfuzzy.patch and used sed to kill the weird lines I had to introduce (see above): pattern="########sdf9s7d87fyusdf98sd7f098sd7f09sduf09uj######" for f in $(git grep -l ${pattern}); do sed -i "/${pattern}/d" ${f} done and squashed, and now we have 1386 fewer fuzzy strings, yay! And po_lint does not complain, which seems like a good sign. :)
-
- 12 Apr, 2020 1 commit
-
-
intrigeri authored
-
- 30 Mar, 2020 1 commit
-
-
gallium69 authored
Currently translated at 93.5% (72 of 77 strings)
-
- 29 Mar, 2020 1 commit
-
-
emmapeel authored
Currently translated at 92.2% (71 of 77 strings)
-
- 22 Mar, 2020 1 commit
-
-
IkiWiki authored
-
- 22 Jan, 2020 1 commit
-
-
ignifugo authored
Currently translated at 96.1% (74 of 77 strings)
-
- 05 Jan, 2020 2 commits
- 23 Oct, 2019 1 commit
-
-
emmapeel authored
Currently translated at 98.7% (76 of 77 strings)
-
- 29 Aug, 2019 2 commits
-
-
sajolida authored
- 20 Jul, 2019 1 commit
-
-
emmapeel authored
Currently translated at 98.7% (76 of 77 strings)
-
- 13 Jul, 2019 1 commit
-
-
emmapeel authored
Currently translated at 98.7% (76 of 77 strings)
-
- 11 Jul, 2019 2 commits
-
-
emmapeel authored
Currently translated at 17.7% (11 of 62 strings) Translation: Tails/wiki/src/news/version_3.14.1.*.po Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_3141po/pt/
-
emmapeel authored
Currently translated at 39.0% (16 of 41 strings) Translation: Tails/wiki/src/news/version_3.11.*.po Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_311po/it/
-
- 30 Jun, 2019 1 commit
-
-
intrigeri authored
During the "scan" phase, ikiwiki first scans raw PO files, including these obsolete strings. We have "[[!command]]" ikiwiki directives split over multiple strings, so in these raw PO files, a directive can be started ("[[!command") but never closed ("]]"), which can cause this warning: Complex regular subexpression recursion limit (32766) exceeded at /usr/share/perl5/IkiWiki.pm line 1754. I suspect that other kinds of power-usage of ikiwiki + PO files can trigger this problem; let's fix this one to start with and see what happens then. refs: #16847
-
- 17 Jun, 2019 1 commit
-
-
Davide authored
Currently translated at 84.4% (65 of 77 strings)
-
- 21 Feb, 2019 1 commit
-
-
IkiWiki authored
-
- 18 Jan, 2019 1 commit
-
-
anonym authored
-
- 29 Dec, 2018 2 commits
-
-
sajolida authored
-
- 18 Dec, 2018 1 commit
-
-
sajolida authored
-
- 15 Dec, 2018 1 commit
-
-
emmapeel authored
-
- 07 Dec, 2018 1 commit
-
-
intrigeri authored
-
- 02 Dec, 2018 1 commit
-
-
emmapeel authored
-
- 22 Nov, 2018 1 commit
-
-
cbrownstein authored
-
- 14 Nov, 2018 1 commit
-
-
emmapeel authored
Currently translated at 93.8% (60 of 64 strings)
-
- 11 Nov, 2018 3 commits
- 07 Nov, 2018 1 commit
-
-
sajolida authored
-
- 26 Oct, 2018 1 commit
-
-
emmapeel authored
-
- 24 Oct, 2018 2 commits
- 20 Aug, 2018 1 commit
-
-
sajolida authored
-
- 31 May, 2018 1 commit
-
-
sajolida authored
-
- 27 Apr, 2018 1 commit
-
-
emmapeel authored
Currently translated at 92.1% (59 of 64 strings)
-
- 24 Apr, 2018 1 commit
-
-
amnesia authored
-