"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars 3. means to extract the needed informatin from the babel
Lars .ldf files. This not be too hard and using the substring and the
Lars regex class form the old 1.1.x series should help a lot.
It would not be too difficult to write a
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Note that we only care about the default menus, user modified
Lars menus we can do nothing about. What do you mean by "hardcode
Lars translations"? We will add the menu definitions file to the list
Lars of files gettext scans for
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| I mean that a user cannot, for example, put his own translation of
| menus in his local directory and have LyX use it.
Why not?
| I personally think
| that this feature of being able to modify LyX behaviour at user level
| is a very nice one.
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars 3. means to extract the needed informatin from the babel
| Lars .ldf files. This not be too hard and using the substring and the
| Lars regex class form the old 1.1.x series should
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars We have three options on when to extract language strings from
Lars the .ldf files: 1. static (we extract and distribute with lyx)
Lars 2. at configure time. 3. live from a running LyX.
Lars These are no listed in my reverse prefered
On Wed, Oct 13, 1999 at 01:45:50PM +0200, Lars Gullik Bjønnes wrote:
| The real problem I see is accents: in portugues.ldf, we have
| \def\refname{Refer\^encias}
Does \^ have special meaning in portugues? Or is it the regular accent
that insetlatexaccent is able to handle?
The later.
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes:
| On Wed, Oct 13, 1999 at 01:45:50PM +0200, Lars Gullik Bjønnes wrote:
|
| | The real problem I see is accents: in portugues.ldf, we have
| | \def\refname{Refer\^encias}
|
| Does \^ have special meaning in portugues? Or is it the
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: | I
Lars mean that a user cannot, for example, put his own translation of
Lars | menus in his local directory and have LyX use it.
Lars Why not?
Because po files cannot be used like
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars We have three options on when to extract language strings from
| Lars the .ldf files: 1. static (we extract and distribute with lyx)
| Lars 2. at configure time. 3. live from a
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
|
| Lars We have three options on when to extract language strings from
| Lars the .ldf files: 1. static (we extract and distribute with lyx)
| Lars 2. at configure time. 3. live from a
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars We just need a module that knows how to display cyrillic, a lot
Lars of these problems will go away/be easier to solve when/if we
Lars switch to unicode.
Lars I am beginning to leand towards using unicode internally in LyX
Lars all
Fully automatic please...
One note though:
Fully automatic seems best, but it is also the most risky. We do not have
control over which strange LaTeX installatinopneople have, and therefore
we would need to build a robust system if it has to work on everything
out there.
I think that a static
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] writes:
| Fully automatic please...
|
| One note though:
|
| Fully automatic seems best, but it is also the most risky. We do not have
| control over which strange LaTeX installatinopneople have, and therefore
| we would need to build a robust
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] wrote:
- muddle on with gettext
This is the least intrusive solution, and thus the safest one.
Do you mean something like:
/* FileGetText: This is C. */
/* Use it as
#define __(str) fgettext(\
LibFileSearch(\
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> 3. means to extract the needed informatin from the babel
Lars> .ldf files. This not be too hard and using the substring and the
Lars> regex class form the old 1.1.x series should help a lot.
It would not be too difficult to
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Note that we only care about the default menus, user modified
Lars> menus we can do nothing about. What do you mean by "hardcode
Lars> translations"? We will add the menu definitions file to the list
Lars> of files gettext
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| I mean that a user cannot, for example, put his own translation of
| menus in his local directory and have LyX use it.
Why not?
| I personally think
| that this feature of being able to modify LyX behaviour at user level
| is a very nice one.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> 3. means to extract the needed informatin from the babel
| Lars> .ldf files. This not be too hard and using the substring and the
| Lars> regex class form the old 1.1.x
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> We have three options on when to extract language strings from
Lars> the .ldf files: 1. static (we extract and distribute with lyx)
Lars> 2. at configure time. 3. live from a running LyX.
Lars> These are no listed in my
On Wed, Oct 13, 1999 at 01:45:50PM +0200, Lars Gullik Bjønnes wrote:
>
> | The real problem I see is accents: in portugues.ldf, we have
> | \def\refname{Refer\^encias}
>
> Does \^ have special meaning in portugues? Or is it the regular accent
> that insetlatexaccent is able to handle?
The
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
| On Wed, Oct 13, 1999 at 01:45:50PM +0200, Lars Gullik Bjønnes wrote:
| >
| > | The real problem I see is accents: in portugues.ldf, we have
| > | \def\refname{Refer\^encias}
| >
| > Does \^ have special meaning in portugues? Or is it
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | I
Lars> mean that a user cannot, for example, put his own translation of
Lars> | menus in his local directory and have LyX use it.
Lars> Why not?
Because po files cannot be
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> We have three options on when to extract language strings from
| Lars> the .ldf files: 1. static (we extract and distribute with lyx)
| Lars> 2. at configure time. 3.
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> We have three options on when to extract language strings from
| Lars> the .ldf files: 1. static (we extract and distribute with lyx)
| Lars> 2. at configure time. 3.
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> We just need a module that knows how to display cyrillic, a lot
Lars> of these problems will go away/be easier to solve when/if we
Lars> switch to unicode.
Lars> I am beginning to leand towards using unicode internally in LyX
> Fully automatic please...
One note though:
Fully automatic seems best, but it is also the most risky. We do not have
control over which strange LaTeX installatinopneople have, and therefore
we would need to build a robust system if it has to work on everything
out there.
I think that a
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > Fully automatic please...
|
| One note though:
|
| Fully automatic seems best, but it is also the most risky. We do not have
| control over which strange LaTeX installatinopneople have, and therefore
| we would need to build a robust
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> wrote:
> > - muddle on with gettext
>
> This is the least intrusive solution, and thus the safest one.
Do you mean something like:
/* FileGetText: This is C. */
/* Use it as
#define __(str) fgettext(\
LibFileSearch(\
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] writes:
| I think Jean-Marc is right ;), if we introduce this we want it right
| straight away and as this is document specific it's related to the
| document and not to the locale. We have so many hacks in the source
|
| I agree with the original
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars I am beginning to agree with Jean-Marc that gettext is unable to
Lars handle this case. (a gettext written for C++ using the C++
Lars notion of locale would work)
Lars Using gettext would be just a shorterm fix, and it would only be
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| 1) localize the name of the layouts in the GUI and the menus (once we
|have ported the new menu system). gettext is able to handle that,
|but this means we have to hardcode translations of things which ar
|enot compiled in. For me,
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] writes:
| Using gettext would be just a shorterm fix, and it would only be
| correct when the locale lang is equal to the doc lang.
|
| ...and therefore, we can't expect that we will have that in the shortterm.
| So, I think we should include the
I am beginning to agree with Jean-Marc that gettext is unable to
handle this case. (a gettext written for C++ using the C++ notion of
locale would work)
Yes, gettext will have a hard time to handle this. We need to implement
our own translation facility to do this right...
Using gettext
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > I think Jean-Marc is right ;), if we introduce this we want it right
| > straight away and as this is document specific it's related to the
| > document and not to the locale. We have so many hacks in the source
|
| I agree with the
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I am beginning to agree with Jean-Marc that gettext is unable to
Lars> handle this case. (a gettext written for C++ using the C++
Lars> notion of locale would work)
Lars> Using gettext would be just a shorterm fix, and it
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| 1) localize the name of the layouts in the GUI and the menus (once we
|have ported the new menu system). gettext is able to handle that,
|but this means we have to hardcode translations of things which ar
|enot compiled in. For me,
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| > Using gettext would be just a shorterm fix, and it would only be
| > correct when the locale lang is equal to the doc lang.
|
| ...and therefore, we can't expect that we will have that in the shortterm.
| So, I think we should include
> I am beginning to agree with Jean-Marc that gettext is unable to
> handle this case. (a gettext written for C++ using the C++ notion of
> locale would work)
Yes, gettext will have a hard time to handle this. We need to implement
our own translation facility to do this right...
> Using
On 08-Oct-99 David S de Lis wrote:
Hi all,
Hi David!
[sniped good explanation]
I think I'd like to hear other developers points of views regarding this
issue. As I said before, it's not big thing, but I thought it deserved a
defense... :)
I think Jean-Marc is right ;), if we introduce
I think Jean-Marc is right ;), if we introduce this we want it right
straight away and as this is document specific it's related to the
document and not to the locale. We have so many hacks in the source
I agree with the original poster that it's an improvement to translate
the fixed text to
On 08-Oct-99 David S de Lis wrote:
> Hi all,
Hi David!
[sniped good explanation]
>
> I think I'd like to hear other developers points of views regarding this
> issue. As I said before, it's not big thing, but I thought it deserved a
> defense... :)
I think Jean-Marc is right ;), if we
> I think Jean-Marc is right ;), if we introduce this we want it right
> straight away and as this is document specific it's related to the
> document and not to the locale. We have so many hacks in the source
I agree with the original poster that it's an improvement to translate
the fixed text
Hi all,
On 5 Oct 1999, Jean-Marc Lasgouttes wrote:
: David two more hackings (text.C and lyx_cb.C)
: David that allows to see the 'Chapter x' and 'Part #' on-screen in
: David the current locale as well as seeing 'Chapter x' in current
: David locale on the TOC popup... and corresponding
Hi all,
On 5 Oct 1999, Jean-Marc Lasgouttes wrote:
: David> two more hackings (text.C and lyx_cb.C)
: David> that allows to see the 'Chapter x' and 'Part #' on-screen in
: David> the current locale as well as seeing 'Chapter x' in current
: David> locale on the TOC popup... and corresponding
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars David S de Lis [EMAIL PROTECTED] writes: | I am sending along,
Lars as well as the bug fix to minibuffer.C (against | 1.0.4pre8),
Lars two more hackings (text.C and lyx_cb.C) that allows to see the |
Lars 'Chapter x' and 'Part #'
"David" == David S de Lis [EMAIL PROTECTED] writes:
David I am sending along, as well as the bug fix to minibuffer.C
David (against 1.0.4pre8),
I'll apply this minibuffer bugfix.
David two more hackings (text.C and lyx_cb.C)
David that allows to see the 'Chapter x' and 'Part #' on-screen in
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| This would be suitable indeed, since the name of the layout in the GUI
| should march the locale. I am not sure however of where this
| translation should be done. Lars prefers po files (for consistency),
| but I think that doing the translation
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars So you want to have additional "po-equivalent files"? How do you
Lars want this? Scattered around in the layout files?
Something like
fr_stdsections.inc:
---
Input* stdsections.inc
Style Chapter
GUIName
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> David S de Lis <[EMAIL PROTECTED]> writes: | I am sending along,
Lars> as well as the bug fix to minibuffer.C (against | 1.0.4pre8),
Lars> two more hackings (text.C and lyx_cb.C) that allows to see the |
Lars> 'Chapter x' and
> "David" == David S de Lis <[EMAIL PROTECTED]> writes:
David> I am sending along, as well as the bug fix to minibuffer.C
David> (against 1.0.4pre8),
I'll apply this minibuffer bugfix.
David> two more hackings (text.C and lyx_cb.C)
David> that allows to see the 'Chapter x' and 'Part #'
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| This would be suitable indeed, since the name of the layout in the GUI
| should march the locale. I am not sure however of where this
| translation should be done. Lars prefers po files (for consistency),
| but I think that doing the translation
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> So you want to have additional "po-equivalent files"? How do you
Lars> want this? Scattered around in the layout files?
Something like
fr_stdsections.inc:
---
Input* stdsections.inc
Style Chapter
"David" == David S de Lis [EMAIL PROTECTED] writes:
David I have updated es.po as to version 1.0.4pre8, I am sorry if I
David am late for 1.0.4 :(
David I am also sending a hack to allow i18n guys (like me) to see
David the welcome message in the minibuffer when LyX starts (which
David was
Hi again,
On 4 Oct 1999, Jean-Marc Lasgouttes wrote:
: "David" == David S de Lis [EMAIL PROTECTED] writes:
:
: David I have updated es.po as to version 1.0.4pre8, I am sorry if I
: David am late for 1.0.4 :(
:
: David I am also sending a hack to allow i18n guys (like me) to see
: David the
David S de Lis [EMAIL PROTECTED] writes:
| I am sending along, as well as the bug fix to minibuffer.C (against
| 1.0.4pre8), two more hackings (text.C and lyx_cb.C) that allows to see the
| 'Chapter x' and 'Part #' on-screen in the current locale as well as seeing
| 'Chapter x' in current locale
> "David" == David S de Lis <[EMAIL PROTECTED]> writes:
David> I have updated es.po as to version 1.0.4pre8, I am sorry if I
David> am late for 1.0.4 :(
David> I am also sending a hack to allow i18n guys (like me) to see
David> the welcome message in the minibuffer when LyX starts (which
Hi again,
On 4 Oct 1999, Jean-Marc Lasgouttes wrote:
: > "David" == David S de Lis <[EMAIL PROTECTED]> writes:
:
: David> I have updated es.po as to version 1.0.4pre8, I am sorry if I
: David> am late for 1.0.4 :(
:
: David> I am also sending a hack to allow i18n guys (like me) to see
:
David S de Lis <[EMAIL PROTECTED]> writes:
| I am sending along, as well as the bug fix to minibuffer.C (against
| 1.0.4pre8), two more hackings (text.C and lyx_cb.C) that allows to see the
| 'Chapter x' and 'Part #' on-screen in the current locale as well as seeing
| 'Chapter x' in current
Hi all!
I am back (sorta). They killed my old server rather badly (and without
notice)
I am hoping to find an email account that can support the burden of some
mailing lists... once I got it, I'll subscribe again...
I have updated es.po as to version 1.0.4pre8, I am sorry if I am late for
Hi all!
I am back (sorta). They killed my old server rather badly (and without
notice)
I am hoping to find an email account that can support the burden of some
mailing lists... once I got it, I'll subscribe again...
I have updated es.po as to version 1.0.4pre8, I am sorry if I am late for
60 matches
Mail list logo
