A good reason to fix it then. We shouldn't deviate from the macosx standard because we dont want to use insetinfo while this is exactly where insetinfos are intended for.
Im sure the fix will not be that difficult. Vincent Op 6 aug. 2011 17:59 schreef "Uwe Stöhr" <uwesto...@web.de> het volgende: > Am 06.08.2011 09:17, schrieb Jürgen Spitzmüller: > >> Rereading that report, I do not see a big problem that hiners us from using >> InsetInfo. This is just a copy and paste problem, isn't it? > > Pasting is correct because the language of course needs to be respected and kept. The problem that > the language cannot be changed. Highlighting the Inset and resetting the language has simply no effect. > The workaround is to create every InsetInfo new from scratch for every documentation file - an > absolute nightmare that would cost us many hours. > I had once a discussion with the translators and the result was not to use InsetInfo until this > issue if fixed because need our limited spare time for other things than to do create these Insets > again and again from scratch. > > regards Uwe
