. There
are things that each individual component owner should do for
him/herself, like including the right formatting codes in the logical
ids (if we stick with them), and reducing excessive context if that
would improve things.
But we are talking here about maemo localization to officially
non
* Mohammed Hassan
(Please follow mail-followup-to, I read the list)
| If the main problem is identifying untranslated strings in the UI, you
| could have a bogus locale where you translate all the translatable
| strings into their logical IDs. (Which could be added as comments in
| the .c
On Fri, 2007-10-26 at 09:45 +0200, ext Tollef Fog Heen wrote:
* Mohammed Hassan
(Please follow mail-followup-to, I read the list)
| If the main problem is identifying untranslated strings in the UI, you
| could have a bogus locale where you translate all the translatable
| strings
On Fri, 2007-10-26 at 16:06 +0300, Marius Vollmer wrote:
Mohammed Hassan [EMAIL PROTECTED] writes:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to maintain the smooth
process. It's not easy to simply drop them. I did not say it's
Hi,
ext Mohammed Hassan wrote:
Which still doesn't help.
Currently if the string is not translated then we mark it in the PO
files so we and the developers can tell that it's not yet translated
In case a developer is using an incorrect logical ID or a logical it not
in the specs, we can
Hi,
Mohammed Hassan wrote:
On Fri, 2007-10-26 at 17:11 +0300, Eero Tamminen wrote:
ext Mohammed Hassan wrote:
Which still doesn't help.
Currently if the string is not translated then we mark it in the PO
files so we and the developers can tell that it's not yet translated
In case a
On Fri, 2007-10-26 at 17:11 +0300, Eero Tamminen wrote:
Hi,
ext Mohammed Hassan wrote:
Which still doesn't help.
Currently if the string is not translated then we mark it in the PO
files so we and the developers can tell that it's not yet translated
In case a developer is using an
On Wed, 2007-10-24 at 16:46 +0200, ext Tollef Fog Heen wrote:
* Mohammed Hassan
| msgfmt will happily provide you with statistics about untranslated
| strings and fuzzy translations, with the added bonus that it can be
| automated.
|
| Yes but it will not help differentiation
On Thu, 2007-10-25 at 08:56 +0300, ext Quim Gil wrote:
- Logical IDs vs internal processes. I'm still digesting the thread but
it looks that it could be done. Won't be easy but it doesn't need to be
done all in once (am I right?). Cases like browser or email client could
be isolated. Hildon
Hi,
ext Riku Voipio wrote:
Mohammed Hassan wrote:
It would be interesting to take our current translations and mine them
for the logical ids that map to the same Engineering English, but at
the same time have different translations in some language. These are
the cases where we would need
Mohammed Hassan [EMAIL PROTECTED] writes:
On Tue, 2007-10-23 at 14:01 +0300, Marius Vollmer wrote:
ext Mohammed Hassan [EMAIL PROTECTED] writes:
What I'd propose is we/I replace the logical IDs with Engineering
English in the POT files you use to translate and convert them back
upon
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to maintain the smooth
process. It's not easy to simply drop them. I did not say it's
impossible. I didn't say it'll be done or it'll not. I'm just saying
that they are needed ;-)
This
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan wrote:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to maintain the smooth
process. It's not easy to simply drop them. I did not say it's
impossible. I didn't say it'll be done
On Wed, 2007-10-24 at 13:54 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan wrote:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to maintain the smooth
process. It's not easy to simply drop them.
On ons, 2007-10-24 at 14:14 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 13:54 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan wrote:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to
Hi,
ext David Weinehall wrote:
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan wrote:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer wrote:
The problem is the logical IDs are needed to maintain the smooth
process. It's not easy to simply drop them. I did not say it's
impossible. I
David Weinehall [EMAIL PROTECTED] writes:
[...] but as a programmer I cannot be happy until we get proper
strings that have the same parameter format as the real strings, to
allow for proper argument checking by the compiler.
Yes, but this is independent from whether we use logical ids or
On Wed, 2007-10-24 at 14:15 +0300, Eero Tamminen wrote:
Hi,
And if you want to check the translation for common errors,
something like this can be used:
https://gramps.svn.sourceforge.net/svnroot/gramps/branches/gramps22/po/check_po
(which of course doesn't work with our unique ID because
On Wed, 2007-10-24 at 14:19 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 14:14 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 13:54 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan wrote:
On Wed, 2007-10-24 at 12:12 +0300, Marius Vollmer
On Wed, 2007-10-24 at 12:12 +0300, ext Marius Vollmer wrote:
...
For example, I have 9 logical ids that map to OK, and 9 that map to
Cancel in the hildon-application-manager .po file:
$ msgunfmt
/usr/share/locale/en_GB/LC_MESSAGES/hildon-application-manager.mo | grep -B 1
'OK'
Kimmo Hämäläinen [EMAIL PROTECTED] writes:
Wrong. It would depend on the context and language.
Yes, it COULD, fer-crying-out-loudly. :) We have the data now to
figure out whether it actually DOES for the set of our supported
languages.
And what happens when you add a new, more
On Wed, 2007-10-24 at 14:56 +0300, Marius Vollmer wrote:
Also, how do you know whether I use the correct context in my code?
Maybe I am using ai_bd_ok for all my OK buttons?
Testing will reveal it.
In general, we should try to reduce the need for context and
complicated translations. The
Marius Vollmer [EMAIL PROTECTED] writes:
For example, I have 9 logical ids that map to OK, and 9 that map to
Cancel in the hildon-application-manager .po file:
$ msgunfmt
/usr/share/locale/en_GB/LC_MESSAGES/hildon-application-manager.mo | grep -B 1
'OK'
msgid
ext Marius Vollmer [EMAIL PROTECTED] writes:
We change the code. Simple. Providing unneeded context is bad in my
opinion, and the way we do it with the logical ids is excessivly ugly.
Also, we provide excessive context, but not very relevant context.
Take ai_bd_new_repository_ok as an
On Wed, 2007-10-24 at 14:56 +0300, Marius Vollmer wrote:
Kimmo Hämäläinen [EMAIL PROTECTED] writes:
Wrong. It would depend on the context and language.
Yes, it COULD, fer-crying-out-loudly. :) We have the data now to
figure out whether it actually DOES for the set of our supported
On Wed, 2007-10-24 at 15:14 +0300, Marius Vollmer wrote:
ext Marius Vollmer [EMAIL PROTECTED] writes:
We change the code. Simple. Providing unneeded context is bad in my
opinion, and the way we do it with the logical ids is excessivly ugly.
Also, we provide excessive context, but not
On Wed, 2007-10-24 at 14:56:46 +0300, ext Marius Vollmer wrote:
In general, we should try to reduce the need for context and
complicated translations. The classical example might:
Searched in %d files and %d directories.
You will never be able to translate this nicely for all languages
On ons, 2007-10-24 at 14:41 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 14:19 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 14:14 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 13:54 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 12:47 +0300, ext Mohammed Hassan
Hi,
On Wed, 2007-10-24 at 15:14 +0300, ext Kimmo Hämäläinen wrote:
On Wed, 2007-10-24 at 14:56 +0300, Marius Vollmer wrote:
Kimmo Hämäläinen [EMAIL PROTECTED] writes:
Wrong. It would depend on the context and language.
Yes, it COULD, fer-crying-out-loudly. :) We have the data now to
On Wed, 2007-10-24 at 15:26 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 14:41 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 14:19 +0300, David Weinehall wrote:
On ons, 2007-10-24 at 14:14 +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 13:54 +0300, David Weinehall
Hi,
Mohammed Hassan wrote:
On Wed, 2007-10-24 at 14:15 +0300, Eero Tamminen wrote:
And if you want to check the translation for common errors,
something like this can be used:
https://gramps.svn.sourceforge.net/svnroot/gramps/branches/gramps22/po/check_po
(which of course doesn't work with
On Wed, 2007-10-24 at 16:03 +0300, Eero Tamminen wrote:
Hi,
Mohammed Hassan wrote:
On Wed, 2007-10-24 at 14:15 +0300, Eero Tamminen wrote:
And if you want to check the translation for common errors,
something like this can be used:
On Wed, 2007-10-24 at 15:33 +0300, ext Igor Stoppa wrote:
Hi,
On Wed, 2007-10-24 at 15:14 +0300, ext Kimmo Hämäläinen wrote:
On Wed, 2007-10-24 at 14:56 +0300, Marius Vollmer wrote:
Kimmo Hämäläinen [EMAIL PROTECTED] writes:
Wrong. It would depend on the context and language.
On Wed, Oct 24, 2007 at 03:08:13PM +0300, Mohammed Hassan wrote:
On Wed, 2007-10-24 at 14:56 +0300, Marius Vollmer wrote:
In general, we should try to reduce the need for context and
complicated translations. The classical example might:
Searched in %d files and %d directories.
Eero Tamminen [EMAIL PROTECTED] writes:
In general, we should try to reduce the need for context and
complicated translations. The classical example might:
Searched in %d files and %d directories.
You will never be able to translate this nicely for all languages
because of the wierd
On ons, 2007-10-24 at 17:53 +0300, ext Marius Vollmer wrote:
Eero Tamminen [EMAIL PROTECTED] writes:
In general, we should try to reduce the need for context and
complicated translations. The classical example might:
Searched in %d files and %d directories.
You will never be
Hi,
Marius Vollmer wrote:
Eero Tamminen [EMAIL PROTECTED] writes:
In general, we should try to reduce the need for context and
complicated translations. The classical example might:
Searched in %d files and %d directories.
You will never be able to translate this nicely for all
On Wed, 2007-10-24 at 18:22 +0300, ext Eero Tamminen wrote:
[1] A former collegue of mine had implemented the Finnish language
morphological model in Z-code, but it needed over 64Kb i.e. more
than the old adventure games written in Z-code... :-)
Which is a mathematical proof that learning
Hi Jordi,
On Mon, 2007-10-22 at 22:43 +0200, ext Jordi Mas wrote:
Hello Quim,
The current system based on logical strings and not on standard open
source practices is open for change though, or at least not-closed to
changes. In fact I’m willing to push this feature to the maemo roadmap.
ext Mohammed Hassan [EMAIL PROTECTED] writes:
What I'd propose is we/I replace the logical IDs with Engineering
English in the POT files you use to translate and convert them back
upon packaging and building.
One immediate problem I see with this is that multiple logical ids can
map to the
On Tue, 2007-10-23 at 14:01 +0300, Marius Vollmer wrote:
ext Mohammed Hassan [EMAIL PROTECTED] writes:
What I'd propose is we/I replace the logical IDs with Engineering
English in the POT files you use to translate and convert them back
upon packaging and building.
One immediate
Mohammed Hassan wrote:
It would be interesting to take our current translations and mine them
for the logical ids that map to the same Engineering English, but at
the same time have different translations in some language. These are
the cases where we would need to use the menu|Open construct
Pada hari Senin, tanggal 22/10/2007 pukul 22:43 +0200, ext Jordi Mas
menulis:
- The possibility to register a new language in the system (the user can
switch to it).
Let's start with this:
https://maemo.org/community/wiki/i18n/
___
maemo-developers
Pada hari Senin, tanggal 22/10/2007 pukul 22:43 +0200, ext Jordi Mas
menulis:
- The possibility to register a new language in the system (the user can
switch to it).
Let's start with this:
https://maemo.org/community/wiki/i18n/
What's the idea of this page? Ask for a better way to do
On Tue, 2007-10-23 at 16:34 +0200, ext API wrote:
Pada hari Senin, tanggal 22/10/2007 pukul 22:43 +0200, ext Jordi Mas
menulis:
- The possibility to register a new language in the system (the user can
switch to it).
Let's start with this:
https://maemo.org/community/wiki/i18n/
Hi Jordi,
On Thu, 2007-10-18 at 21:20 +0200, ext Jordi Mas wrote:
Is there any way to translate the UI into a language not supported
directly by Nokia?
If not, I would be possible from the community to localize the different
individual PO files, build a deb pack for this language and deploy
Hi Jordi,
On Thu, 2007-10-18 at 21:20 +0200, ext Jordi Mas wrote:
Is there any way to translate the UI into a language not supported
directly by Nokia?
If not, I would be possible from the community to localize the different
individual PO files, build a deb pack for this language
Hello Quim,
The current system based on logical strings and not on standard open
source practices is open for change though, or at least not-closed to
changes. In fact I’m willing to push this feature to the maemo roadmap.
A problem here are the implications any change has on code, processes,
Thanks for this insightful email, let's not get it lost.
On Mon, 2007-10-22 at 22:43 +0200, ext Jordi Mas wrote:
May be makes sense to move all of this to a Wiki page (community
localization?) and start collecting all this feedback there.
Yes, please.
--
Quim Gil - http://maemo.org
Hi Jordi,
On Thu, 2007-10-18 at 21:20:11 +0200, Jordi Mas wrote:
It seems technically possible to localize the different components to
other languages since all the infrastructure is based on intltool and
seems very well internationalized.
Well, the source code is using logical strings, which
On Thu, Oct 18, 2007 at 09:20:11PM +0200, Jordi Mas wrote:
I would like to explore the possibility of localizing Nokia N800 user
interface to languages that are not currently localized by Nokia itself[1].
I also.
It seems technically possible to localize the different components to
other
51 matches
Mail list logo