Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2004-03

Re: fpc l10n issue

4 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Peter Vreman
to Rimgaudas Laucius: 1) did you thought ever about creation l10n framework for fpc? I think contributors could…
Show quoted text 7 lines
Hello, 1) did you thought ever about creation l10n framework for fpc? I think contributors could submit translated fpc messages files (.msg) and other locale dependent stuff there. It needs tool for merging translated messages from one version to higher also.

resourcestrings and the gettext unit provided a way to translate messages using the standard gettext tools. For the compiler this can not be used for speed reasons.

Show quoted text 8 lines
2) there is some messages like this: "Expected $1". We translated these messages, but stuff that comes from compiler under "$1" remains untranslated for example "Identifier" because it is hardcoded (i explored 1.0.6 v.). Can this be solved in future? For examle extracting those strings from compiler source to the messages file.

There are only a few that can be translated. Most are keywords that are untranslatable.

Reply by email

Michael Van Canneyt
to Rimgaudas Laucius: 1) did you thought ever about creation l10n framework for fpc? I think contributors could…
Rimgaudas Laucius wrote 6 lines
Hello, 1) did you thought ever about creation l10n framework for fpc? I think contributors could submit translated fpc messages files (.msg) and other locale dependent stuff there. It needs tool for merging translated messages from one version to higher also.

This exists already. the msgdif tool does this. (see compiler/utils)

Show quoted text 5 lines
2) there is some messages like this: "Expected $1". We translated these messages, but stuff that comes from compiler under "$1" remains untranslated for example "Identifier" because it is hardcoded (i explored 1.0.6 v.). Can this be solved in future? For examle extracting those strings from compiler source to the messages file.

This could be done, but one of the compiler people would need to look into this.

Michael.

Reply by email

Rimgaudas Laucius

Hello,

1) did you thought ever about creation l10n framework for fpc? I think contributors could submit translated fpc messages files (.msg) and other locale dependent stuff there. It needs tool for merging translated messages from one version to higher also.

2) there is some messages like this: "Expected $1". We translated these messages, but stuff that comes from compiler under "$1" remains untranslated for example "Identifier" because it is hardcoded (i explored 1.0.6 v.). Can this be solved in future? For examle extracting those strings from compiler source to the messages file.

Reply by email

Florian Klaempfl
to Michael Van Canneyt: This exists already. the msgdif tool does this. (see compiler/utils) This could be done,…
Michael Van Canneyt wrote 13 lines
On Wed, 3 Mar 2004, Rimgaudas Laucius wrote: >Hello, > >1) did you thought ever about creation l10n framework for fpc? I think >contributors could submit translated fpc messages files (.msg) and other >locale dependent stuff there. It needs tool for merging translated messages >from one version to higher also. This exists already. the msgdif tool does this. (see compiler/utils)

msgdif is broken for years :/

Reply by email