Re: KOMA report and localisation problem.

2012-04-08 Thread Georg Baum
Pavel Sanda wrote: Georg, would it be easy to add Listing into the layouttranslation machinery we automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2) Does anything break if I make

Re: KOMA report and localisation problem.

2012-04-08 Thread Richard Heck
On 04/08/2012 03:48 PM, Georg Baum wrote: Pavel Sanda wrote: Georg, would it be easy to add Listing into the layouttranslation machinery we automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2)

Re: KOMA report and localisation problem.

2012-04-08 Thread Georg Baum
Pavel Sanda wrote: Georg, would it be easy to add Listing into the layouttranslation machinery we automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2) Does anything break if I make

Re: KOMA report and localisation problem.

2012-04-08 Thread Richard Heck
On 04/08/2012 03:48 PM, Georg Baum wrote: Pavel Sanda wrote: Georg, would it be easy to add Listing into the layouttranslation machinery we automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2)

Re: KOMA report and localisation problem.

2012-04-08 Thread Georg Baum
Pavel Sanda wrote: > Georg, > > would it be easy to add Listing into the layouttranslation machinery we > automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2) Does anything break if I make

Re: KOMA report and localisation problem.

2012-04-08 Thread Richard Heck
On 04/08/2012 03:48 PM, Georg Baum wrote: Pavel Sanda wrote: Georg, would it be easy to add Listing into the layouttranslation machinery we automatically use on the LyX side? Yes (see attachment). Two questions: 1) Why is features.useInsetLayout() not called for each inset in validate()? 2)

KOMA report and localisation problem.

2012-04-06 Thread Hannu Vuolasaho
Hi! I checked the translation through. The localization_test.lyx file could be more better it had some more real life samples. Which again is problematic since lyx can't embed graphics. I can clearly see why no-one wanted to touch it :) There are thousand ways to say I'm drunk and few

Finnish translation (was: KOMA report and localisation problem.)

2012-04-06 Thread Pavel Sanda
Hannu Vuolasaho wrote:  401  Translation fi  402 Acknowledgement Kiitos This translates thank you. It is OK if some some equation or something was given by someone else and then writer wants to give credit for that. If it is used as telling something is true then it fails. It is

KOMA report and localisation problem.

2012-04-06 Thread Hannu Vuolasaho
Hi! I checked the translation through. The localization_test.lyx file could be more better it had some more real life samples. Which again is problematic since lyx can't embed graphics. I can clearly see why no-one wanted to touch it :) There are thousand ways to say I'm drunk and few

Finnish translation (was: KOMA report and localisation problem.)

2012-04-06 Thread Pavel Sanda
Hannu Vuolasaho wrote:  401  Translation fi  402 Acknowledgement Kiitos This translates thank you. It is OK if some some equation or something was given by someone else and then writer wants to give credit for that. If it is used as telling something is true then it fails. It is

KOMA report and localisation problem.

2012-04-06 Thread Hannu Vuolasaho
Hi! I checked the translation through. The localization_test.lyx file could be more better it had some more real life samples. Which again is problematic since lyx can't embed graphics. I can clearly see why no-one wanted to touch it :) There are thousand ways to say I'm drunk and few

Finnish translation (was: KOMA report and localisation problem.)

2012-04-06 Thread Pavel Sanda
Hannu Vuolasaho wrote: >  401  Translation fi >  402 "Acknowledgement" "Kiitos" > This translates thank you. It is OK if some some equation or something was > given by someone else and then writer wants to give credit for that. If it is > used as telling something is true then it fails.

Re: KOMA report and localisation problem.

2012-04-05 Thread Guenter Milde
On 2012-04-04, Richard Heck wrote: On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Localization of

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 02:42 AM, Guenter Milde wrote: On 2012-04-04, Richard Heck wrote: On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Well, that's a mystery. I see the problem here, too, on the LyX side. The translations seem to be there, though, in the

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part}

Re: KOMA report and localisation problem.

2012-04-05 Thread Jean-Marc Lasgouttes
Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part} This is what I was about to answer. Note how the translation is marked fuzzy. Perhaps we're not using it, then. The same is true of

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 09:03 AM, Jean-Marc Lasgouttes wrote: Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part} This is what I was about to answer. Note how the translation is marked fuzzy.

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Hi! I added ticket. http://www.lyx.org/trac/ticket/8115 Next starts to be more Latex question. I tried to understand how babel works but I couldn't set up preamble so that lstlistname or listname changes. Are there any tricks? I wouldn't want to override systemfiles to get what I want since

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Just to inform a bit ERT magic  \renewcommand{\lstlistingname}{Listaus} before any listing does what I want it to do. For now all my problems are solved. Thanks everyone. best regards, Hannu Vuolasaho

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 12:24 PM, Hannu Vuolasaho wrote: An in /usr/share/texmf-dist/tex/latex/listings/listings.sty\lst@UserCommand\lstlistingname{Listing} Now. If I'm correct \lstlistingname always generates word Listing. Is there any way to override that so it generates Listaus, except writing the

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: Hi! I added ticket. http://www.lyx.org/trac/ticket/8115 Hi! :) There is worse problem with Finnish - we were not able to contact any native speaker to review translation of some environments which are used in TeX output (i.e. PDF output), not just on screen. Please

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source listing says in

Re: KOMA report and localisation problem.

2012-04-05 Thread Guenter Milde
On 2012-04-04, Richard Heck wrote: On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Localization of

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 02:42 AM, Guenter Milde wrote: On 2012-04-04, Richard Heck wrote: On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Well, that's a mystery. I see the problem here, too, on the LyX side. The translations seem to be there, though, in the

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part}

Re: KOMA report and localisation problem.

2012-04-05 Thread Jean-Marc Lasgouttes
Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part} This is what I was about to answer. Note how the translation is marked fuzzy. Perhaps we're not using it, then. The same is true of

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 09:03 AM, Jean-Marc Lasgouttes wrote: Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid Part \\Roman{part} msgstr \\Roman{part} This is what I was about to answer. Note how the translation is marked fuzzy.

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Hi! I added ticket. http://www.lyx.org/trac/ticket/8115 Next starts to be more Latex question. I tried to understand how babel works but I couldn't set up preamble so that lstlistname or listname changes. Are there any tricks? I wouldn't want to override systemfiles to get what I want since

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Just to inform a bit ERT magic  \renewcommand{\lstlistingname}{Listaus} before any listing does what I want it to do. For now all my problems are solved. Thanks everyone. best regards, Hannu Vuolasaho

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 12:24 PM, Hannu Vuolasaho wrote: An in /usr/share/texmf-dist/tex/latex/listings/listings.sty\lst@UserCommand\lstlistingname{Listing} Now. If I'm correct \lstlistingname always generates word Listing. Is there any way to override that so it generates Listaus, except writing the

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: Hi! I added ticket. http://www.lyx.org/trac/ticket/8115 Hi! :) There is worse problem with Finnish - we were not able to contact any native speaker to review translation of some environments which are used in TeX output (i.e. PDF output), not just on screen. Please

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source listing says in

Re: KOMA report and localisation problem.

2012-04-05 Thread Guenter Milde
On 2012-04-04, Richard Heck wrote: > On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: >> Hi! >> I'm writing KOMA report class document and it behaves weird. In Lyx I >> have Part N and in pdf I get part in Finnish as expected. This is >> acceptable even I was curious if it would translate.

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 02:42 AM, Guenter Milde wrote: On 2012-04-04, Richard Heck wrote: On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Well, that's a mystery. I see the problem here, too, on the LyX side. The translations seem to be there, though, in the

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 08:44 AM, Hannu Vuolasaho wrote: OK. Here is simplest translation sample. Shows both problems. Lyx file, pdf and screenshot of Lyx. The version of Lyx is 2.0.3 Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid "Part \\Roman{part}" msgstr

Re: KOMA report and localisation problem.

2012-04-05 Thread Jean-Marc Lasgouttes
Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid "Part \\Roman{part}" msgstr "\\Roman{part}" This is what I was about to answer. Note how the translation is marked "fuzzy". Perhaps we're not using it, then. The same is

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 09:03 AM, Jean-Marc Lasgouttes wrote: Le 05/04/2012 14:59, Richard Heck a écrit : Maybe this is the problem: #: lib/layouts/stdcounters.inc:10 #, fuzzy msgid "Part \\Roman{part}" msgstr "\\Roman{part}" This is what I was about to answer. Note how the translation is marked

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Hi! I added ticket. http://www.lyx.org/trac/ticket/8115 Next starts to be more Latex question. I tried to understand how babel works but I couldn't set up preamble so that lstlistname or listname changes. Are there any tricks? I wouldn't want to override systemfiles to get what I want since

RE: KOMA report and localisation problem.

2012-04-05 Thread Hannu Vuolasaho
Just to inform a bit ERT magic  \renewcommand{\lstlistingname}{Listaus} before any listing does what I want it to do. For now all my problems are solved. Thanks everyone. best regards, Hannu Vuolasaho

Re: KOMA report and localisation problem.

2012-04-05 Thread Richard Heck
On 04/05/2012 12:24 PM, Hannu Vuolasaho wrote: An in /usr/share/texmf-dist/tex/latex/listings/listings.sty\lst@UserCommand\lstlistingname{Listing} Now. If I'm correct \lstlistingname always generates word Listing. Is there any way to override that so it generates "Listaus", except writing the

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: > > Hi! > > I added ticket. > http://www.lyx.org/trac/ticket/8115 Hi! :) There is worse problem with Finnish - we were not able to contact any native speaker to review translation of some environments which are used in TeX output (i.e. PDF output), not just on screen.

Re: KOMA report and localisation problem.

2012-04-05 Thread Pavel Sanda
Hannu Vuolasaho wrote: > > Hi! > > I'm writing KOMA report class document and it behaves weird. In Lyx I have > Part N and in pdf I get part in Finnish as expected. This is acceptable even > I was curious if it would translate. Now I have source code listing. The > caption of source listing

Re: KOMA report and localisation problem.

2012-04-04 Thread Richard Heck
On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source

Re: KOMA report and localisation problem.

2012-04-04 Thread Richard Heck
On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source

Re: KOMA report and localisation problem.

2012-04-04 Thread Richard Heck
On 04/03/2012 09:55 PM, Hannu Vuolasaho wrote: Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source

KOMA report and localisation problem.

2012-04-03 Thread Hannu Vuolasaho
Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source listing says in Finnish that it is listing

KOMA report and localisation problem.

2012-04-03 Thread Hannu Vuolasaho
Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source listing says in Finnish that it is listing

KOMA report and localisation problem.

2012-04-03 Thread Hannu Vuolasaho
Hi! I'm writing KOMA report class document and it behaves weird. In Lyx I have Part N and in pdf I get part in Finnish as expected. This is acceptable even I was curious if it would translate. Now I have source code listing. The caption of source listing says in Finnish that it is listing