LyX Web site
Hello, I recently begun the translation of the site to French, and I have a suggestion: use mdash instead of -- wherever it happens (currently I found some in http://www.lyx.org/WhatIsLyX ). Regards -- Jean-Pierre
Re: LyX Web site
Helge Hafting a écrit : Jean-Pierre Chrétien wrote: Hello, I recently begun the translation of the site to French, and I have a suggestion: use mdash instead of -- wherever it happens (currently I found some in http://www.lyx.org/WhatIsLyX ). When you use -- in LyX, an endash happens in the output, and --- turns into emdash. This is why some LyX users use -- now and then. Sure, I use it myself. But unless pmwiki provides a similar mechanism, as Jean-Marc suggested, HTML entities are required in the web site. -- Jean-Pierre
Re: To translators of the web site. SiteTranslation now a bit better
Christian Ridderström a écrit : Hi, I've fiddled (more than I expected, guess I'm rusty), and the page http://www.lyx.org/SiteTranslation now should show translated pages in _red_ if the corresponding english page has been edited more recently. In case the translated page has been edited more recently, it's shown in green. Well done, Christian, thanks. -- Jean-Pierre
Re: Offre d'aide
frederic.steve...@ac-amiens.fr a écrit : Bonjour, J'utilise LyX depuis quelques années, par intermittence. En retour, je peux vous proposer mes services, même si mes compétences ne sont pas bien grandes : je ne programme pas, mais je peux traduire, par exemple, corriger des documents en français (syntaxe, grammaire, typographie, vocabulaire). Si vous pensez que je puisse être d'une quelconque utilité, n'hésitez pas. Merci pour votre proposition, mais la langue d'usage de lyx-docs est l'anglais, il existe la liste lyx-fr spécifique au français: lyx-fr at lists.lyx.org So I will forward your mail on lyx-fr and answer there. Thanks and regards. -- Jean-Pierre
Web site translation: how to use SVN
Hello, While translating this page in French, these sentences This is the new development and stable branch. The development will progress in branches and the main trunk will stay stable. were unclear to me. I suggest This is the new development and stable branch. The development will progress in the main trunk and the stable successive versions can be found in branches. The most recent branches/BRANCH_X_X_X directory is however still active to provide maintenance releases of the current stable version. -- Jean-Pierre
Braille example in French
Hello, Attached is a tentative Freanch version of the Braille example. I am not a specialist of Braille, but I feel that Braille support in LyX for French suffers from the limitations of Braille support in LaTeX for foreign languages (the Maj modifier is not the same in English Braille and in French Braille e.g.). In addition - active characters in French babel do not work in the Braille commands, I tried to add english encaspsulation to avoid LaTeX errors without success; - the French guillemets (set in Document-Settings-Language) do not work. About the latter, it seems that this is a recent regression in branch w.r.t 1.6.3. I thought first that it was due to the fact that the doc is Unicode in LaTeX, but it is true with a fresh article doc. Any ticket about this ? -- Jean-Pierre Braille.lyx Description: application/lyx
Re: Braille example in French
Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: [...] The Braille package only supports English. For all language-specific characters you have to use the braillebox environment. Can you please add a sentence that this is also the case for the French Maj modifier? Attached is an updated version. In addition - active characters in French babel do not work in the Braille Same problem as above, Braille doesn't take care of language-specific things and thus also not of babel. Corrected in the preamble. Btw, why are the greyed notes in Braille style ? I loose the guillemets there when I fall back to english babel to avoid active chars. - the French guillemets (set in Document-Settings-Language) do not work. Works fine there with today's branch build. Right, in fact svn up make is not enough to refresh lyx, I will run the full update command in the future. Regards -- Jean-Pierre Braille.lyx Description: application/lyx
[Fwd: Delivery Status Notification (Failure)]
Hello, po-upda...@lyx.org seems to be down... Any clue ? -- Jean-Pierre Message original Sujet : Delivery Status Notification (Failure) Date : Mon, 28 Sep 2009 06:42:40 -0700 (PDT) De : Mail Delivery Subsystem mailer-dae...@googlemail.com Pour : jeanpierre.chret...@free.fr This is an automatically generated Delivery Status Notification Delivery to the following recipient failed permanently: po-upda...@lyx.org - Original message - [...] To: po-upda...@lyx.org Subject: [Fwd: fr.po for branch] Content-Type: multipart/mixed; boundary=060902010508080605030603 This is a multi-part message in MIME format. --060902010508080605030603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message original Sujet : fr.po for branch Date : Mon, 28 Sep 2009 15:36:37 +0200 - Message truncated -
French translation of the web site
Hello, The translation is quite complete and up to date, thanks to Siegfried and Alain: http://www.lyx.org/SiteTranslation#toc5 Is there a way to display the French pages if the browser is French-speaking ? -- Jean-Pierre
Re: French translation of the web site
Christian Ridderström a écrit : On Wed, 7 Oct 2009, Jean-Marc Lasgouttes wrote: Jean-Pierre Chrétien jeanpierre.chret...@free.fr writes: Is there a way to display the French pages if the browser is French-speaking ? I have proposed this in the past, but Christian was not sure he wanted it. I still think we should (at least for languages that are considered to be complete enough) By now I've forgotten any objections I might have had, so for me it's fine. Of course, I've also completely forgotten how this would be implemented... I'm rather busy so if either you do it, or I'm given some algorithm. AFAIR, needs directives on the server side. LyX pretends that the server name is none of my business :-( If it's Apache, language negotiation may be on by default: AddLanguage da .dk AddLanguage nl .nl AddLanguage en .en AddLanguage et .et AddLanguage fr .fr AddLanguage de .de AddLanguage he .he ... but the mechanism does not seem compatible with pmwiki, as it requires pages in different languages to have suffices like .fr, .de, etc. I guess that this was the problem that raised objections from you at the time. Forget about my suggestion. -- Jean-Pierre
Re: fr.po for branch + Intro.lyx
Jürgen Spitzmüller a écrit : However, your new version has the following diff: - Il y a aussi une site de référence pour les traductions en français, sur - laquelle vous pouvez télécharger les fichiers les plus récents + Il y a aussi une site de référence pour les traductions en français Should this go in? No, I simplified the phrase a bit (to account for the fact that the current version of the docs are now published on the wiki), but we may publish there prereleases of the lyx-2.0 docs, so you can leave it as it is. -- Jean-Pierre
Re: xypic.lyx in French update
Uwe Stöhr a écrit : One tip: When you need to use a multiplication sign like in 3x3 matrix, you can insert it via the menu Insert-Special Character-Symbols. I therefore replaced the formula with this sign in your file. I followed the chktex hints and typed in \times in Math. To use your tip, you must know which alphabet to parse: here I have Latin-1 supplement as default, and I had to display all characters and to parse them carefully to find out a x sign in Casseau. Is that the right one ? -- Jean-Pierre
powerdot-example
Hello, Please find attached a French translation of the powerdot-example file, named exemple-powerdot.lyx. I removed the \usepackage{listings} command in the premable, as I guess that it is no more needed since listings has been intefaced with LyX. I get some warnings in the command window, like: Counter section does not exist. step: Counter does not exist: subsection -- Jean-Pierre exemple-powerdot.lyx Description: application/lyx
Re: How to update fr.po in trunk
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: Is it correct to merge fr.po in trunk and fr.po in branch like this to backport my branch updates in trunk ? I usually do this manually, using Lokalize (the KDE 4 po editor), which provides nifty abilities to sync/merge two po files. You can select branch's fr.po as secondary sync source, navigate through all messages that are different there and directly copy them to trunk's po file. I could do this with XEmacs po-mode, but I went to poedit when the po-files were converted to UTF-8. I run Debian stable, KDE-4 is not available so I can't use loKalize. I guess I will test the msgmerge path, seems efficient as it found 53-17 = 36 messages in branch that came translated in trunk (these come from string changes committed both in branch and in trunk). I guess also that most of the 257-143=114 new fuzzies come from the branch file unification steps. -- Jean-Pierre
Re: powerdot-example
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: I doubt so. Are you sure you're really using that file? Sorry, I think I get confused between the two versions of exemple-powerdot.lyx, I get your errors all right when I copy the file I attached to my mail into the temporary. -- Jean-Pierre
Re: Layout for a letter (in French)
Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: Some remarks: - the layout file doesn't follow our layout file style and is in the quite old format 4 OK, I will check this - you use a lot of preamble code in the layout file, it this really needed? I didn't write the code, I guess it is needed to be able to type in the various elements of the letter in any order, I will review it. - in the preamble of the LyX example file you load the packages * lmodern - this is unnecessary because the user can decide in the document settings what font to use Right. * itemsep - this is not necessary as the file doesn't contain items. (When you really want to have no item separation, don't load this style file but set the length \itemsep to 0pt.) Right. - you used the LaTeX class lettre for your layout file. What about the other letter document classes LyX already supports? dinbrief and g-brief2 are in German but its strings can easily be translated to French. have you already had a look if support for them might be useful? Yes, these letter layouts do not follow the French presentation of letters. I guess this is the reason why there are several German alternatives to the letter layout. -- Jean-Pierre
Example file seminar.lyx translation in French
Hello, Please find attached a French translation of the example. Note that the English version suffers from the bug described in the last slide: a4paper appears a class option, so that the complilation fails with earlier versions of seminar. I suppressed it in the translated file. In addition I find the explanation unclear, I would suggest: ...in the menu Document-Settings-Page Layout set the Paper Size to “a4” (unless it is the default layout of your LaTeX distribution) and remove a4paper... The first note says nothing about PDF (ps2pdf). Here I find it better than dvipdfm: the third slide does not appear rotated. Finally, I think that the layout could be modified to get the slideheadings next to the slide control styles. I guess this will wait 1.6.6. -- Jean-Pierre seminar.lyx Description: application/lyx
Re: powerdot-example
Ignacio Garcia a écrit : This issue remains too: the author names don't appear in the pdf output. It happens also with the English version in branch. Is it true for you? Putting the LyX note in the Title environment, beside A LyX sample, fix it here. Right, here is an updated version of the French translation. -- Jean-Pierre exemple-powerdot.lyx Description: application/lyx
Re: Beamer example update
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: I see that the English and German Beamer templates are updated. Do I have time to update also the French template ? If you can send it very quick (within the next hours), I can consider it. Here it is. -- Jean-Pierre fr_beamer-conference-ornate-20min.lyx Description: application/lyx
Shortcut conflicts in the French interface
Hello, While editing an example file for crossref implementations in LyX, I found a couple of shortcut conflicts I had overlooked (in math context menus, like Menus.cpp(587): Menu warning: menu entries Ajouter une ligne au-dessus|A and Environnement AMS|A share the same shortcut. If you are aware of such conflicts, please post me the messages that you may see in the command window from which you started LyX (on Linux, I don't know where to see these messages on Windows). TIA -- Jean-Pierre
Re: Shortcut conflicts in the French interface
Jean-Pierre Chrétien a écrit : If you are aware of such conflicts, please post me the messages that you may see in the command window from which you started LyX (on Linux, I don't know where to see these messages on Windows). My post only concerns the French interface. I posted it in French on the lyx-fr mailing list, and I cross-posted it on lyx-users and lyx-docs, please answer only on one of these lists, thank you. -- Jean-Pierre
Update of UserGuide and EmbeddedObjects manuals
Hello, Following discussions in ticket #6608, please find attached updates of these manuals (sections 6.1 in UserGuide and 3.4.1 in EmbeddedObjects), with change tracking. I guess that thes files won't go through the mailing list, so I post patches wrt the current versions of the manuals in branch. I've already translated in French, I'll post it later. -- Jean-Pierre --- UserGuide.lyx.orig 2010-04-19 18:01:47.0 +0200 +++ UserGuide.lyx 2010-04-20 10:39:34.0 +0200 @@ -108,9 +108,9 @@ \papercolumns 1 \papersides 2 \paperpagestyle default -\tracking_changes false +\tracking_changes true \output_changes false -\author +\author Jean-Pierre \author \end_header @@ -24445,8 +24445,24 @@ \end_layout \begin_layout Standard -Note that the style page won't print the page number if the label is on - the previous, the same, or the next page. +Note that the style +\change_inserted 0 1271691416 + +\begin_inset Quotes eld +\end_inset + +on page +\change_unchanged +page +\change_inserted 0 1271691060 + +\begin_inset Quotes erd +\end_inset + + +\change_unchanged + won't print the page number if the label is on the previous, the same, + or the next page. You will e. \begin_inset space \thinspace{} \end_inset @@ -24468,6 +24484,19 @@ \end_inset instead. + +\change_inserted 0 1271752702 + Style +\begin_inset Quotes eld +\end_inset + +reference on page page +\begin_inset Quotes erd +\end_inset + + won't print anything if the label if on the same page. +\change_unchanged + \end_layout \begin_layout Standard @@ -24564,8 +24593,339 @@ Embedded Objects \emph default manual. +\change_inserted 0 1271693304 + \end_layout +\begin_layout Standard + +\change_inserted 0 1271693498 + +\series bold +prettyref +\series default + does not know currently all the possible label shortcuts, you may extend + to other shortcuts than +\family typewriter +eq +\family default +, +\family typewriter +lem +\family default +, +\family typewriter +thm +\family default +, +\family typewriter +cha +\family default +, +\family typewriter +sec +\family default +, +\family typewriter +tab +\family default +, and +\family typewriter +fig +\family default + by adding to the preamble e.g.: +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694162 + +\backslash +newrefformat{cor}{Corollary +\backslash +ref{#1}} +\end_layout + +\begin_layout Paragraph + +\change_inserted 0 1271694428 +Note for non-English documents: +\end_layout + +\begin_layout Standard + +\change_inserted 0 1271694166 +using babel languages which make the period character active (like French) + creates an error with styles +\begin_inset Quotes eld +\end_inset + +on +\begin_inset space ~ +\end_inset + +page +\begin_inset space ~ +\end_inset + +page +\begin_inset Quotes erd +\end_inset + + and +\begin_inset Quotes eld +\end_inset + +reference +\begin_inset space ~ +\end_inset + +on +\begin_inset space ~ +\end_inset + +page +\begin_inset space ~ +\end_inset + +page +\begin_inset Quotes erd +\end_inset + +, and with style +\begin_inset Quotes eld +\end_inset + +Formatted +\begin_inset space ~ +\end_inset + +reference +\begin_inset Quotes erd +\end_inset + +. + +\end_layout + +\begin_layout Itemize + +\change_inserted 0 1271694166 +In the latter case, you can embed each reference in two ERT boxes like this: + +\end_layout + +\begin_deeper +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\series bold +{ +\backslash +shorthandoff{:} +\series default +Formatted +\begin_inset space ~ +\end_inset + +reference +\series bold +} +\end_layout + +\begin_layout Standard + +\change_inserted 0 1271694166 +Moreover, as +\series bold +prettyref +\series default + is not internationalized, you will have to redefine the +\backslash + +\family typewriter +newformat +\family default + commands in the preamble: +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{eq}{ +\backslash +textup{( +\backslash +ref{#1})}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{lem}{Lemma +\backslash +ref{#1}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{thm}{Theorem +\backslash +ref{#1}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{cha}{Chapter +\backslash +ref{#1}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{sec}{Section +\backslash +ref{#1}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{tab}{Table +\backslash +ref{#1} on page +\backslash +pageref{#1}} +\end_layout + +\begin_layout LyX-Code + +\change_inserted 0 1271694166 + +\backslash +newrefformat{fig}{Figure +\backslash +ref{#1} on page +\backslash +pageref{#1}} +\end_layout + +\begin_layout Standard + +\change_inserted 0 1271694166 +by the adequate string
Interface in trunk
Hello, IMHO, the sentence The document class requested\n \t%1$s\n requires ... (line 535 in src/BufferParams.cpp) should read better The document class selected\n \t%1$s\n requires ... Regards -- Jean-Pierre
Checksums and signing
Hello, I just translated in French this new section of http://www.lyx.org/Download and I had a try with this new procedure. I'm new to gpg, so where do I find te keyserver ? Should not this information be added to the paragraph ? Btw, the named link pointed to in section 1 is toc11, not toc7. -- Jean-Pierre
Plain layout
Hello, While reviewing French docs for 1.6.7 release, I noticed that all the menu markups have changed: they appear inside 4 small markers, and the corresponding style reads Plain layout (greyed out) as shown on the attached image. The corresponding LyX code reads: cite \begin_inset Flex CharStyle:MenuItem status collapsed \begin_layout Plain Layout File\SpecialChar \menuseparator Print \end_layout \end_inset /cite In the French docs, the same piece of code reads: cite \family sans Fichier\SpecialChar \menuseparator Imprimer /cite I understand that a MenuItem character style has been used in the English docs. I guess it must be possible to filter the French docs to substitute the character style to the former simple text font change, but is it worth to do so? -- Jean-Pierre inline: markup.png
Re: Plain layout
Uwe Stöhr a écrit : Am 05.07.2010 16:18, schrieb Jean-Pierre Chrétien: I understand that a MenuItem character style has been used in the English docs. I guess it must be possible to filter the French docs to substitute the character style to the former simple text font change, but is it worth to do so? Why do you want to remove the character styles? They work the same way in all languages. Sure, but currently the font changes are not implemented by character styles in the French Extended manual. It's quite a lot of work to change manually each occurrence, and I wonder if a filtering of the LyX file is ever possible, when I consider the LyX markup for plain font change. -- Jean-Pierre
Re: Plain layout
Uwe Stöhr a écrit : Am 07.07.2010 08:18, schrieb Jean-Pierre Chrétien: I don't have an idea how to do this. But its no problem if you omit the character styles in the French manual - I also omit them in the German ones. OK. However I activated the LogicalMarkup module to be able to copy/paste from the English manual in the French one without red patches emphasizing unrecognized layouts. As MenuItem is not part of the module, I had to patch this \begin_local_layout Format 7 InsetLayout CharStyle:MenuItem LyxType charstyle LabelString menu LatexType command LatexName menuitem Font Family Sans EndFont Preamble \newcommand*{\menuitem}[1]{{\sffamily #1}} EndPreamble End \end_local_layout into the .lyx file. Is there a way to ad this local_layout inset from the LyX interface ? Otherwise it would be good to add MenuItem to the LogicalMarkup module (maybe called SansSerif ?) -- Jean-Pierre
lyx help translation
Hello, The following sentence appears in the command line help of LyX: Anything else is equivalent to `all', but is not consumed Sorry, I don't understand what 'is not consumed' means. Is it 'is not executed' ? -- Jean-Pierre
Re: lyx help translation
Jürgen Spitzmüller a écrit : I would translate it as: it is silently skipped, and the program performs as if all was issued as an argument. Understood, thanks. However I've mentioned this before, but lyx-2.0.0svn -help does not display the translated strings in a French locale on Debian Lenny. So my translation is anyway useless :-( Shoud I file a ticket about this ? I found none currently. -- Jean-Pierre
Re: lyx help translation
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: Shoud I file a ticket about this ? I found none currently. Yes, please. Bug #6842 -- Jean-Pierre
Re: Beginner Question
Jordan Tousignant a écrit : I'm trying to follow the tutorial, but I can't find the example_raw.lyx file to do the exercises. Where is it? File-Open (Alt+F O the shortcuts way) then click on the Examples button in the upper right corner and browse the directory. -- Jean-Pierre
Re: Layout for a letter (in French)
Uwe Stöhr uwestoehr at web.de writes: Jean-Pierre Chrétien schrieb: - you used the LaTeX class lettre for your layout file. What about the other letter document classes LyX already supports? [...] Yes, these letter layouts do not follow the French presentation of letters. I guess this is the reason why there are several German alternatives to the letter layout. OK, then we'll use your layout file when the mentioned issues are fixed/reviewed. I've finally reviewed, simplified and updated the lettre.layout file and the modelettre.lyx template which implement (almost) completely the class lettre.cls, hopefully for inclusion in LyX-1.6.8. The styles are in English, I tried to minimize the number of new strings to be translated, but there are some. I recreated the pot file after svn up, merged with the current fr.po and updated it (I don't know if the pot creation file should be done directely on svn, and the update of po file should be made after svn up). I'm going to send the three files via po-updates. -- Jean-Pierre
Re: Layout for a letter (in French)
Liviu Andronic a écrit : What about frletter? It is based on 'letter' and loosely follows French conventions. IMHO, the lettre class is more powerful, and I've been using the layout and the template for a long time with full success. The layout is on the wiki, but was also recently included in branch and trunk. I've seen this, yes. I rather worked on the French docs since Uwe's requirement to update and simplify the lettre.layout, so it is ready just right now. -- Jean-Pierre
Message in en.po
Hello, Is seems to me that message: Adds environments to define header and footer lines NOTE: To use this mudule you must set the Headings style in the menu Document Settings - Page Layout to fancy! should rather read: Adds environments to define header and footer lines. NOTE: To use this module you must set the Headings style in the menu Document - Settings - Page Layout to fancy! -- Jean-Pierre
Re: Please prepare for LyX 1.6.8
Szõke Sándor - Alex a écrit : PS.: Good news from me: At 26.10.2010. a nice girl born onto Earth. She called Greta. She is my first daughter, and requires all the time we have (and even more). She is hungry, and unfortunately she doesn't like to sleep, therefore she cries a lot. Some pictures are available at http://szokesandor.hu in the Gallery section (20101026_sello_szuletes [mermaid born], 20101029_greta_hazajon [Greta comes home], 20101030_greta_otthon_2nap [2nd day at home]). Congratulations, and a long and happy life for Greta. -- Jean-Pierre
Re: beamer.layout
Jürgen Spitzmüller a écrit : Maybe it would be a good idea to add these *Margin strings to gettext? Adapting it to French is probably not the right solution for other languages. They are already, and translated in the po files, that's why in French (and maybe other languages) the string Colonnes (alignées sur première ligne) (translation of Columns (top aligned)) gets truncated in the LyX window if the label is static. -- Jean-Pierre
Re: beamer.layout
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: But does the Dynamic option for margin have a drawback ? Otherwise it works fine. I don't think so. But it's not something I'd like to change two days prior to the relase. Purely cosmetic, it can wait 1.6.9 of course. Maybe it can go in trunk also. -- Jean-Pierre
Re: English version of the Customization manual
Pavel Sanda a écrit : Jean-Pierre, your free.fr is continuosly rejecting my mails, so CC-ing to lyx-doc. Sorry for this. What does the rejection message say, so that I can see what's wrong with my provider ? Uwe is not here, so i will try to speak in his name. work on 1.6 manuals has been finished (i seem to remember such messages in recent months). all work should be focused on 2.0 manuals, which can change of course. OK, I will see with the 2.0 manual, but I hope that the French 1.6 manuals can still be updated. -- Jean-Pierre
Web site download page
Hello, Seems to me that variable (:winaltinstallerurl: in that page is no longer used. Sould be removed I guess. -- Jean-Pierre
Re: Small typo in RC2 French
Pavel Sanda a écrit : Murat Yildizoglu wrote: I am translating the interface element names from French to signal the typo: In Preferences/Type/Word Completion, the title of the second block of preferences on the right tab must read En mode mathématique instead of En mode mathé*t*matique. Small detail, but visible default ;-) Will be corrected in the next releases. Thanks for the hint. -- Jean-Pierre
Re: Translations of Math environments in LyX output - last call for LyX 2.0
Pavel Sanda a écrit : Pavel Sanda wrote: Please go through all entries in the attached file for your language and ensure that they are correctly translated. Make any needed update in the .po files as usual. The lib/layouttranslations file will be regenerated automatically from the .po files before the final 2.0.0 release. note: we shrinked the list of lib/layouttranslations not to contain strings which are translated by babel, the current version can be found here: http://www.lyx.org/trac/browser/lyx-devel/trunk/lib/layouttranslations Hello Pavel, I don't unserstand what happened, a lot of strings which are not translated in frenchb.ldf have disappeared. Here are the strings present in frenchb.ldf and in the first version of layouttranslations: \def\listfigurename{Table des figures}% \def\listtablename{Liste des tableaux}% \def\figurename{{\scshape Figure}}% \def\tablename{{\scshape Table}}% \def\proofname{D\'emonstration}% Btw, there are some peculiarities that the mechanism is unable to manage, like the \scshape required by french typography. On the other side, I would have liked to correct the inconsistence in French babel about the translation of table: \def\listtablename{Liste des tableaux}% \def\tablename{{\scshape Table}}% (\def\tablename{{\scshape Tableau}} would be better IMHO), so I would have preferred LyX to overwrite babel defaults to make them consistent with the French terms used in LyX. -- Jean-Pierre
Re: Translations of Math environments in LyX output - last call for LyX 2.0
Pavel Sanda a écrit : Julien Rioux wrote: Actually, I think we should, eventually :) why not fix it in french babel if its wrong? I had an exchange about this issue with Daniel Flipo, the maintainer of French babel. I asked him about the inconsitency, and more generally about the translation of 'table' in French. This is a bit complex, because there are two different translations - 'table' and 'tableau' which have not exactly the same meaning, table is more informal (one would not say e.g. 'tableau de matières' for toc), but in most situations where a table is a presentation of numerical results, the word 'tableau' is more appropriate. He agreed with me about the inconsistency between 'Liste des tableaux' and 'table' for each individual caption, but was reluctant to change it mainly because of the changes in old docs (overfull hboxes or more serious changes in the layout). However he changed the captions some time ago from Fig. and Tab. to Figure and Tableau, so he may be convinced. He suggested to raise the question on fr.comp.text.tex, but I declined the proposal because I guess I will end wity 50/50 rating between table and tableau, not to speak of possible flame wars. Anyway, even in the present situation, the correct instructions to change the captions and more generally the layouttranslations strings should be provided in the LyX doc, in the line of the recent answer I made to an user on the lyx-fr list (sorry, this is in French): http://www.mail-archive.com/lyx-fr@lists.lyx.org/msg01842.html To conclude, currently LyX knows 'tableau' as the standard homogeneous translation for the table environment in the GUI, that's why I think it would be more correct to provide an homogeneous translation in the LaTeX output, with accompanying appropriate explanations (in the French version). -- Jean-Pierre
Userguide
Hello, While reviewing the French version of the UserGuide for branch, I added section A.7.4 about the Check TeX program, the line appears with my installation. This section does not appear in the original English manual, nor in the 2.0 version of the manual. -- Jean-Pierre
Re: Site translations
Diego Queiroz a écrit : I realized right now that French and Japanese versions of the site have copies of the download links variables in the source code. As state in SiteDocumentation, the download links should be centralized in the English download page. So those variables aren't necessary. I removed them from the Portuguese (the one I am currently translating) and the French version (because it was already updated). On the place of the variables I included the following comment: (:comment Please update the variables on the ENGLISH download page! See Web.SiteDocumentation#DownloadLinksDocumentation for instructions :) And included the following in the English page: (:comment If you are using this page as a template for a new translation, DO NOT COPY these variables. Skip them and go to TOC. :) I think this will prevent future misunderstandings. Thanks a lot for performing this, Diego, I should have noticed the {Web.Download$:} tags in the page code. -- Jean-Pierre
enumitem.lyx
Hello, There are two items in German in this example file. Are they intended to be so? -- Jean-Pierre
Fwd: Additional manual
Hello, While revewing the French translation of this manual, I found a few items which need correction IMHO: section 5.6.1: rather Document--Settings-Output-Synchronize with Output than Document-Output-Synchronize with Output section 7.1.3: sentence Another choice in the most desperate situations is to use View-Remove All Error Boxes, which will get rid of all warnings instantly. seems obsolete, as I do not find this item menu anymore (nor in fr.po as well). section 7.2.1: sentence Before you begin to use the version control features in LyX, you should be familiar with RCS/CVS/SVN usage before start using it under LyX. is redundant. -- Jean-Pierre
Re: Translation of shortcuts descriptions via Lyx info insets
Le 25/08/2011 21:16, Uwe Stöhr a écrit : Am 22.08.2011 11:03, schrieb Jean-Pierre Chrétien: You can see that Return is translated as Entrée (which is the word written on French Keyboards), but I can't edit the Alt+Return sequence as it comes from a lyx info reference. This is a known limitation of InsetInfo that it cannot be set into the language of the document. Just 3 weeks ago we discussed this on the lyx-devel list again and hopefully tzhis will be fixed soon. OK, I've parsed the Initial experience with LyX thread, and if I understand correctly, I should rather leave the Insetinfo insets as they are rather than replace them by a plain translation, this will be corrected ('soon' seems optimistic, ticket #5348 has no milestone set). I have however further questions: - is the InsetInfo stuff documented in some place? - how could I create one from scratch in a fresh doc? - does the mecanism extends (or will extend) to other stuff than shortcuts, as e.g. menu items like DocumentSettings? - if I open ToolsPreferencesEditingShortcuts in French, and search for 'break-paragraph' shortcuts, I find that 'Return' is translated as 'Retour'. This is bad because it is translated by 'Entrée', which is better IMHO, in the docs. Where are these strings translated? I can't find anything in the po files, nor in the whole tree of the LyX sources. -- Jean-Pierre
Current values of lyx versions in I18n web page
Hello, I read this in http://www.lyx.org/I18n quote The following table details the current state of the translations of the LyX GUI for the LyX stable branch (version 2.1.0svn), which will become the next maintenance release. /quote Further investigation shows that variables in the page point to wrong values: (:LyX_i18n_version:) - 2.1.0svn (:LyX_i18n_trunk_version:) - 2.0.0svn The attached patch hopefully corrects this (I set the branch maintenance number to 2.0.2svn, maybe a bit early). -- Jean-Pierre --- farm/cookbook/LyX/i18n.inc.orig 2011-09-01 08:49:26.0 +0200 +++ farm/cookbook/LyX/i18n.inc 2011-09-01 08:50:41.0 +0200 @@ -1,6 +1,6 @@ ?php // The current version -$lyx_version = 2.1.0svn; +$lyx_version = 2.0.2svn; // The branch tag $branch_tag = branches/BRANCH_2_0_X; --- farm/cookbook/LyX/i18n_trunk.inc.orig 2011-09-01 08:49:44.0 +0200 +++ farm/cookbook/LyX/i18n_trunk.inc 2011-09-01 08:54:06.0 +0200 @@ -1,7 +1,7 @@ ?php // The current version -$lyx_version = 2.0.0svn; -// The branch tag +$lyx_version = 2.1.0svn; +// The trunk tag $branch_tag = trunk; // The data itself
Re: Current values of lyx versions in I18n web page
Le 01/09/2011 14:27, Uwe Stöhr a écrit : Am 01.09.2011 08:57, schrieb Jean-Pierre Chrétien: I read this in http://www.lyx.org/I18n Further investigation shows that variables in the page point to wrong values: Thanks, I've put this in. I several times informed Richard heck (the 2.0.x release maintainer) about this, but with every update he switched back to the wrong version numbering. I guess there is a bug in his update script. Should I edit the wiki page about release procedures of maintenance versions to add 'Update next lyx maintenance version number in i18n.inc' in the www-user section ? Another question: What is your time frame to update the French documentation? There is more work to do to be up to date for LyX 2.0.x but before I can start with the final step, I need your translations. The Math and EmbeddedObjects manual are already finished, so you only need to translate them - which is not urgent. For the UserGuide I need to do some more update work. I therefore need your translation updates soon. If you don't have time for this right now, pleas send me what you have. I will then go on and inform you when I'm ready with the UserGuide. Currently, following your last mail about it, I restored the 2.0.0 preamble and I am at the same time merging my last updates for 1.6 and your new updates, translating them or not depending if thet are full paragraphs or more local edits. I can speedup things by just merging your edits without translations to be able to handle you shortly a UserGuide.lyx file than you can edit again. I will come back to translations once you are OK with your changes. What would be your deadline to begin editing the manual again? -- Jean-Pierre
Re: powerdot-example.lyx fails to compile with TL 2011/MikTeX 2.9
Le 05/10/2011 21:12, Uwe Stöhr a écrit : Am 05.10.2011 15:48, schrieb Jean-Pierre Chrétien: Currently I have some spare time and would go on with the English version. But to avoid conflicts, I would be happy if you could send me what you have when you finished section 6.7. Then I can go on and will only change Appendix C and the sections below 6.8. OK? Please go on editing the English version and plugging changes in the French version of UserGuide.lyx in Trac: my current updated document is a merge between the 1.6 version with 2.0 preamble, your updated French version and the up-to-date Englidh version with is the real reference that I check carefully for changes anyway. If you restrat with my current version, I will be more lost than working on it until is is fully updated. I have a fez suggestions about the English version: 1/ by the end of section 3.3.6: is the page break still appropriate ? 2/ section 3.3.7.4: index entry should read Lists!Custom instead of Lists!Description 3/ section 3.8.2.2: menu item should read File-Export-LaT{}eX (standard) instead of File-Export-LaT{}eX 4/ section 6.1, definition of a formatted reference: I would add a word about prettyref deprecation in the note, like: ..prettyref or refstyle. The prettyref package is deprecated by LyX, which selects refstyle as default for any new document. I would add as well an example of a formatted reference. Here is an example of a formatted reference: sec:Citation. 5/ section 6.1, definition of a textual reference: make it more precise, e.g. prints the content of the caption or the name of the reference, e.g. the heading of a section instead of prints the caption or name of the reference -- Jean-Pierre
Re: powerdot-example.lyx fails to compile with TL 2011/MikTeX 2.9
Le 09/10/2011 06:33, Uwe Stöhr a écrit : Am 07.10.2011 16:17, schrieb Jean-Pierre Chrétien: But this is not the case. The default setting is still to use prettyref. refstyle is only used if you explicitly set its option in the document settings. Just open a fresh document and look at DocumentSettingsDocument class. And take a look at the prettyref code, I don't understand how Kevin Ruland can claim copyright for such a small piece of creativity, which has no provision for multinlingual application and in addition is hopelessly broken in French babel. As a result, users have developed a lot of document specific command definitions, which prevented LyX developers to simply remove support for it from the LyX distribution (see the threads about this last year). Have I mentioned the ridiculous public domain release, clearly just added to avoid being thrown away by TL maintainers ? -- Jean-Pierre
Consistency of strrings in theroems modules
Hello, While updating fr.po for 2.0.2, I see that the Conjecture \\theconjecture and such strings in theorems-without-preamble.inc are not consistent with similar strings in other theorems modules (there is no final dot). I know that this can't be solved before 2.0.2 because of the freeze, but it adds unnecessary lines in the po files, unless there is a strong reason to do so. -- Jean-Pierre
Re: Local Layouts - Additional Features manual?
Le 12/01/2012 08:07, Andrew Parsloe a écrit : Dear LyX documenters, I recently needed to turn a big LyX document into a number of Word documents (one for each chapter). Because the export to OpenOffice format no longer worked on my system (I can't find oolatex in a new install of MiKTeX 2.9), and time was short, I resorted to pasting from the pdf to Word. Up to my own experience, I found latex2rtf http://latex2rtf.sourceforge.net/ to be the best solution to turn à LyX document into office stuff (open the result in Word, not in OpenOffice). Math constructs are correctly translated (but alas cannot be edited, but for simple ones). -- Jean-Pierre
Re: lyx-docs@lists.lyx.org
Le 19/01/2012 10:25, elloh van a écrit : Dear Sir/Madam, I would like to know if provisions are made in LyX to make range citations as in the second and third citations in the file ''type-one-citation'' when your document is printed ? If yes, where can I find it in LyX ? If natbib fits your needs in citation style DocumentsSettingsBibliographyNatbibNatbib stylenumerical [#ID] in the citation menu and adding the keywords sortcompress to the class options in DocumentsSettingsDocument classOptions will do it. With biblatex, seems that the keywords style=numeric-comp in the class options do the trick. -- Jean-Pierre
Website translated pages flag pointers
Hello, While translating the last change in http://www.lyx.org/PressAboutLyX in the French corresponding page, I see that the French flag at the top of the page points on http://www.lyx.org/WebFr.PageActions instead of http://www.lyx.org/WebFr.PressAboutLyX This is not specific to French, nor to the requested page: other flags behave alike in every page of the website. The language selector (leftmost button) works however all right. -- Jean-Pierre
Listing of English pages in the website translation page
Hello, A new HowToUseGIT page has been added to the set of website page. It would be good to reflect this change (and maybe others ?) in the English root page. It would be nice also to remove pages which do not need translation any more. TIA -- Jean-Pierre
Re: Listing of English pages in the website translation page
Le 03/07/2012 13:37, Pavel Sanda a écrit : Jean-Pierre Chrétien wrote: A new HowToUseGIT page has been added to the set of website page. It would be good to reflect this change (and maybe others ?) in the English root page. Where do you mean? I changed the link in http://www.lyx.org/Development. Sorry, my mail was unclear without the URL of the page: http://www.lyx.org/SiteTranslation It would be nice also to remove pages which do not need translation any more. Which ones? At the time of my initial translation, I did not translate * AboutLyXMod * DeveloperResources * DevelopmentNews * HomeNewGraphic * OldIntro * PressReleaseLyX1-0-0 Was that correct ? -- Jean-Pierre
Re: URGENT help with LYX
Le 20/08/2012 12:24, Sydney Jason a écrit : Hello, I have just completed my thesis and about to print it for submission and just discovered that Lyx is printing funny character for my table of content List of figure, List of table Can some one please help me, my submission is few days time. I attached the screenshot of the error. this is the only problem . What is your question exactly ? The page numebering (as John seems to have understood) or the fact that some parts are in English and others in Dutch ? Jean-Pierre
How to mirror LyX sites Web page
Hello, Following the recent updates of this page, I think that this sentence in section 2 : (I think I want to require this for national lyx mirrors.) is outdated. -- Jean-Pierre
Re: Issues with Tutorial Section 3.4 Labels and Cross-References
Le 30/11/2012 00:03, Eric Kenney a écrit : Hi! I'm using your tutorial, and so far I'm finding it pretty useful, except: Section 3.4, Labels and Cross-References. 1st off, you tell us to use a reference on page page cross reference. But you forget to tell us two things: 1, that this cross reference will simply omit on page page in the cross reference is on the same page as the label. And 2nd, in 3.4.2 you tell us to insert this into the sentence Section [Cross-Reference], which can be found on page. Like so. This yields, at best, ...Section 2 on page X, which can be found on page. As such, I've wasted an inappropriate amount of time on this section trying to figure out what I was doing wrong. You may want to fix it. Which LyX version are you using ? In the current version of the Tutorial, I read: cite View your document as DVI, and you will see that LaTeX has been even cleverer than that. It refers to “Section 2” and depending how much text you have between the start of Section 2 and this cross-reference you may see “on this page”, “on the previous page” or “on page n” (whereas n is the page number). /cite You are however right about the crossref procedure insertion, which should be changed to: cite If you want to know more about this document, then see Section. Now — with the cursor after the word “Section” — choose Insert-Cross Reference... /cite -- Jean-Pierre
Re: Issues with Tutorial Section 3.4 Labels and Cross-References
Le 30/11/2012 14:41, Jean-Pierre Chrétien a écrit : You are however right about the crossref procedure insertion, which should be changed to: cite If you want to know more about this document, then see Section. Now — with the cursor after the word “Section” — choose Insert-Cross Reference... /cite Rather with a space before the period (an unbreakable space in fact, as explained further in the section): cite If you want to know more about this document, then see Section . Now — with the cursor before the period after the word “Section” — choose Insert-Cross Reference... /cite with a space before the period (an unbreakable space in fact, as explained further in the section).
Re: Issues with Tutorial Section 3.4 Labels and Cross-References
Le 30/11/2012 15:51, Jean-Pierre Chrétien a écrit : Le 30/11/2012 14:41, Jean-Pierre Chrétien a écrit : cite If you want to know more about this document, then see Section . Now — with the cursor before the period after the word “Section” — choose Insert-Cross Reference... /cite with a space before the period (an unbreakable space in fact, as explained further in the section). oups, sorry, forget the last sentence. Jean-Pierre
Re: Faute de frappe dans Introduction à LyX
Le 02/02/2013 20:47, Haller Roland a écrit : Bonjour, Je me permet de vous signaler l'absence de esse dans la phrase : Extension du Guide de L’Utilisateur, il explique en détail comment utiliser les tableaux, les graphiques, les objets flottants, les notes et _le _boîtes. Page 9, section 2.3, paragraphe Objets insérés. C'est corrigé, merci de l'avoir signalé. Notez bien que la liste lyx-docs est anglophone, il existe une liste francophone : lyx...@lists.lyx.org -- Jean-Pierre
Typo in UserGuide
Hello, In section 5.2 of the UserGuide, the following sentence: cite For example, that is how you would construct the brackets around a matrix: formula and to make it easier to see the layers of parentheses. /cite does not seem very clear to me. Should not it read : to make it easier to see the layers of parentheses. (i.e. withoud and) ? -- Jean-Pierre
Typo
Hello, While updating fr.po for master, I found the word spezification several times in in powerdot.layout. -- Jean-Pierre --- lib/layouts/powerdot.layout.orig 2013-05-28 13:38:28.0 +0200 +++ lib/layouts/powerdot.layout 2013-05-28 13:39:16.0 +0200 @@ -267,7 +267,7 @@ LabelType Itemize Argument 1 LabelString Itemize Type -Tooltip Itemize type spezification (see powerdot manual) +Tooltip Itemize type sepcification (see powerdot manual) EndArgument Argument 2 LabelString Itemize Options @@ -290,7 +290,7 @@ CopyStyle Itemize Argument 1 LabelString Itemize Type -Tooltip Itemize type spezification (see powerdot manual) +Tooltip Itemize type sepcification (see powerdot manual) DefaultArgtype=1 EndArgument End @@ -317,7 +317,7 @@ RefPrefix enu Argument 1 LabelString Enumerate Type -Tooltip Enumerate type spezification (see powerdot manual) +Tooltip Enumerate type sepcification (see powerdot manual) EndArgument Argument 2 LabelString Enumerate Options @@ -340,7 +340,7 @@ CopyStyle Enumerate Argument 1 LabelString Enumerate Type -Tooltip Enumerate type spezification (see powerdot manual) +Tooltip Enumerate type sepcification (see powerdot manual) DefaultArgtype=1 EndArgument End
Re: Typo
On 28/05/2013 14:48, Siegfried Meunier-Guttin-Cluzel wrote: Hello, Sorry, I don't understand sepcification ... I think it's specification ?? Sure, thanks for pointing it out, attached is a correct diff. -- Jean-Pierre --- lib/layouts/powerdot.layout.orig 2013-05-28 13:38:28.0 +0200 +++ lib/layouts/powerdot.layout 2013-05-28 14:56:13.0 +0200 @@ -267,7 +267,7 @@ LabelType Itemize Argument 1 LabelString Itemize Type -Tooltip Itemize type spezification (see powerdot manual) +Tooltip Itemize type specification (see powerdot manual) EndArgument Argument 2 LabelString Itemize Options @@ -290,7 +290,7 @@ CopyStyle Itemize Argument 1 LabelString Itemize Type -Tooltip Itemize type spezification (see powerdot manual) +Tooltip Itemize type specification (see powerdot manual) DefaultArgtype=1 EndArgument End @@ -317,7 +317,7 @@ RefPrefix enu Argument 1 LabelString Enumerate Type -Tooltip Enumerate type spezification (see powerdot manual) +Tooltip Enumerate type specification (see powerdot manual) EndArgument Argument 2 LabelString Enumerate Options @@ -340,7 +340,7 @@ CopyStyle Enumerate Argument 1 LabelString Enumerate Type -Tooltip Enumerate type spezification (see powerdot manual) +Tooltip Enumerate type specification (see powerdot manual) DefaultArgtype=1 EndArgument End
Re: Remarques sur l'intro à LyX
Le 15/09/2013 14:53, Etienne Candel a écrit : Bonjour, A plusieurs reprises, l'introduction utilise des ... après un etc., or c'est une faute typographique (certes répandue). Je réponds en anglais car cette liste est anglophone, la liste francophone est lyx...@lists.lyx.org Typos corrected in the attached patches both for branch and master versions of Intro.lyx. I also corrected the link to www.lyx.org/Translation to point towards the French version WebFr.Translation. -- Jean-Pierre --- lib/doc/fr/Intro.lyx.orig 2013-09-15 16:32:09.0 +0200 +++ lib/doc/fr/Intro.lyx 2013-09-15 16:36:51.0 +0200 @@ -196,11 +196,11 @@ LyX est un système de préparation de documents. Il est excellent si vous voulez écrire des articles scientifiques et techniques complexes avec des mathématiques, des références croisées, des bibliographies, - des index, etc\SpecialChar \ldots{} - Il est très bon pour tous les documents de toutes tailles - pour lesquels sont requises les fonctions habituelles d'un traitement de - texte: numérotation des sections et pagination automatiques, correction - orthographique, et ainsi de suite. + des index, etc. + Il est très bon pour tous les documents de toutes tailles pour lesquels + sont requises les fonctions habituelles d'un traitement de texte: numérotation + des sections et pagination automatiques, correction orthographique, et + ainsi de suite. Il peut aussi servir à écrire une lettre à votre maman, même si je vous accorde qu'il existe sans doute des programmes plus simples pour ça. Il n'est certainement pas le meilleur outil pour créer des affiches, tracts @@ -510,9 +510,8 @@ voulez \emph default définir exactement où va chaque chose, parce qu'il n'y a pas d'unités fonctionn -elles comme des paragraphes, des sections, etc\SpecialChar \ldots{} - Ãa ne veut pas dire qu'il - manque à LyX des fonctions utiles. +elles comme des paragraphes, des sections, etc. + Ãa ne veut pas dire qu'il manque à LyX des fonctions utiles. Ãa signifie simplement que ce n'est pas l'outil adapté â vous n'utilisez pas un tournevis pour enfoncer des clous (sauf si votre tournevis est garanti à vie). @@ -581,8 +580,7 @@ \end_layout \begin_layout Itemize -interligne (simple, double, etc\SpecialChar \ldots{} -); +interligne (simple, double, etc.); \end_layout \begin_layout Itemize @@ -594,8 +592,7 @@ \end_layout \begin_layout Itemize -types de caractère (gras, italique, souligné, etc\SpecialChar \ldots{} -). +types de caractère (gras, italique, souligné, etc.). \end_layout \begin_layout Standard @@ -795,8 +792,7 @@ \family typewriter dvi \family default -, ou le convertir vers d'autres formats comme PostScript, PDF, etc\SpecialChar \ldots{} - +, ou le convertir vers d'autres formats comme PostScript, PDF, etc. \end_layout \begin_layout Standard @@ -2685,7 +2681,7 @@ \begin_layout Standard D'autre part il faut prendre garde à ne modifier que la dernière version de la traduction. - C'est toujours celle qui est sur le serveur SVN + C'est toujours celle qui est sur le serveur Trac \lang english \begin_inset Flex URL @@ -2708,7 +2704,7 @@ \begin_layout Plain Layout -http://www.devel.lyx.org/ +http://www.lyx.org/WebFr.Translation \end_layout \end_inset --- lib/doc/fr/Intro.lyx.orig 2013-09-15 16:27:50.0 +0200 +++ lib/doc/fr/Intro.lyx 2013-09-15 16:36:21.0 +0200 @@ -196,11 +196,11 @@ LyX est un système de préparation de documents. Il est excellent si vous voulez écrire des articles scientifiques et techniques complexes avec des mathématiques, des références croisées, des bibliographies, - des index, etc\SpecialChar \ldots{} - Il est très bon pour tous les documents de toutes tailles - pour lesquels sont requises les fonctions habituelles d'un traitement de - texte: numérotation des sections et pagination automatiques, correction - orthographique, et ainsi de suite. + des index, etc. + Il est très bon pour tous les documents de toutes tailles pour lesquels + sont requises les fonctions habituelles d'un traitement de texte: numérotation + des sections et pagination automatiques, correction orthographique, et + ainsi de suite. Il peut aussi servir à écrire une lettre à votre maman, même si je vous accorde qu'il existe sans doute des programmes plus simples pour ça. Il n'est certainement pas le meilleur outil pour créer des affiches, tracts @@ -510,9 +510,8 @@ voulez \emph default définir exactement où va chaque chose, parce qu'il n'y a pas d'unités fonctionn -elles comme des paragraphes, des sections, etc\SpecialChar \ldots{} - Ãa ne veut pas dire qu'il - manque à LyX des fonctions utiles. +elles comme des paragraphes, des sections, etc. + Ãa ne veut pas dire qu'il manque à LyX des fonctions utiles. Ãa signifie simplement que ce n'est pas l'outil adapté â vous n'utilisez pas un tournevis pour enfoncer des clous (sauf si votre tournevis est garanti
Typos in Customization.lyx
Hello, While updating Customization.lyx for French, I found these : Section 3.2, second paragraph, sentence : The definitions of the copiers may use four variables: should read: The definitions of the copiers may use eight variables: In footnote #2, section 4.1.1, a translator (Adrien or Siegfried, I guess, I didn't add added it myself) a warning about Emacs edition of po files, as Emacs does not know (up to my knowledge) to handle files encoded in Unicode, something like Emacs contains a `mode' for editing po files, as well, but beware, po files are Unicode-encoded. In section 4.1.2; the doc suggests to make a copy of the document, it's OK for simple docs, but it won't be good for complex docs with images, file paths will be broken when the document will be submitted. It's much better to retrieve the LyX tree from git and to edit directly the doc in place. Section 4.1bis, International Keyboard Support: what is the status of this section in an outdated branch? Section 5.1, enum 3a: the TeXLive path should be indicated, I added in the French doc /usr/local/texlive/texmf-local, (and as well /usr/share/texmf as it appears when installed by my Debian). In the same line, I added ~/.texlive for the location of TEXMFHOME. Section 5.1, enum 3b: I don't use Windows, but shouldn't the path be documented for Windows 7 and Windows 8 if they have changed ? Section 5.3.3: the current format number is 48. Section 5.3.6: the last line of Argument item should end by a period. in the ForceLocal doc, in the second sentence, 'argment' should read 'argument'; the 'If' after the colon should be 'if'. in the Bib_Environment doc, adds additionnaly is a pleonasm; a period is missing after \begin{thebibliography}{99}. Section 5.3.7: last sentence, the example should read '(e.g. 2.0.x to 2.1.0)' instead of '(e.g. 2.0.x to 2.1.y)' IMHO, as it won't change after 2.1.0 until 2.2.0 Section 5.3.12: should not citemisc %author%, “%title”./cite read citemisc %author%, “%title%”./cite? Appendix B: legend for buttonbg should read Color used for button background -- Regards Jean-Pierre
Re: Typos in Customization.lyx
Le 23/01/2014 11:28, Jean-Marc Lasgouttes a écrit : Le 23/01/2014 10:19, Jean-Pierre Chrétien a écrit : In footnote #2, section 4.1.1, a translator (Adrien or Siegfried, I guess, I didn't add added it myself) a warning about Emacs edition of po files, as Emacs does not know (up to my knowledge) to handle files encoded in Unicode, something like Emacs contains a `mode' for editing po files, as well, but beware, po files are Unicode-encoded. According to http://www.gnu.org/software/gettext/manual/html_node/Installation.html#Installation the right thing to add in .emacs for recent emacsen is (autoload 'po-mode po-mode Major mode for translators to edit PO files t) (setq auto-mode-alist (cons '(\\.po\\'\\|\\.po\\. . po-mode) auto-mode-alist)) (autoload 'po-find-file-coding-system po-compat) (modify-coding-system-alist 'file \\.po\\'\\|\\.po\\. 'po-find-file-coding-system) You're right, emacs seems to handle Unicode all right. I was mistaken because I personnaly use xemacs, which does not. So you can forget my hint -- Jean-Pierre
Re: Translations of Math environments in LyX output for LyX 2.1
Le 10/04/2014 12:36, Vincent van Ravesteijn a écrit : On Wed, Apr 9, 2014 at 11:44 PM, Jean-Pierre Chrétien jeanpierre.chret...@free.fr wrote: Le 26/03/2014 21:40, Vincent van Ravesteijn a écrit : All languages need to be reviewed for the following strings: Property (except Finnish), Solution (except Finnish), Listing, Listings I can't see anything to change for French. I posted a request for comments on lyx-fr and got one reply from Julien who wanted some clarifications. The only problem I have is that 'Table' is translated in French as 'Tableau' so that the 'List of Tableaux' coming from Optimization theory will be ambiguous with the standard 'List of Tables' translation in the Toc if I translate both by 'Liste des tableaux'. The workaround I found with 2.0 was to translate in layouttranslations as 'Liste des tableaux (TO)' where TO stands for 'Théorie de l'Optimisation'. The strings in layouttranslations are special as they end up in the actual PDF document. So, adding TO looks a bit wrong to me, because the reader of the document won't understand. Any other idea ? No, not really. I guess the best thing to do is to just have the same translation. One refers to tables in LyX, the other one to the tables in the document. No, my point on this is that one has in the same document a regular 'List of Tables' and a OT layout 'List of Tableaux', if they are translated both as 'Liste des tableaux' (one is in babel file frenchb.ldf and on in layouttranslations), I will get two entries 'Liste des tableaux' in the Toc (these strings appear only ther, right ?). To discriminate, I added the TO tag. I could come back to 'Liste des tables' in layoutranslations to differ from babel, but as I choose to translate 'table' as 'tableaux' I though I should remain consistent. -- Jean-Pierre
Re: Translations of Math environments in LyX output for LyX 2.1
Le 11/04/2014 10:02, Vincent van Ravesteijn a écrit : I found two French texts on the subject: http://www.persee.fr/web/revues/home/prescript/article/lfr_0023-8368_2000_num_126_1_989?_Prescripts_Search_tabs1=standard; http://www.filecluster.fr/logiciel/OTableau-151858.html Maybe it is such a specialized field that the suffix (OT) is clear to everyone ? Or maybe you can translate it as tableau optimalité théorie. Vincent Well, I mean: Tableau - Tableau List of Tableaux - Liste des tableaux optimalité théorie I parsed the first French document that you pointed out. I would prefer thus Tableau - Tableau phonologique List of Tableaux - Liste des tableaux phonologiques Jürgen , what do you think? Would phonological be approprioate in English if an ambiguity was to be solved ? I will update the linguistics manual if you agree. Vincent, thanks a lot for finding this reference, I guess you have other things to worry about to-day... -- Jean-Pierre
Re: Text style menu entry
Le 10/05/2021 à 11:47, Jean-Pierre Chrétien a écrit : Hello After the review of the documentation to make clear the distinction between text properties and text styles, new subsection 3.5.7.1 refers to a non-existent "Text Style" menu entry. "Text properties" seems more appropriate, knowing the builtin styles can be found in the "Semantic Markup" column there. I intend to correct this, does it seem OK ? More precisely, I'm going to change use the Text Style dialog [...] as described in section [subsec:Fine-Tuning-with-the] to use the Text Properties dialog (Edit>Text Properties>Customize...) under 'Semantic Markup' The 'Fine Tuning' section deals with formal markup, not semantic markup. -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
Text style menu entry
Hello After the review of the documentation to make clear the distinction between text properties and text styles, new subsection 3.5.7.1 refers to a non-existent "Text Style" menu entry. "Text properties" seems more appropriate, knowing the builtin styles can be found in the "Semantic Markup" column there. I intend to correct this, does it seem OK ? -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
Missing item+ shortcut in UserGuide
Hello, At the beginning of section 2.1, "Save all" is missing in the description of the menu list for "File". And the keyboard shortcut with "New from template..." is replaced by "undefined". The reason is that Ctrl-Shift-N which pointed to buffer-new-template with 2.3, now points to the new "dialog-show lyxfiles templates". Substituting the info inset externally solves this issue (I do not know how to edit an info inset inside LyX). I will post an updated version later, I may find other typos while updating the French version of the manual. -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
Re: Text style menu entry
Le 10/05/2021 à 11:54, Jean-Pierre Chrétien a écrit : Le 10/05/2021 à 11:47, Jean-Pierre Chrétien a écrit : Hello After the review of the documentation to make clear the distinction between text properties and text styles, new subsection 3.5.7.1 refers to a non-existent "Text Style" menu entry. "Text properties" seems more appropriate, knowing the builtin styles can be found in the "Semantic Markup" column there. I intend to correct this, does it seem OK ? More precisely, I'm going to change use the Text Style dialog [...] as described in section [subsec:Fine-Tuning-with-the] to use the Text Properties dialog (Edit>Text Properties>Customize...) under 'Semantic Markup' The 'Fine Tuning' section deals with formal markup, not semantic markup. Hello, Finally I reviewed completely section 3.5.7 (sorry, I wrote section 3.7 in the git log): in addition to the editions above, I reorganized paragraphs to stick to the combo boxes of the Text Properties window (Font properties, Decoration, etc.) I had also to turn the inset info menu name Edit>Text Properties>Customize in static form: it appeared translated in French in the LyX window (which is intended I suppose for an InsetInfo tag), but also in the pdf export, which is not good at all. Comments welcome. -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
Typo in Customization manual ?
Hello In the Customization manual, should not (in the définition of TableStyle): Grid_with_Head: Like Simple_Grid, but with the header column offset with a second horizontal line. This is also the default style of LyX. read Grid_with_Head: Like Simple_Grid, but with the header row offset with a second horizontal line. This is also the default style of LyX. I can edit the manual if needed. -- Regards Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
What does Library mean?
Hello While translating the interface for master, I find the following string: Library directory What does library mean in the context? Does it refer to /usr/lib? I was unable to find the string in LyX. -- Jean-Pierre -- lyx-docs mailing list lyx-docs@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-docs
splash.lyx
Hello, Attached is a patch to correct a wrong pointer in splash.lyx (branch version), together with a corrected French version of the splash.lyx file. -- Jean-Pierre --- lib/examples/splashOrig.lyx 2015-02-12 09:47:44.0 +0100 +++ lib/examples/splash.lyx 2015-02-12 09:48:03.0 +0100 @@ -111,7 +111,7 @@ \begin_layout Enumerate The output from LyX looks great! Use the menu \family sans -View\SpecialChar \menuseparator +Document\SpecialChar \menuseparator View \begin_inset space ~ \end_inset splash.lyx Description: application/lyx
Re: Intro manual
Le 08/03/2015 11:41, Uwe Stöhr a écrit : I try to keep the docs in sync. Only new stuff will go to master. So indeed, I could have written to retrieve the docs from branch, but from which branch? The branch changes from release to release while the master is always the master. So I am a bit lazy to update the intro manual for every release ;-). As I wrote in a previous mail : Le 06/03/2015 10:41, Jean-Pierre Chrétien a écrit : Of course, a plain user who intends to improve the docs may not be aware of the status of the doc update for translators. so let's leave the Intro manual as it is, Uwe will manage the (I guess) few contributions which will be proposed. So no change needed to the Intro manual, you may have a good vacation I hope :-) -- Jean-Pierre
Warnings while exporting UserGuide to pdf
Hello, I get a couple of warnings in the log when I export the UserGuide to PDF: Class scrbook Warning: Usage of package `fancyhdr' together (scrbook) with a KOMA-Script class is not recommended. (scrbook) I'd suggest to use (scrbook) package `scrpage2' or `scrlayer-scrpage'. (scrbook) Nevertheless, using requested (scrbook) package `fancyhdr' on input line 133. Class scrbook Warning: Usage of deprecated font command `\bf'! (scrbook) You should note, that in 1994 font command `\bf' has (scrbook) been defined for compatiblitiy to Script 2.0 only. (scrbook) Now, after two decades of LaTeX2e and NFSS2, you (scrbook) shouldn't use such commands any longer and within (scrbook) KOMA-Script usage of `\bf' is definitely deprecated. (scrbook) See `fntguide.pdf' for more information about (scrbook) recommended font commands. (scrbook) Note also, that KOMA-Script will remove the definition (scrbook) of `\bf' anytime until release of about version 3.20. (scrbook) But for now, KOMA-Script will replace deprecated `\bf' (scrbook) by `\normalfont \bfseries ' on input line 1531. In addition I get this in the calling command window: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited These are hamless as the PDF is here all right, but... -- Jean-Pierre
splash.lyx
Forget my preceding mail, the emitter was not the right one. Message transféré Sujet : splash.lyx Date : Wed, 29 Jul 2015 16:18:14 +0200 De : Administrateur JdJ cont...@jardinsdejade.fr Répondre à : cont...@jardinsdejade.fr Pour : LyX Documentation Team lyx-docs@lists.lyx.org Hello, Please find attached two patches for splash.lyx in English and French, to edit the error about viewing the PDF result. -- Regards Jean-Pierre --- splashOrig.lyx 2015-02-12 09:47:44.0 +0100 +++ splash.lyx 2015-02-12 09:48:03.0 +0100 @@ -111,7 +111,7 @@ \begin_layout Enumerate The output from LyX looks great! Use the menu \family sans -View\SpecialChar \menuseparator +Document\SpecialChar \menuseparator View \begin_inset space ~ \end_inset --- splash.lyx~ 2014-11-19 14:06:06.0 +0100 +++ splash.lyx 2015-02-12 09:44:00.0 +0100 @@ -116,7 +116,7 @@ \begin_layout Enumerate Les résultats de mise en page de LyX sont très esthétiques! Faites \family sans -Affichage\SpecialChar \menuseparator +Document\SpecialChar \menuseparator Visionner \begin_inset space ~ \end_inset @@ -125,7 +125,7 @@ \begin_inset space ~ \end_inset -(pdflatex] +(pdflatex)] \family default ou cliquez maintenant sur le bouton \begin_inset Info
LyX Web site
Hello, I recently begun the translation of the site to French, and I have a suggestion: use instead of -- wherever it happens (currently I found some in http://www.lyx.org/WhatIsLyX ). Regards -- Jean-Pierre
Re: LyX Web site
Helge Hafting a écrit : Jean-Pierre Chrétien wrote: Hello, I recently begun the translation of the site to French, and I have a suggestion: use instead of -- wherever it happens (currently I found some in http://www.lyx.org/WhatIsLyX ). When you use "--" in LyX, an endash happens in the output, and "---" turns into emdash. This is why some LyX users use "--" now and then. Sure, I use it myself. But unless pmwiki provides a similar mechanism, as Jean-Marc suggested, HTML entities are required in the web site. -- Jean-Pierre
Re: To translators of the web site. SiteTranslation now a bit better
Christian Ridderström a écrit : Hi, I've fiddled (more than I expected, guess I'm rusty), and the page http://www.lyx.org/SiteTranslation now should show translated pages in _red_ if the corresponding english page has been edited more recently. In case the translated page has been edited more recently, it's shown in green. Well done, Christian, thanks. -- Jean-Pierre
Re: Offre d'aide
frederic.steve...@ac-amiens.fr a écrit : Bonjour, J'utilise LyX depuis quelques années, par intermittence. En retour, je peux vous proposer mes services, même si mes compétences ne sont pas bien grandes : >je ne programme pas, mais je peux traduire, par exemple, >corriger des documents en français (syntaxe, grammaire, typographie, vocabulaire). Si vous pensez que je puisse être d'une quelconque utilité, n'hésitez pas. Merci pour votre proposition, mais la langue d'usage de lyx-docs est l'anglais, il existe la liste lyx-fr spécifique au français: lyx-fr at lists.lyx.org So I will forward your mail on lyx-fr and answer there. Thanks and regards. -- Jean-Pierre
Web site translation: how to use SVN
Hello, While translating this page in French, these sentences This is the new development and stable branch. The development will progress in branches and the main trunk will stay stable. were unclear to me. I suggest This is the new development and stable branch. The development will progress in the main trunk and the stable successive versions can be found in "branches". The most recent branches/BRANCH_X_X_X directory is however still active to provide maintenance releases of the current stable version. -- Jean-Pierre
Braille example in French
Hello, Attached is a tentative Freanch version of the Braille example. I am not a specialist of Braille, but I feel that Braille support in LyX for French suffers from the limitations of Braille support in LaTeX for foreign languages (the Maj modifier is not the same in English Braille and in French Braille e.g.). In addition - active characters in French babel do not work in the Braille commands, I tried to add english encaspsulation to avoid LaTeX errors without success; - the French guillemets (set in Document->Settings->Language) do not work. About the latter, it seems that this is a recent regression in branch w.r.t 1.6.3. I thought first that it was due to the fact that the doc is Unicode in LaTeX, but it is true with a fresh article doc. Any ticket about this ? -- Jean-Pierre Braille.lyx Description: application/lyx
Re: Braille example in French
Uwe Stöhr a écrit : > Jean-Pierre Chrétien schrieb: [...] > The Braille package only supports English. For all language-specific characters you have to use the braillebox environment. > Can you please add a sentence that this is also the case for the French Maj modifier? Attached is an updated version. > >> In addition >> - active characters in French babel do not work in the Braille > > Same problem as above, Braille doesn't take care of language-specific things and thus also not of babel. Corrected in the preamble. Btw, why are the greyed notes in Braille style ? I loose the guillemets there when I fall back to english babel to avoid active chars. > >> - the French guillemets (set in Document->Settings->Language) do not work. > > Works fine there with today's branch build. Right, in fact svn up && make is not enough to refresh lyx, I will run the full update command in the future. Regards -- Jean-Pierre Braille.lyx Description: application/lyx
[Fwd: Delivery Status Notification (Failure)]
Hello, po-upda...@lyx.org seems to be down... Any clue ? -- Jean-Pierre Message original Sujet : Delivery Status Notification (Failure) Date : Mon, 28 Sep 2009 06:42:40 -0700 (PDT) De : Mail Delivery SubsystemPour : jeanpierre.chret...@free.fr This is an automatically generated Delivery Status Notification Delivery to the following recipient failed permanently: po-upda...@lyx.org - Original message - [...] To: po-upda...@lyx.org Subject: [Fwd: fr.po for branch] Content-Type: multipart/mixed; boundary="060902010508080605030603" This is a multi-part message in MIME format. --060902010508080605030603 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message original Sujet : fr.po for branch Date : Mon, 28 Sep 2009 15:36:37 +0200 - Message truncated -
French translation of the web site
Hello, The translation is quite complete and up to date, thanks to Siegfried and Alain: http://www.lyx.org/SiteTranslation#toc5 Is there a way to display the French pages if the browser is French-speaking ? -- Jean-Pierre
Re: French translation of the web site
Christian Ridderström a écrit : On Wed, 7 Oct 2009, Jean-Marc Lasgouttes wrote: Jean-Pierre Chrétien <jeanpierre.chret...@free.fr> writes: Is there a way to display the French pages if the browser is French-speaking ? I have proposed this in the past, but Christian was not sure he wanted it. I still think we should (at least for languages that are considered to be complete enough) By now I've forgotten any objections I might have had, so for me it's fine. Of course, I've also completely forgotten how this would be implemented... I'm rather busy so if either you do it, or I'm given some algorithm. AFAIR, needs directives on the server side. LyX pretends that the server name is none of my business :-( If it's Apache, language negotiation may be on by default: AddLanguage da .dk AddLanguage nl .nl AddLanguage en .en AddLanguage et .et AddLanguage fr .fr AddLanguage de .de AddLanguage he .he ... but the mechanism does not seem compatible with pmwiki, as it requires pages in different languages to have suffices like .fr, .de, etc. I guess that this was the problem that raised objections from you at the time. Forget about my suggestion. -- Jean-Pierre
Re: fr.po for branch + Intro.lyx
Jürgen Spitzmüller a écrit : However, your new version has the following diff: - Il y a aussi une site de référence pour les traductions en français, sur - laquelle vous pouvez télécharger les fichiers les plus récents + Il y a aussi une site de référence pour les traductions en français Should this go in? No, I simplified the phrase a bit (to account for the fact that the current version of the docs are now published on the wiki), but we may publish there prereleases of the lyx-2.0 docs, so you can leave it as it is. -- Jean-Pierre
Re: xypic.lyx in French update
Uwe Stöhr a écrit : One tip: When you need to use a multiplication sign like in "3x3" matrix, you can insert it via the menu Insert->Special Character->Symbols. I therefore replaced the formula with this sign in your file. I followed the chktex hints and typed in \times in Math. To use your tip, you must know which alphabet to parse: here I have Latin-1 supplement as default, and I had to display all characters and to parse them carefully to find out a x sign in Casseau. Is that the right one ? -- Jean-Pierre
powerdot-example
Hello, Please find attached a French translation of the powerdot-example file, named exemple-powerdot.lyx. I removed the \usepackage{listings} command in the premable, as I guess that it is no more needed since listings has been intefaced with LyX. I get some warnings in the command window, like: Counter section does not exist. step: Counter does not exist: subsection -- Jean-Pierre exemple-powerdot.lyx Description: application/lyx
Re: How to update fr.po in trunk
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: Is it correct to merge fr.po in trunk and fr.po in branch like this to backport my branch updates in trunk ? I usually do this manually, using Lokalize (the KDE 4 po editor), which provides nifty abilities to sync/merge two po files. You can select branch's fr.po as "secondary sync source", navigate through all messages that are different there and directly copy them to trunk's po file. I could do this with XEmacs po-mode, but I went to poedit when the po-files were converted to UTF-8. I run Debian stable, KDE-4 is not available so I can't use loKalize. I guess I will test the msgmerge path, seems efficient as it found 53-17 = 36 messages in branch that came translated in trunk (these come from string changes committed both in branch and in trunk). I guess also that most of the 257-143=114 new fuzzies come from the branch file unification steps. -- Jean-Pierre
Re: powerdot-example
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: I doubt so. Are you sure you're really using that file? Sorry, I think I get confused between the two versions of exemple-powerdot.lyx, I get your errors all right when I copy the file I attached to my mail into the temporary. -- Jean-Pierre
Re: Layout for a letter (in French)
Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: Some remarks: - the layout file doesn't follow our layout file style and is in the quite old format 4 OK, I will check this - you use a lot of preamble code in the layout file, it this really needed? I didn't write the code, I guess it is needed to be able to type in the various elements of the letter in any order, I will review it. - in the preamble of the LyX example file you load the packages * lmodern - this is unnecessary because the user can decide in the document settings what font to use Right. * itemsep - this is not necessary as the file doesn't contain items. (When you really want to have no item separation, don't load this style file but set the length \itemsep to "0pt".) Right. - you used the LaTeX class "lettre" for your layout file. What about the other letter document classes LyX already supports? dinbrief and g-brief2 are in German but its strings can easily be translated to French. have you already had a look if support for them might be useful? Yes, these letter layouts do not follow the French presentation of letters. I guess this is the reason why there are several German alternatives to the letter layout. -- Jean-Pierre
Example file seminar.lyx translation in French
Hello, Please find attached a French translation of the example. Note that the English version suffers from the bug described in the last slide: a4paper appears a class option, so that the complilation fails with earlier versions of seminar. I suppressed it in the translated file. In addition I find the explanation unclear, I would suggest: ...in the menu Document->Settings->Page Layout set the Paper Size to “a4” (unless it is the default layout of your LaTeX distribution) and remove "a4paper"... The first note says nothing about PDF (ps2pdf). Here I find it better than dvipdfm: the third slide does not appear rotated. Finally, I think that the layout could be modified to get the slideheadings next to the slide control styles. I guess this will wait 1.6.6. -- Jean-Pierre seminar.lyx Description: application/lyx
Re: powerdot-example
Ignacio Garcia a écrit : This issue remains too: the author names don't appear in the pdf output. It happens also with the English version in branch. Is it true for you? Putting the LyX note in the Title environment, beside "A LyX sample", fix it here. Right, here is an updated version of the French translation. -- Jean-Pierre exemple-powerdot.lyx Description: application/lyx
Re: Beamer example update
Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: I see that the English and German Beamer templates are updated. Do I have time to update also the French template ? If you can send it very quick (within the next hours), I can consider it. Here it is. -- Jean-Pierre fr_beamer-conference-ornate-20min.lyx Description: application/lyx