Re: Approaching LyX 1.5.6
Em Sábado, 19 de Julho de 2008, o Jürgen Spitzmüller escreveu: Ramon Flores wrote: I have took a look at the new pot file, and I have found some messages that I think shouldn't be there, because they shouldn't be translated. The messages are: ... 2726 PDFTEX 2728 PSTEX These are new: We now provide to opportunity to translate file formats. So the messages should be there, and they _can_ be transated, if this is necessary in some languages. Apologies for forgetting that there are other writing systems besides the latin alphabet.
Re: Approaching LyX 1.5.6
Em Sábado, 19 de Julho de 2008, o Jürgen Spitzmüller escreveu: > Ramon Flores wrote: > > I have took a look at the new pot file, and I have found some messages > > that I think shouldn't be there, because they shouldn't be translated. > > The messages are: ... > > 2726 PDFTEX > > 2728 PSTEX > > These are new: We now provide to opportunity to translate file formats. So > the messages should be there, and they _can_ be transated, if this is > necessary in some languages. Apologies for forgetting that there are other writing systems besides the latin alphabet.
Re: Approaching LyX 1.5.6
Em Quinta, 17 de Julho de 2008, o Jürgen Spitzmüller escreveu: Since I'll go to vacancies after next week, I'm trying to get 1.5.6 out at the end of next week. Therefore we'd need pending translation patches until Thursday, July 24. Translators, please let me know if you cannot make it until then. I have took a look at the new pot file, and I have found some messages that I think shouldn't be there, because they shouldn't be translated. The messages are: 2665 Tgif to 2679 XPM And some other messages as: 2720 LyX 1.3.x 2721 LyX 1.4.x 2726 PDFTEX 2728 PSTEX Cheers Ramom
Re: Approaching LyX 1.5.6
Em Quinta, 17 de Julho de 2008, o Jürgen Spitzmüller escreveu: > Since I'll go to vacancies after next week, I'm trying to get 1.5.6 out at > the end of next week. Therefore we'd need pending translation patches until > Thursday, July 24. Translators, please let me know if you cannot make it > until then. I have took a look at the new pot file, and I have found some messages that I think shouldn't be there, because they shouldn't be translated. The messages are: 2665 Tgif to 2679 XPM And some other messages as: 2720 LyX 1.3.x 2721 LyX 1.4.x 2726 PDFTEX 2728 PSTEX Cheers Ramom
Translation of a message 3541
Hi: I'm the galician translator, and finishing the lyx-1.5.2 translation. But I can not figure what is the meaning of message 3541: No vertical grid lines in 'cases': feature %1$s So I would thank for a explanation of this message. Cheers Ramon
Translation of a message 3541
Hi: I'm the galician translator, and finishing the lyx-1.5.2 translation. But I can not figure what is the meaning of message 3541: No vertical grid lines in 'cases': feature %1$s So I would thank for a explanation of this message. Cheers Ramon
Re: 2 questions about translation
Jürgen Spitzmueller wrote: 1) How (or what) to translate (if necessary): Bitmap: $$AbsOrRelPathParent$$Basename Xfig: $$AbsOrRelPathParent$$Basename Chess: $$AbsOrRelPathParent$$Basename Only the part before the colon, i.e. Bitmap, Xfig and Chess. The rest is substituted by a filename later. Thanks. Pavel Sanda wrote: note that if you want the translation in 1.5.0 you are short of time... (1 day left ?:) Thanks for remembering it to me. My translation was almost ready, and I have sent it some half an hour ago. And 5 minutes later it was in, thanks to Jean-Marc. 2) Running lyx from console the following error appears: Menu warning: menu entry Texto simples... does not contain shortcut `a'. http://bugzilla.lyx.org/show_bug.cgi?id=3548 I'm afraid that I can not bypass this bug. Thanks for the link. Cheers Ramon
Re: 2 questions about translation
Jürgen Spitzmueller wrote: >> 1) How (or what) to translate (if necessary): >> >> Bitmap: $$AbsOrRelPathParent$$Basename >> Xfig: $$AbsOrRelPathParent$$Basename >> Chess: $$AbsOrRelPathParent$$Basename >Only the part before the colon, i.e. "Bitmap", "Xfig" and "Chess". The rest >is substituted by a filename later. Thanks. Pavel Sanda wrote: > note that if you want the translation in 1.5.0 you are short of time... > (1 day left ?:) Thanks for remembering it to me. My translation was almost ready, and I have sent it some half an hour ago. And 5 minutes later it was in, thanks to Jean-Marc. > > > 2) Running lyx from console the following error appears: > > > > Menu warning: menu entry "Texto simples..." does not contain shortcut > > `a'. > > http://bugzilla.lyx.org/show_bug.cgi?id=3548 I'm afraid that I can not bypass this bug. Thanks for the link. Cheers Ramon
translating lyx-1.5.0
Hi: I'm the galician translator of Lyx. Updating lyx-1.5.0 I have found a lot of messages that correspond to latex commands, more exactly from message 2148 to message 2612. These messages correspond to tooltips that appear when the user hover the cursor over a symbol of the math toolbar. In English, these messages are the latex commands corresponding to the symbols that can be selected from the math toolbar. If the writer know the latex name for a symbol, is quicker to write it with the keyboard that to select it with the mouse. So, as there is not a galician version of LaTeX, I considered more useful not to translate these messages. So the user can learn the names of the symbols, and enter them by keyboard. So I would know what the other translators think about the following questions: 1) Are LaTeX command translated to any language?. If not, and I think that there are no translation, then 2) what is the point of translating those messages in LyX. Surely yours Ramon
Re: translating lyx-1.5.0
Jean-Marc Lasgouttes wrote: Uwe The commands itself like \linebreak are not translated, the Uwe rest is usually translated. Michael and JMarc can tell you more Uwe about this. The commands should not be translated indeed. What are typical examples of commands? #: lib/ui/stdtoolbars.inc:316 msgid overline msgstr #: lib/ui/stdtoolbars.inc:317 msgid overbrace msgstr #: lib/ui/stdtoolbars.inc:318 msgid overleftarrow msgstr #: lib/ui/stdtoolbars.inc:319 msgid overrightarrow msgstr === Pavel Sanda wrote: http://www.mail-archive.com/[EMAIL PROTECTED]/msg114471.html I haven't see this message. But I agree. Cheers Ramon
translating lyx-1.5.0
Hi: I'm the galician translator of Lyx. Updating lyx-1.5.0 I have found a lot of messages that correspond to latex commands, more exactly from message 2148 to message 2612. These messages correspond to tooltips that appear when the user hover the cursor over a symbol of the math toolbar. In English, these messages are the latex commands corresponding to the symbols that can be selected from the math toolbar. If the writer know the latex name for a symbol, is quicker to write it with the keyboard that to select it with the mouse. So, as there is not a galician version of LaTeX, I considered more useful not to translate these messages. So the user can learn the names of the symbols, and enter them by keyboard. So I would know what the other translators think about the following questions: 1) Are LaTeX command translated to any language?. If not, and I think that there are no translation, then 2) what is the point of translating those messages in LyX. Surely yours Ramon
Re: translating lyx-1.5.0
Jean-Marc Lasgouttes wrote: > Uwe> The commands itself like "\linebreak" are not translated, the > Uwe> rest is usually translated. Michael and JMarc can tell you more > Uwe> about this. > > The commands should not be translated indeed. What are typical > examples of commands? #: lib/ui/stdtoolbars.inc:316 msgid "overline" msgstr "" #: lib/ui/stdtoolbars.inc:317 msgid "overbrace" msgstr "" #: lib/ui/stdtoolbars.inc:318 msgid "overleftarrow" msgstr "" #: lib/ui/stdtoolbars.inc:319 msgid "overrightarrow" msgstr "" === Pavel Sanda wrote: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg114471.html I haven't see this message. But I agree. Cheers Ramon
Re: PO files FAQ
Hi, I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: 1) Not always LANG variable works. Sometimes is necessary to use another variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx 2) In order to test the translation it is necessary to test if the language use to make the translation is accepted by lyx. I.e. if the language is in the text file languages. 3) If the language used to make the translation is in the text file languages, it is not necessary to compile lyx. In this case is enough to compile the po file, with the command msgfmt that is part of the gettext packet. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html http://gnuwin32.sourceforge.net/packages/gettext.htm Bye Ramon
Re: PO files FAQ
Hi, I think it is a very good idea to write this FAQ, and to put it in the wiki. So I would like to make some comments: 1) Not always LANG variable works. Sometimes is necessary to use another variable. For example with Mandriva 2006 with KDE you need to use KDE_LANG, and with Mandriva 2007, and KDE, it is necessary to use LC_ALL. Ex: a) KDE_LANG=xx_CC lyx b) LC_ALL=xx_CC lyx 2) In order to test the translation it is necessary to test if the language use to make the translation is accepted by lyx. I.e. if the language is in the text file "languages". 3) If the language used to make the translation is in the text file "languages", it is not necessary to compile lyx. In this case is enough to compile the po file, with the command "msgfmt" that is part of the gettext packet. http://www.gnu.org/software/gettext/manual/html_mono/gettext.html http://gnuwin32.sourceforge.net/packages/gettext.htm Bye Ramon
