i18n-bugs July 2021

i18n-bugs@lists.fedoraproject.org

1 participants
66 discussions

[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1733869 Bug ID: 1733869 Summary: gettext: Getting errors in double free with msgfmt command. Product: Fedora Version: 30 Status: NEW Component: gettext Assignee: panovotn(a)redhat.com Reporter: poyadav(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jjanco(a)redhat.com, nphilipp(a)redhat.com, panovotn(a)redhat.com, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Error in poc, please refer the result section for details. Version-Release number of selected component (if applicable): gettext-0.19.8.1-18.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1. Clone https://github.com/CCCCCrash/POCs.git. 2. Run valgrind msgfmt poc command. 3. Observe the output. Actual results: [poyadav@localhost doublefree]$ valgrind msgfmt poc ==8072== Memcheck, a memory error detector ==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==8072== Command: msgfmt poc ==8072== ==8072== Conditional jump or move depends on uninitialised value(s) ==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so) ==8072== by 0x487E8EA: po_lex_charset_set (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487E098: po_gram_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487A773: catalog_reader_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt) ==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt) ==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so) ==8072== poc:17: duplicate message definition... poc:16: ...this is the location of the first definition poc:18:3: syntax error poc:18: keyword "n" unknown poc:19: end-of-line within string poc:28: duplicate message definition... poc:24: ...this is the location of the first definition poc:35: keyword "msgud_plural" unknown poc:34: missing 'msgstr' section poc:35:13: syntax error poc:40: end-of-line within string poc:46: end-of-line within string poc: warning: Charset missing in header. Message conversion to user's charset will not work. poc:42: duplicate message definition... poc:6: ...this is the location of the first definition poc:46:2: syntax error poc:46: keyword "Ep" unknown poc:47: keyword "C" unknown poc:48: keyword "s" unknown poc:49: keyword "bo" unknown poc:50: keyword "S" unknown poc:50:236: invalid control sequence poc:50:397: invalid control sequence poc:51: end-of-line within string msgfmt: too many errors, aborting ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 59,783 bytes in 123 blocks ==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 650 bytes in 82 blocks ==8072== indirectly lost: 0 bytes in 0 blocks ==8072== possibly lost: 0 bytes in 0 blocks ==8072== still reachable: 59,133 bytes in 41 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== Use --track-origins=yes to see where uninitialised values come from ==8072== For lists of detected and suppressed errors, rerun with: -s ==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Expected results: No errors. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1954716] New: Fonts not used correctly
by bugzilla＠redhat.com 08 Dec '22

08 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1954716 Bug ID: 1954716 Summary: Fonts not used correctly Product: Fedora Version: rawhide Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: barbarah.duarte(a)fluocomunicacao.com.br QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pnemade(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1776799 --> https://bugzilla.redhat.com/attachment.cgi?id=1776799&action=edit LibreOffice with all three fonts displayed in regular, italic and bold face. I have installed some company-provided fonts for use in presentations etc.: $ ls /usr/share/fonts/neo-sans-intel/ NeoSansIntel-Italic.ttf NeoSansIntel-MediumItalic.ttf NeoSansIntel-LightItalic.ttf NeoSansIntel-Medium.ttf NeoSansIntel-Light.ttf NeoSansIntel.ttf In LibreOffice I have a choice of three separate fonts: Neo Sans Intel, Neo Sans Intel Medium, and Neo Sans Intel Light. For each of those three, the italic version of the font (from the separate TTF file) is used. I can tell by the tail on the 'f' character. For bold text, however, an 'emboldening' algorithm seems to be used instead of using the appropriate separate font file. In GNOME font selection dialogs, I see just one 'Neo Sans Intel' family, with a choice of 8 styles. I'll ignore the italic versions since those do actually seem to work as expected, so there are four weights listed: - Light (== Neo Sans Intel Light) - Regular (== Neo Sans Intel Medium) - Medium (== Neo Sans Intel Medium) - Bold (== Neo Sans Intel Medium + emboldening algorithm?) I *don't* seem to have an option in GNOME which will just use the straight 'Neo Sans Intel' font. So both seem to be getting it wrong, in different ways. Or perhaps there's something wrong with the fonts themselves? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1981500] New: [f34] some snaps are having font display issues
by bugzilla＠redhat.com 07 Dec '22

07 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1981500 Bug ID: 1981500 Summary: [f34] some snaps are having font display issues Product: Fedora Version: 34 OS: Linux Status: NEW Component: fontconfig Severity: medium Assignee: tagoh(a)redhat.com Reporter: dvd(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pnemade(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Installing some snaps like codium are having font issues in dialog windows. This has been widely discussed upstream [1] Tried multiple workarounds and none of them are working: ~~~ sudo rm /var/cache/fontconfig/* rm ~/.cache/fontconfig/* rm -f ~/snap/codium/current/.cache/ fc-cache -r -v snap run --shell codium fc-cache -r -v exit ~~~ I also tried this with VScodium running Arch wiki [a] suspects it's an issue caused by fontconfig>=2.13.91 Version-Release number of selected component (if applicable): fontconfig-2.13.93-6.fc34.x86_64 snapd-selinux-2.51-1.fc34.noarch snap-confine-2.51-1.fc34.x86_64 snapd-2.51-1.fc34.x86_64 How reproducible: All the time Steps to Reproduce: 1. snap install codium 2. Open Folder dialog or any kind of dialog Actual results: All the text is square instead of readable characters Expected results: We should be able to read the text. Additional info: [a] https://wiki.archlinux.org/title/Talk:Snap [1] ~~~ https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora-and-ar… https://forum.inkdrop.app/t/snap-with-no-visible-letters-in-system-dialogs-… https://wiki.archlinux.org/title/Talk:Snap https://githubmemory.com/repo/snapcrafters/codium/issues/6 https://github.com/VSCodium/vscodium/issues/426 ~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1771836] New: ibus not responsive on wayland with sway as windowmanager
by bugzilla＠redhat.com 30 Nov '22

30 Nov '22

https://bugzilla.redhat.com/show_bug.cgi?id=1771836 Bug ID: 1771836 Summary: ibus not responsive on wayland with sway as windowmanager Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: chorn(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1635626 --> https://bugzilla.redhat.com/attachment.cgi?id=1635626&action=edit strace when running ibus-wayland from a terminal in sway Description of problem: ibus not responsive on wayland with sway as windowmanager Version-Release number of selected component (if applicable): ibus-wayland-1.5.21-3.fc31.x86_64 ibus-1.5.21-3.fc31.x86_64 ibus-mozc-2.23.2815.102-8.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora31, select lxde-desktop-environment to get wayland installed 2. dnf -y install sway ibus-wayland ibus-mozc 3. useradd -m chris; passwd chris 4. Use this in the users .bashrc : [[ $(pgrep ibus-daemon) ]] || ibus-daemon --xim --daemonize -r export IMSETTINGS_INTEGRATE_DESKTOP=yes export IMSETTINGS_MODULE=ibus export QT_IM_MODULE=ibus export XMODIFIERS=@im=ibus export GTK_IM_MODULE=ibus 5. Boot system into multi-usermode, for example in setting it as default target and rebooting 6. login as user chris 7. run sway in executing 'sway' 8. get a terminal in pressing $mod + return (by default, $mod is the windows-key) 9. verify ibus-daemon is running: 'ps ax|grep ibus' 10. try to run ibuswayland: '/usr/libexec/ibus-wayland' Actual results: No input_method global Expected results: ibus-wayland should run, and I should be able to switch input method to mozc as configured with 'ibus-setup'. Additional info: - Might very well be an issue on my side.. but after trying this now for a week, taking that to bugzilla. - fcitx4 from Fedora works under sway. - When setting up ibus as above, I was never able to run ibus-wayland, and ibus did never react to attempts to switch the input method with shift+space or ctrl+space, I tried these combinations after setting them up with ibus-setup - Instead of running ibus-daemon from user .bashrc, I did run it from sway directly. Steps: mkdir ~/.config/sway cp /etc/sway/config ~/.config/sway/config echo 'exec /usr/bin/ibus-daemon --xim --daemonize' >>~/.config/sway/config The result is the same though. - When running ibus-daemon non-daemonizing from a terminal, I get this: [chris@космос ~]$ ibus-daemon -r -v (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.303: panel.vala:255: If you launch KDE5 on xterm, export XDG_CURRENT_DESKTOP=KDE before launch KDE5. (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.335: ibus_bus_call_sync: org.freedesktop.DBus.Properties.Get: GDBus.Error:org.freedesktop.DBus.Error.Failed: No global engine. (and ibus-daemon stays running) - I tried various terminals, for example xterm and terminator -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1933539] New: Require mkfontdir/mkfontscale directly, not xorg-x11-xkb-utils
by bugzilla＠redhat.com 30 Nov '22

30 Nov '22

https://bugzilla.redhat.com/show_bug.cgi?id=1933539 Bug ID: 1933539 Summary: Require mkfontdir/mkfontscale directly, not xorg-x11-xkb-utils Product: Fedora Version: rawhide Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: peter.hutterer(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, extras-qa(a)fedoraproject.org, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, mtasaka(a)tbz.t-com.ne.jp, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com Depends On: 1933537 Blocks: 1932731 Target Milestone: --- Classification: Fedora liberation-fonts currently BuildRequires: xorg-x11-font-utils xorg-x11-font-utils is to be split up into multiple packages, see Bug 1932731. This package only requires mkfontscale and mkfontdir, so let's BuildRequires these directly. xorg-x11-font-utils has had Provides for those for ages now anyway, so this is largely a noop from this package's POV. Suggested diff: diff --git a/liberation-fonts.spec b/liberation-fonts.spec index a9cc575..583e224 100644 --- a/liberation-fonts.spec +++ b/liberation-fonts.spec @@ -24,7 +24,8 @@ Source8: %{fontname}-sans.metainfo.xml Source9: %{fontname}-serif.metainfo.xml BuildArch: noarch -BuildRequires: fontpackages-devel >= 1.13, xorg-x11-font-utils +BuildRequires: fontpackages-devel >= 1.13 +BuildRequires: mkfontscale mkfontdir BuildRequires: fontforge BuildRequires: libappstream-glib BuildRequires: python3 Verified successful build in a local F33 container with only the mkfontscale (Bug 1932734) and bdftopcf (Bug 1932736) packages installed, no xorg-x11-font-utils. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1932731 [Bug 1932731] X.org Utility Deaggregation - xorg-x11-font-utils https://bugzilla.redhat.com/show_bug.cgi?id=1933537 [Bug 1933537] Require mkfontdir/mkfontscale directly, not xorg-x11-xkb-utils -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1858617] New: vlgothic-fonts-20200719 is available
by bugzilla＠redhat.com 12 Oct '22

12 Oct '22

https://bugzilla.redhat.com/show_bug.cgi?id=1858617 Bug ID: 1858617 Summary: vlgothic-fonts-20200719 is available Product: Fedora Version: rawhide Status: NEW Component: vlgothic-fonts Keywords: FutureFeature, Triaged Assignee: tagoh(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 20200719 Current version/release in rawhide: 20141206-16.fc32 URL: https://osdn.jp/projects/vlgothic/releases/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/5103/ -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1916743] New: Fedora Scientific Spin does not include ibus-table* packages
by bugzilla＠redhat.com 12 Jul '22

12 Jul '22

https://bugzilla.redhat.com/show_bug.cgi?id=1916743 Bug ID: 1916743 Summary: Fedora Scientific Spin does not include ibus-table* packages Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-table Severity: high Assignee: mfabian(a)redhat.com Reporter: pa_ubach(a)alum.mit.edu QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com, mfabian(a)redhat.com, pwu(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: Clean install of Fedora Scientific (KDE) does not include the ibus-table* packages that are necessary for local distributions of the keyboard. Version-Release number of selected component (if applicable): How reproducible: Haven't tried Steps to Reproduce: 1. Install Fedora Scientific 2. Try to type using dead keys in any KDE program or LibreOffice. 3. Actual results: Vowel letters don't include accents. Expected results: áàäâéèéêíïîóòöôúùüû Additional info: To fix the problem, the user must install ibus-table* packages, which is not described in the documentation, but it should not be necessary to search it in the documentation anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Fedora-i18n-bugs] [Bug 1757760] New: Hiragana to English conversion with F10 key adds unwanted letters
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1757760 Bug ID: 1757760 Summary: Hiragana to English conversion with F10 key adds unwanted letters Product: Fedora Version: rawhide Status: NEW Component: ibus-kkc Assignee: dueno(a)redhat.com Reporter: ykatabam(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: When we enter an English word with consecutive double letters (e.g. assembly) in Hiragana mode and use F10 to convert into English, the double letters becomes the triple letters in some cases (e.g. asssembly). This happens irregularly, but tends to happen more often for longer words. Here are some examples: communication becomes commmunication bugzilla becomes bugzilla Pittsburgh becomes Pitttsburgh FYI, auto-correct is disabled, as auto-correct changes the input when it's not a dictionary word so it doesn't allow us to convert into English properly in hiragana mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1936777] New: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 05 Jun '22

05 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1936777 Bug ID: 1936777 Summary: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV Product: Fedora Version: 34 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e9e25725fbf5b802310f7153823734fd779117b2;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.24-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service cmdline: /usr/libexec/ibus-x11 --kill-daemon crash_function: ibus_bus_connect_async executable: /usr/libexec/ibus-x11 journald_cursor: s=f2062dd079fe488fb71eaaf5c3a6c6de;i=64d9;b=7aa46cfdf18e49c4bdacf0acfee8806c;m=b349fea0;t=5bd0beaaa310b;x=3f2d3a76fa7ae073 kernel: 5.11.3-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 ibus_bus_connect_async at /usr/src/debug/ibus-1.5.24-1.fc34.x86_64/src/ibusbus.c:462 #1 _g_cclosure_marshal_VOID__OBJECT_OBJECT_ENUMv at ../gio/gmarshal-internal.c:1380 #2 _g_closure_invoke_va at ../gobject/gclosure.c:873 #5 g_file_monitor_source_dispatch at ../gio/glocalfilemonitor.c:567 #8 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131 #10 ibus_main at /usr/src/debug/ibus-1.5.24-1.fc34.x86_64/src/ibusshare.c:318 Potential duplicate: bug 1926996 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1787124] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by bugzilla＠redhat.com 16 May '22

16 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=1787124 Bug ID: 1787124 Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR IANT_ID=matecompiz; Component: mozc Assignee: tagoh(a)redhat.com Reporter: ryutaroh2006(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I don't know how or why ibuz-engine-mozc was killed by SIGABRT... Version-Release number of selected component: ibus-mozc-2.23.2815.102-8.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service cmdline: /usr/libexec/ibus-engine-mozc --ibus crash_function: __fdelt_chk executable: /usr/libexec/ibus-engine-mozc journald_cursor: s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9 kernel: 5.3.16-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #6 __fdelt_chk at fdelt_chk.c:25 #7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108 #8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157 #9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs July 2021