Fedora 19 i18n and Translation Test day

Fedora 19 Alpha released and it is best time to test translation and i18n feature, so that bugs can be timely fixed before release.

FLTG  team providing support for Translation Test Day and I18N Test Day by add, review test cases, search features and communicate between various groups.

for Translation Test Day, we add few more gnome applications (like gnome-initial setup) and remove features those are no more available or default in Fedora 19 (like ibus, which is not part of gnome desktop). Translation Test Matrix is improved, while Report Page and Feedback page is created. Anaconda, have major in-complete translation for almost in all language, while gnome-initial-setup, gnome-clock etc application those are new in gnome-3.8 are also have English interface.

Fedora i18n Test Day (May 02, 2013) is upcoming, where tester can get time to review feature for gnome-ibus integration, new shortcuts to Enable/Disable input (check i18n Meeting log for detail).

Major Rendering issue for Indic locales detected (Hindi, Punjabi confirmed and bug already filed) during pre-test activity. Actually this issue already reported for Anaconda (lorax) here, but but with gnu-free-fonts have bugs for Indic locales and set default for Monospace instead of Lohit fonts (as lohit is no monospace), now gnome desktop effecting by this. During i18n Meeting it was found that Either disable gnu-free-fonts for Indic language (those are effected), which is easy way or disable monospace for Indic

Advertisements

lokalize Junk data with qt 4.7.1 – workaround 2 (fedora)

when lokalize crash problem was fixed, then New problem arrived – Junk data in translated field

(check video here)

Steps to Reproduce:
1. run lokalize with translation file (PO file)
2. input something in local language (other than English)
3. Use BackSpace to delete some (not all)
5. Page Down (Move to next string)
6. Page Up (Move back to original String


Actual results:
Junk data inserted in text field automatically, which is not typed

Expected results:
Only Text should be there, which is typed, works fine with BackSpace

KDE bug 249373, kde-i18n mailing list discussion

OpenSUSE, kbuntu and Arch Linux user confirmed that problem.

Fedora workaround for this is below (on Fedora 14):
1) yum remove qt (it will remove whole kde, will not effect much if you are using other than KDE desktop)
2) yum remove kdelibs-common
3) Disable fedora-updates.repo (/etc/yum.repos.d/fedora-updates.repo)  (enabled=0)
4) yum install kdesdk (or other package which you want to install for kde)

Now your lokalize should work normal (qt-4.7.0-3.fc14.x86_64 from fedora 14 Released repo), but note 
that you are not going to get any update for your system (which includes security fixes also)

Nokia provide fix (Crash issue) for qt-4.7.2, but that patch was backport to 4.7.1 for many
distribution. Nobody respond to bug yet (from Nokia).

lokalize crash with qt 4.7.1 – workaround

lokalize is crashing from last few weeks in latest qt-4.7.1

Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?id=660028

Upstream KDE Bug: https://bugs.kde.org/show_bug.cgi?id=249373

Nokia qt bug: http://bugreports.qt.nokia.com/browse/QTBUG-15659

for Fedora, you need to downgrade your ‘qt’ packages for ‘qt-4.7.0-8′ or eariler,

which you can download from Koji or Simple way is:

$yum downgrade qt*

meanwhile

lokalize is crashing from last few weeks in latest qt-4.7.1.

Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?id=660028

Upstream KDE Bug: https://bugs.kde.org/show_bug.cgi?id=249373

Nokia qt bug: http://bugreports.qt.nokia.com/browse/QTBUG-15659

for Fedora, you need to downgrade your ‘qt’ packages for ‘qt-4.7.0-8’ or eariler,

which you can download from Koji or Simple way is:

$yum downgrade qt*

meanwhile Kevin Kofler confirm that qt is fixed by upstream (commit). So fix should be available in

fedora soon.

Windows 7 Language Pack for Indic Languages…

Windows 7 Language Packs made available for Indic locales Here and instruction to install is Given Here.

I have only Windows Home premium, so at a time only one Language can work and not able to switch between different languages without change settings (Professional and Ultimate has feature for Multiple Language).

I am using Punjabi Language for Windows Desktop. Translation is better than Windows XP, but still it needs some improvement (which I would like to say not enhancement, but problematic). Dialog Box size different from en_US Windows and Few dialog box/window are not appear proper. Translation sometime seems like too low-level (pure Punjabi) to use actually. More over Most translation is just copy of Hindi, which sometime don’t make any sense in Punjabi.

Few Screenshots are below.

 

 

 

ਯਾਚਨਾ (what is this?)

Just providing Translation without any Review from actual computer users, it is bad (only good to complete formality for business deals)

KDE 4.3 – lokalize fixed

after kde 4.2 release, lokalize has problem
to Find or Replace Text. It was big problem
to Edit Translation files (po) with Lokalize,
if you want to find or replace some text in
lokalize.
But KDE 4.3 release, it is fixed and now
you can find/replace text. Catalogmanager
it is now automatic show status of all
files. Both the fix are quit helpful for
translator.
Fedora 11 and Fedora 10 Users can get
those package (kdebase-4.3* etc) by
enable test repo with following command
$yum update –enablerepo=updates-testing

but if you can wait for days, then you can get
package with yum update only.

period for which lokalize has problem, I
tried alternative PO Editor, which as
few different, but impressive features.
(Update later)

virtaal
linguist-qt4 (qt-devel package)

GCompris Translation – Bad foot-prints

I got mail from gnome mailing list regarding
“[Announce Release 8.4.9]”. It included Punjabi
Translation, just would like to search what it is
actually. As it is part of gnome, so expecting
translation to check. It was transliteration only,
second file failed to pass ‘msgfmt’ check. Translation
was really bad and I hope to work with developer
to use proper svn translation from gnome.
But Again CDAC is moving its hard-core
‘Govt’ way. It is not just bad, but worse foot-print,
which their followers are following again and again…

First Gnome GIT Commit IN…

gnome moved to GIT ahead of KDE:-)
it was confusion how to commit as a Translator as Damned lies are changed and
everybody can make account on it and submit translation there. But how
to commit.
I have did small search and send first updated file via GIT-svn.
———
alam@linux-1f05:~/ git clone git://git-mirror.gnome.org/git/gnome-desktop
alam@linux-1f05:~/ git svn init -s svn+ssh://@svn.gnome.org/svn/gnome-desktop –prefix=origin/svn/
alam@linux-1f05:~/git svn rebase
alam@linux-1f05:~/l10n/gnome/GIT/gnome-desktop/po> git commit -a -m “2nd attempt to commit translation for pa.po”
Created commit 8ba8cb7: 2nd attempt to commit translation for pa.po
1 files changed, 189 insertions(+), 153 deletions(-)
alam@linux-1f05:~/l10n/gnome/GIT/gnome-desktop> git svn dcommit
Committing to svn+ssh://@svn.gnome.org/svn/gnome-desktop/trunk …
M po/pa.po
Committed r5344
M po/pa.po
r5344 = 99872f975ea4227625f8ba2d1df58e5e78e8534f (origin/svn/trunk)
No changes between current HEAD and refs/remotes/origin/svn/trunk
Resetting to the latest refs/remotes/origin/svn/trunk
——
it is reflected and Damned lies. It was 2nd try and commit…

few things:
1) Download size is quite big (gnome-panel-~40MB) (-)
2) number of commands increase (5 instead of 2) (-)

Link used as Reference to make this happen.