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)
Showing posts with label Translation. Show all posts
Showing posts with label Translation. Show all posts
09 August, 2009
09 March, 2009
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...
"[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...
Labels:
community,
l10n,
Translation
12 January, 2009
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.
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://
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://
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.
Labels:
Gnome,
Technical,
Translation,
Troubleshooting
16 December, 2008
Mozilla l10n status update - quick
after many days I committed to l10n changes to
hg repo at Mozilla Firefox/thunderbird. After
commit, changes are reflected to server quite
fast like Gnome
http://l10n.mozilla.org/dashboard/
you can customize this for single language as
I have only Punjabi Language:
http://l10n.mozilla.org/dashboard/?locale=pa-IN
(at slow home connection, it is quite big help)
hg repo at Mozilla Firefox/thunderbird. After
commit, changes are reflected to server quite
fast like Gnome
http://l10n.mozilla.org/dashboard/
you can customize this for single language as
I have only Punjabi Language:
http://l10n.mozilla.org/dashboard/?locale=pa-IN
(at slow home connection, it is quite big help)
Labels:
community,
l10n,
software,
Translation
17 October, 2008
a Project Change from pa-IN to pa - Mission, not only word
Unicode make it clear that 'pa-gur-IN' is basic part of 'pa' locale
where pa-gur-IN Represent as < LANG >-< SCRIPT >-< REGION >
so Punjabi-Gurmukhi-India Script is actually making 'pa' locale.
So Most Project already using 'pa' is for Punjabi, quite few project
like mozilla is using pa-IN, which need to update.
A bug 380287 filed for Firefox/Thunderbird
updates.
I tried to file before Firefox 3 Release and asked to fix it, but
Mozilla Team was busy with other important task, so it was skipped.
Finally Team have a time and get back to it.
Unicode: http://www.unicode.org/cldr/bugs/locale-bugs?findid=1300
---------------------------------------------------------------------
pa (Stage 1) //Punjabi =
pa-IN (default)(unicode bug _above)
/ \
/ \
pa-arb pa-gur (Stage 2) //2 different Script
(Shahmukhi / Gurmukhi)
| |
pa-PK pa-IN (Stage 3)//Region based,
Pakistan India
---------------------------------------------------------------------
So, Now First we need to skip region based choice and to
original locale choice (that is 'pa'), which is important
as if you run a application, by giving pa-IN or pa-PK, and
no translation available for that, then application will check
for 'pa' translation. As 'pa' is default, so we need to use it
(as Unicode confirmed this).
What happened if Shahmukhi Script people want to start project
for Punjabi?
Surely they have to use script encoding with language like pa-arb
or pa@arb as there is script difference and only solution is to use
arb with pa and it is true for all projects. After all script is basic
difference, not region as any Shahmukhi Punjabi User can be
anywhere is world as Gurmukh Punjabi Script User are.
I got most response from NRI Punjabi people instead of India based.
so it is not good to attach a specific region with locale due to
population (census). I was never happy to divide a language
on basis of region, as Language has no boundary itself, but it
flow of ideas, freedom to express those, So we should make it
open and out of boundary. If I have operating system, then sometimes
it can be used to select timezone for locale automatic, but should
not be forced to use only that timezone. My Mac is showing
same issue as I selected Punjabi, then only Showing region as
India. Surely more Punjabi Mac users are outside India and
Apple is still confuse with "non-census" data. So
making my (our) locale region-free is important mission for me.
During working on bug, something interesting is pointed out that
mozilla got around 100 hits daily for Punjabi locale. It was
quite good figure, if I cared to my guess.
Hope to fix this issue soon as 'Seth' is working quite hard, but
I was worrying about his late comment in bug "will ask our Indic localizers
who write blogs to make the announcement."
let us see what is output of that...
where pa-gur-IN Represent as < LANG >-< SCRIPT >-< REGION >
so Punjabi-Gurmukhi-India Script is actually making 'pa' locale.
So Most Project already using 'pa' is for Punjabi, quite few project
like mozilla is using pa-IN, which need to update.
A bug 380287 filed for Firefox/Thunderbird
updates.
I tried to file before Firefox 3 Release and asked to fix it, but
Mozilla Team was busy with other important task, so it was skipped.
Finally Team have a time and get back to it.
Unicode: http://www.unicode.org/cldr/bugs/locale-bugs?findid=1300
---------------------------------------------------------------------
pa (Stage 1) //Punjabi =
pa-IN (default)(unicode bug _above)
/ \
/ \
pa-arb pa-gur (Stage 2) //2 different Script
(Shahmukhi / Gurmukhi)
| |
pa-PK pa-IN (Stage 3)//Region based,
Pakistan India
---------------------------------------------------------------------
So, Now First we need to skip region based choice and to
original locale choice (that is 'pa'), which is important
as if you run a application, by giving pa-IN or pa-PK, and
no translation available for that, then application will check
for 'pa' translation. As 'pa' is default, so we need to use it
(as Unicode confirmed this).
What happened if Shahmukhi Script people want to start project
for Punjabi?
Surely they have to use script encoding with language like pa-arb
or pa@arb as there is script difference and only solution is to use
arb with pa and it is true for all projects. After all script is basic
difference, not region as any Shahmukhi Punjabi User can be
anywhere is world as Gurmukh Punjabi Script User are.
I got most response from NRI Punjabi people instead of India based.
so it is not good to attach a specific region with locale due to
population (census). I was never happy to divide a language
on basis of region, as Language has no boundary itself, but it
flow of ideas, freedom to express those, So we should make it
open and out of boundary. If I have operating system, then sometimes
it can be used to select timezone for locale automatic, but should
not be forced to use only that timezone. My Mac is showing
same issue as I selected Punjabi, then only Showing region as
India. Surely more Punjabi Mac users are outside India and
Apple is still confuse with "non-census" data. So
making my (our) locale region-free is important mission for me.
During working on bug, something interesting is pointed out that
mozilla got around 100 hits daily for Punjabi locale. It was
quite good figure, if I cared to my guess.
Hope to fix this issue soon as 'Seth' is working quite hard, but
I was worrying about his late comment in bug "will ask our Indic localizers
who write blogs to make the announcement."
let us see what is output of that...
Labels:
community,
FIrefox,
non-Technical,
Opensource,
Punjabi,
software,
Team,
Translation
Firefox 3.1 Beta 1 - for Punjabi
Again Firefox available for Testing beta version. It is available
for Punjabi Version 3.1Beta1
Windows Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=win&lang=pa-IN
Mac Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=osx&lang=pa-IN
Linux Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=linux&lang=pa-IN
If you have resource please download and Test once (for Punjabi), so
that we can make impact for locale [1]
More This Beta release Information:
http://www.mozilla.com/en-US/firefox/all-beta.html
After Test, please send us your review, comment about
Translation to our mailing list Punjab-users so that
we can work to update as we have two week to finish before
Beta 2 release. I have one issue with me (which is sent by
Mr. A S Kang for copy/link issue)
[1] Mozilla Bug
ਬੱਗ ਮੁਤਾਬਕ ਔਸਤ ਪੰਜਾਬੀ ਲਈ ਹਿੱਟ 100 ਰੋਜ਼ਾਨਾ ਹੈ, ਮੈਨੂੰ ਥੋੜ੍ਹੀ ਹੈਰਾਨੀ ਹੋਈ ਕਿ 100 ਕਿੱਥੋ ਹੋ ਗਏ, ਸੱਚੀ
ਐਨੀ ਉਮੀਦ ਨਹੀਂ ਸੀ। ਬਾਕੀ ਮੋਜ਼ੀਲਾ ਸਿਸਟਮ ਐਡਮਿਨ ਦੇ ਸ਼ਬਦ ਖੁਦ ਪੜ੍ਹ ਲਵੋ ਜੀ! Check
Admin comment below about Punjabi
"For the most part it looks like we have about 100 Active Daily users for pa-IN.
There is a strange couple of days just recently where we had a huge spike.
aug 21,22... Can anyone think of what might have caused this? Holiday or any
other event? I could have just been an error in our reporting system...
Here is the data for those two days and the last 15.
2008-08-21 7,004
2008-08-22 533
...
2008-10-01 110
2008-10-02 94
2008-10-03 115
2008-10-04 99
2008-10-05 93
2008-10-06 107
2008-10-07 106
2008-10-08 114
2008-10-09 96
2008-10-10 119
2008-10-11 99
2008-10-12 102
2008-10-13 117
2008-10-14 113
2008-10-15 119"
for Punjabi Version 3.1Beta1
Windows Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=win&lang=pa-IN
Mac Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=osx&lang=pa-IN
Linux Download:
http://download.mozilla.org/?product=firefox-3.1b1&os=linux&lang=pa-IN
If you have resource please download and Test once (for Punjabi), so
that we can make impact for locale [1]
More This Beta release Information:
http://www.mozilla.com/en-US/firefox/all-beta.html
After Test, please send us your review, comment about
Translation to our mailing list Punjab-users so that
we can work to update as we have two week to finish before
Beta 2 release. I have one issue with me (which is sent by
Mr. A S Kang for copy/link issue)
[1] Mozilla Bug
ਬੱਗ ਮੁਤਾਬਕ ਔਸਤ ਪੰਜਾਬੀ ਲਈ ਹਿੱਟ 100 ਰੋਜ਼ਾਨਾ ਹੈ, ਮੈਨੂੰ ਥੋੜ੍ਹੀ ਹੈਰਾਨੀ ਹੋਈ ਕਿ 100 ਕਿੱਥੋ ਹੋ ਗਏ, ਸੱਚੀ
ਐਨੀ ਉਮੀਦ ਨਹੀਂ ਸੀ। ਬਾਕੀ ਮੋਜ਼ੀਲਾ ਸਿਸਟਮ ਐਡਮਿਨ ਦੇ ਸ਼ਬਦ ਖੁਦ ਪੜ੍ਹ ਲਵੋ ਜੀ! Check
Admin comment below about Punjabi
"For the most part it looks like we have about 100 Active Daily users for pa-IN.
There is a strange couple of days just recently where we had a huge spike.
aug 21,22... Can anyone think of what might have caused this? Holiday or any
other event? I could have just been an error in our reporting system...
Here is the data for those two days and the last 15.
2008-08-21 7,004
2008-08-22 533
...
2008-10-01 110
2008-10-02 94
2008-10-03 115
2008-10-04 99
2008-10-05 93
2008-10-06 107
2008-10-07 106
2008-10-08 114
2008-10-09 96
2008-10-10 119
2008-10-11 99
2008-10-12 102
2008-10-13 117
2008-10-14 113
2008-10-15 119"
Labels:
community,
FIrefox,
l10n,
linux,
Mac,
Mozila,
non-Technical,
Opensource,
Project,
Punjabi,
software,
Team,
Translation,
Windows
27 August, 2008
evening to make error free translation...
waiting from last few weeks to update few translated files, those have errors and I know that:-)
gnome-power-manager - > last time I did a lot of translation for this and 2 translation Errors were there, I got those, but was in hurry so committed as it is. Finally It is over, but need to find fine editor on Mac. Poedit, LocFactory Editor not work as I was not expert with those, finally KDE4 installatin helped me and lokalize Make it possible.
kde4 - plasma's translation was really un-understandable, and just today I got on my newly laptop, that line is first to see:-(
that line hit me and I started work to remove Error.
so, finally committed changes and gnome/kde desktop for Punjabi is more good than before.
gnome-power-manager - > last time I did a lot of translation for this and 2 translation Errors were there, I got those, but was in hurry so committed as it is. Finally It is over, but need to find fine editor on Mac. Poedit, LocFactory Editor not work as I was not expert with those, finally KDE4 installatin helped me and lokalize Make it possible.
kde4 - plasma's translation was really un-understandable, and just today I got on my newly laptop, that line is first to see:-(
that line hit me and I started work to remove Error.
so, finally committed changes and gnome/kde desktop for Punjabi is more good than before.
Labels:
Gnome,
KDE,
KDE4,
l10n,
non-Technical,
Punjabi,
Team,
Translation
12 August, 2008
my first 'hg' commit to mozilla
I was trying mozilla l10n commit with new version control system, Mercurial.
Finally today I cheched out en-US and pa-IN (for checkout, please check Docs),
started with few translation for one file and used step as mention in Mozilla Docs
following is output of my terminal
------
amanpreet:pa-IN Preet$ hg commit -m "updating translation first time with hg for Punjabi (pa) by Amanpreet Singh Alam"
amanpreet:pa-IN Preet$ hg outgoing
comparing with ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
changeset: 2:0c8a3c71fe9d
tag: tip
user: A S Alam
date: Tue Aug 12 11:47:59 2008 +0530
summary: updating translation first time with hg for Punjabi (pa) by Amanpreet Singh Alam
amanpreet:pa-IN Preet$ hg push
pushing to ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
amanpreet:pa-IN Preet$ hg push
pushing to ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
no changes found
---------
first 'hg push' is so slient that I can't understand that anything commited or not, so I run once again
and tried to fresh checkout and Yes, changes are there. So Please don't except any version for new files
as in CVS.
So, finally log can be check Mozilla-l10n-central
First Punjabi hg commit "Push" can be found at
First Punjabi Commit Log.
Finally today I cheched out en-US and pa-IN (for checkout, please check Docs),
started with few translation for one file and used step as mention in Mozilla Docs
following is output of my terminal
------
amanpreet:pa-IN Preet$ hg commit -m "updating translation first time with hg for Punjabi (pa) by Amanpreet Singh Alam"
amanpreet:pa-IN Preet$ hg outgoing
comparing with ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
changeset: 2:0c8a3c71fe9d
tag: tip
user: A S Alam
date: Tue Aug 12 11:47:59 2008 +0530
summary: updating translation first time with hg for Punjabi (pa) by Amanpreet Singh Alam
amanpreet:pa-IN Preet$ hg push
pushing to ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
amanpreet:pa-IN Preet$ hg push
pushing to ssh://hg.mozilla.org/l10n-central/pa-IN/
searching for changes
no changes found
---------
first 'hg push' is so slient that I can't understand that anything commited or not, so I run once again
and tried to fresh checkout and Yes, changes are there. So Please don't except any version for new files
as in CVS.
So, finally log can be check Mozilla-l10n-central
First Punjabi hg commit "Push" can be found at
First Punjabi Commit Log.
Labels:
l10n,
Mozila,
Technical,
Translation
23 June, 2008
Punjabi Firefox: Newspaper Caption and Indic communities
Punjabi Firefox Release news is
available in newspaper DNA
it couldn't be great thing if happened in
Punjab (or Punjabi) newspaper, but it
was newspaper in Maharashtra (PUNE)
Color page news and with Great Heading.
People had question about Hindi (surely it is
should be). Reply was simple "it is community
driven translation, not by Mozilla."
Real means is it. I never saw Mozilla to
push any community to do translation,
it is ok with various communities, where
languages are with good priority like
European countries, but when talk about Indian
Languages, where English has 'Great'
priority over local language for 'high
class'/'first class' society, someone
don't forgot that more than those 'First
class' people, native speakers for their
respective languages. If those people are
not active in communities or open source,
it should not understand that those
languages are not required or can
skip those.
This time happen with Hindi, which
is not released with Firefox 3. Rajesh
did very hard work to finish it, actually
he completed, but Release process for
Firefox is tough and it is not 'simple'
to follow. You should follow 'daily' routine
to ask question from responsible persons
(in Mozilla l10n, I found Axel (Pike) only
guy for this).
Process need to make simple, (
people are working on it), but it is not
too complex in either sense (to understand
or follow). You can keep track if keep yourself
regular.
I found thread on mailing list as following
Hindi why not?.
While agree with Sangeeta about comment,
Axel point is valid too, actually Axel is most
busy person during l10n release. Process as
I told earlier is not bad, but it can be improved
as it is unique process I found during my 6 year
L10N/i18n experience. It is best for get 'build
for your language' in every 15 mintnes. it is
fast to test, and very dedicated Test Case and
Test Process. although Translation is not simple
as it is not 'po' files for most translators, but
I thought it is 'USE TO' factor than 'Easiness'.
Mozilla explain that " reaching out to recruit people to work on
localisations for Indian users", hope to improve situation soon.
available in newspaper DNA
it couldn't be great thing if happened in
Punjab (or Punjabi) newspaper, but it
was newspaper in Maharashtra (PUNE)
Color page news and with Great Heading.
People had question about Hindi (surely it is
should be). Reply was simple "it is community
driven translation, not by Mozilla."
Real means is it. I never saw Mozilla to
push any community to do translation,
it is ok with various communities, where
languages are with good priority like
European countries, but when talk about Indian
Languages, where English has 'Great'
priority over local language for 'high
class'/'first class' society, someone
don't forgot that more than those 'First
class' people, native speakers for their
respective languages. If those people are
not active in communities or open source,
it should not understand that those
languages are not required or can
skip those.
This time happen with Hindi, which
is not released with Firefox 3. Rajesh
did very hard work to finish it, actually
he completed, but Release process for
Firefox is tough and it is not 'simple'
to follow. You should follow 'daily' routine
to ask question from responsible persons
(in Mozilla l10n, I found Axel (Pike) only
guy for this).
Process need to make simple, (
people are working on it), but it is not
too complex in either sense (to understand
or follow). You can keep track if keep yourself
regular.
I found thread on mailing list as following
Hindi why not?.
While agree with Sangeeta about comment,
Axel point is valid too, actually Axel is most
busy person during l10n release. Process as
I told earlier is not bad, but it can be improved
as it is unique process I found during my 6 year
L10N/i18n experience. It is best for get 'build
for your language' in every 15 mintnes. it is
fast to test, and very dedicated Test Case and
Test Process. although Translation is not simple
as it is not 'po' files for most translators, but
I thought it is 'USE TO' factor than 'Easiness'.
Mozilla explain that " reaching out to recruit people to work on
localisations for Indian users", hope to improve situation soon.
Labels:
community,
corporate,
Mozila,
Translation
Subscribe to:
Posts (Atom)