from:"Jean\-Pierre Chrétien"

Additional.lyx: subsections 10.8, 10.9 and 10.10

2024-03-31 Thread Jean-Pierre Chrétien


Dear doc maintainers,

While updating the translation of the French Additional.lyx manual, I saw that 
in the original manual these three subsections, which were previously in a 
section entitled "Lyx Features needing Extra Software", appear now in section 
"The lyx Server".

This mistake was introduced with commit 7b447915c2464effea8bae1c0701745fbc30ea5f

I restored chapter 11 as before.

--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Text style menu entry

2021-05-14 Thread Jean-Pierre Chrétien


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

Re: Text style menu entry

2021-05-10 Thread Jean-Pierre Chrétien


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

2021-05-10 Thread Jean-Pierre Chrétien


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

2021-05-06 Thread Jean-Pierre Chrétien


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

Typo in Customization manual ?

2021-04-28 Thread Jean-Pierre Chrétien


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?

2021-02-10 Thread Jean-Pierre Chrétien


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

Re: Incorrect User guide documentation for passing options to nomencl package

2021-01-10 Thread Jean-Pierre Chrétien


Le 09/01/2021 à 20:17, Pavel Sanda a écrit :

On Fri, Jan 08, 2021 at 09:17:02PM -0500, Richard Kimberly Heck wrote:




Pavel, maybe that is a sub-topic for Monday: Who will do whatever it is
that Uwe used to do for major releases.


Good idea.
Jean-Pierre maybe you can join the meeting as well?


Sure, thanks for the invitation, I'm free to-morrow at 5pm CET. I will be glad 
to meet everybody in almost real after 20 years of mailing lists...


--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Incorrect User guide documentation for passing options to nomencl package

2021-01-08 Thread Jean-Pierre Chrétien


Le 08/01/2021 à 07:30, Richard Kimberly Heck a écrit :

On 1/5/21 5:30 PM, Diab Jerius wrote:


(BTW, The downloadable manuals from https://wiki.lyx.org/LyX/Manuals#UserGuide 
are out of date.  Is there a better place to get the latest ones?)


I'm not sure what the status of these is. Of course you can compile themselves 
from the Help menu.


Hello

Uwe used to keep these in sync... I can update the docs if you think it useful.

--
Jean-Pierre

--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Lyx version in preparation

2020-12-13 Thread Jean-Pierre Chrétien


Dear all,

In

https://www.lyx.org/RoadMap

the version number should be 2.3.7 rather than 2.3.6,, right ?

--
Jean-Pierre

--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Incorrect checkbox name in Customization manual

2020-07-12 Thread Jean-Pierre Chrétien


Hello,

While updating the Customization manual translation in French, I see at the end 
of section 5.3.13 a reference to the checkbox name “Full aut list”.


The effective name in the po file is "All authors".
I intend to correct this together with my update of the French manual. Is it OK 
?

--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: CiteEngine translation

2020-06-15 Thread Jean-Pierre Chrétien


Le 15/06/2020 à 13:44, Jean-Pierre Chrétien a écrit :

Le 15/06/2020 à 13:10, Jürgen Spitzmüller a écrit :

Am Montag, den 15.06.2020, 11:10 +0200 schrieb Jean-Pierre Chrétien:

While translating section 5.2.6 of the 2.3 Customization manual, I
see that the citengine command names cannot be translated.


What do you mean with "cite engine command names"?


I see
MaxCiteNames, CiteFramework, CiteEngine and CiteFormat.


OK, forget about this, entries in layout files, and thus citeengine files, are 
not translatable.

But it hurts in the flow of a translated paragraph, IMHO.

--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: CiteEngine translation

2020-06-15 Thread Jean-Pierre Chrétien


Le 15/06/2020 à 13:10, Jürgen Spitzmüller a écrit :

Am Montag, den 15.06.2020, 11:10 +0200 schrieb Jean-Pierre Chrétien:

While translating section 5.2.6 of the 2.3 Customization manual, I
see that the citengine command names cannot be translated.


What do you mean with "cite engine command names"?


I see
MaxCiteNames, CiteFramework, CiteEngine and CiteFormat.

But the descriptions which are part of the citeengine files contents are 
translatable (and translated in French).


--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

CiteEngine translation

2020-06-15 Thread Jean-Pierre Chrétien


Hello,

While translating section 5.2.6 of the 2.3 Customization manual, I see that the 
citengine command names cannot be translated.

Is this wanted ?

--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Finalize the translation of the LyX 2.3 series

2020-06-15 Thread Jean-Pierre Chrétien


Le 14/06/2020 à 19:25, Scott Kostyshak a écrit :



If I remember correctly, we used to use track changes for the documents.
That is, all of the text that needed translation was marked as changed.
Did we move away from that workflow? From the translator perspective, it
seems easier to navigate tracked changes.


My concern is about docs to be translated: I have new stuff in English from the 
time when Uwe used to paste it from the English original to the translated docs 
(French, German, Japanese and Italian AFAIR), and to record changes in txt 
documents at the root of the tree. This applies only to <= 2.3 manuals.


Starting with 2.4, it's up to the translator to check the changes in the English 
docs and to carry them in the foreign documents. It is thus necessary to have 
new stuff with tracking changes in the English source of documentation. IMHO, 
this is better because I do not have to track parts of the document in English, 
and developers' time is better spent making improvements than preparing 
translators' work.
I'm not sure to have finished the translation of 2.4 manuals before release, so 
a way to keep memory of tracking changes should be available before merging the 
changes for release.


Of course, this is not a criticism of Uwe's work, who was always concerned about 
helping people as much as possible.


--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Finalize the translation of the LyX 2.3 series

2020-06-14 Thread Jean-Pierre Chrétien


Le 14/06/2020 à 11:48, Jürgen Spitzmüller a écrit :

Am Sonntag, den 14.06.2020, 11:37 +0200 schrieb Jean-Pierre Chrétien:

Sure, I have seen the numerous improvements made. But as I
understand, it is now up to me to check the changes in the English
docs and report them in the French manual (currently, there are only
a few differences between e.g. the UserGuide versions in 2.3.x and
master), so the path to follow is

   * update the 2.3.x docs;

   * load the docs with 2.4.0dev to insure conversion;

   * save and commit the new docs in master;

   * check for changes in the English version (they are marked as
change tracking, right ?)


Yes.


BTW, is there a way to use the advanced search to detect text in English 
language (when I am in a French doc, of course).


--
Jean-Pierre


--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Finalize the translation of the LyX 2.3 series

2020-06-14 Thread Jean-Pierre Chrétien


Le 14/06/2020 à 11:25, Jürgen Spitzmüller a écrit :

Am Sonntag, den 14.06.2020, 10:17 +0200 schrieb Jean-Pierre Chrétien:

Is it the right way to proceed?


Generally yes. You should also check the tracked changes in the English
docs, though. There are quote some changes as compared to 2.3.x.


Sure, I have seen the numerous improvements made. But as I understand, it is now 
up to me to check the changes in the English docs and report them in the French 
manual (currently, there are only a few differences between e.g. the UserGuide 
versions in 2.3.x and master), so the path to follow is

 * update the 2.3.x docs;
 * load the docs with 2.4.0dev to insure conversion;
 * save and commit the new docs in master;
 * check for changes in the English version (they are marked as change 
tracking, right ?) and import them in the 2.4.x French docs;

 * translate.

Thanks for your help

--
Jean-Pierre

--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Finalize the translation of the LyX 2.3 series

2020-06-14 Thread Jean-Pierre Chrétien


Hello,

Some parts of the 2.3 documentation manuals remain untranslated in French:
 1/ in section 6.5.2 of the UserGuide, the biblatex documentation;
 2/ in section 7.2 of the Additional manual, the subsections about CVS, SVN and 
GIT;

 3/ a few paragraphs in section 7.3 of the same manual;
 4/ sections 5.3.13 and 5.3.14 of the Customization manual, and a few 
paragraphs about citengine.


2/ remains untranslated from the beginning, as users of these feature mots 
probably read English.

3/ and 4/ are not a big deal.
The main sections that I would like to get translated in the 2.3 documentation 
before tackling the 2.4 manuals is 1/.


I thus intend to translate in 2.3 and copy the translations in 2.4, as I 
understand that the 2.4 manuals have been edited to include the new functionalities.


Is it the right way to proceed?


--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Translations for 2.3.5

2020-05-21 Thread Jean-Pierre Chrétien


Le 20/05/2020 à 21:54, Richard Kimberly Heck a écrit :

We are now moving towards the release of 2.3.5. Please prepare
translations by the end of the month.


While compiling to test 2.3.5 against shortcuts, I get this (compiling 
--with-included-hunspell):



../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx: In member 
function ‘bool HunspellImpl::spell(const string&, int*, std::__cxx11::string*)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:562:7: warning: 
this statement may fall through [-Wimplicit-fallthrough=]

   }
   ^
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:564:5: note: 
here
 case INITCAP: {
 ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx: In member 
function ‘std::__debug::vector > 
HunspellImpl::suggest(const string&)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:900:16: 
warning: this statement may fall through [-Wimplicit-fallthrough=]

   capwords = 1;
   ~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:901:5: note: 
here
 case HUHCAP: {
 ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:1012:18: 
warning: this statement may fall through [-Wimplicit-fallthrough=]

 capwords = 1;
 ~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:1013:7: note: 
here
   case HUHCAP: {
   ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manpar../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx: 
In member function ‘bool HunspellImpl::spell(const string&, int*, 
std::__cxx11::string*)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:562:7: warning: 
this statement may fall through [-Wimplicit-fallthrough=]

   }
   ^
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:564:5: note: 
here
 case INITCAP: {
 ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx: In member 
function ‘std::__debug::vector > 
HunspellImpl::suggest(const string&)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:900:16: 
warning: this statement may fall through [-Wimplicit-fallthrough=]

   capwords = 1;
   ~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:901:5: note: 
here
 case HUHCAP: {
 ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:1012:18: 
warning: this statement may fall through [-Wimplicit-fallthrough=]

 capwords = 1;
 ~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/hunspell/hunspell.cxx:1013:7: note: 
here
   case HUHCAP: {
   ^~~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manparser.cxx: In member 
function ‘virtual bool ManParser::next_token(std::__cxx11::string&)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manparser.cxx:72:17: warning: 
this statement may fall through [-Wimplicit-fallthrough=]

   state = 2;
   ~~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manparser.cxx:75:7: note: 
here
   case 2:  // non word chars
   ^~~~

ser.cxx: In member function ‘virtual bool 
ManParser::next_token(std::__cxx11::string&)’:
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manparser.cxx:72:17: warning: 
this statement may fall through [-Wimplicit-fallthrough=]

   state = 2;
   ~~^~~
../../../2.3.x/3rdparty/hunspell/1.6.2/src/parsers/manparser.cxx:75:7: note: 
here
   case 2:  // non word chars
   ^~~~

--
Jean-Pierre
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: mistakes in french documentation

2019-05-08 Thread Jean-Pierre Chrétien


Le 07/05/2019 à 18:02, Edouard Genetay a écrit :
I'll write in french since i aim to signal french orthographical mistakes. If i 
send this e-mail to the wrong adress, please, send forward.


You should rather post to the French-speaking list : lyx...@lists.lyx.org,
where I post a copy of the present answer.



je mets en piece jointe les imprime ecran des erreurs.
"Coquille" est claire : c'est dans les paramètres. il est ecrit "si vous ne la 
appliquez".

"Coquille_2" apparait dans le tutoriel. "Maintenant mise le curseur"
et "coquille_3" apparait dans le guide d'utilisateur. la 5eme ligne de texte 
présente à la fin "si tout une structure".


Corrected for the coming soon lyx-2.3.3.

--
Thanks for pointing out these typos.
Jean-Pierre

Re: Some text missing in example_raw.lyx

2018-11-17 Thread Jean-Pierre Chrétien


Le 17/11/2018 à 12:14, Ravindra Pankaj a écrit :

Dear Sir/Madam,
In file example_raw.lyx, section 5, Notes is missing compared to 
example_lyxified.lyx file. Is it done deliberately or on purpose?
I am using Lyx on Fedora 29 and Lyx was installed using Fedora's default package 
manager 'dnf'. I have attached lyx files with this mail.


Hello

I guess that it is done deliberately to add details about how raw was lyxified.

--
Regards
Jean-Pierre

Re: Bug Report

2018-06-12 Thread Jean-Pierre Chrétien


Le 12/06/2018 à 23:16, Jean-Pierre Chrétien a écrit :

Le 12/06/2018 à 20:24, Andrii Trelin a écrit :

Hello,

I've found quite an unexpected bug in LyX, the description is in the attachment.


I cannot reproduce this 


  on lyx-2.3.0

--
Jean-Pierre

Re: Bug Report

2018-06-12 Thread Jean-Pierre Chrétien


Le 12/06/2018 à 20:24, Andrii Trelin a écrit :

Hello,

I've found quite an unexpected bug in LyX, the description is in the attachment.


I cannot reproduce this, I can move the pane freely.
Up to date Debian Stretch, Qt5.

--
Jean-Pierre

Re: [Web site] recent notify posts

2018-04-03 Thread Jean-Pierre Chrétien


Le 03/04/2018 à 20:44, Apache a écrit :

All recent posts: http://www.lyx.org/wiki/index.php/Site/AllRecentChanges

* http://www.lyx.org/WebFr.Download . . . April 03, 2018, at 05:42 PM by 
skostysh
* http://www.lyx.org/WebFr.Download . . . April 03, 2018, at 05:44 PM by 
skostysh


Thanks for your corrections, Scott.

--
Jean-Pierre

Status of French documentation for 2.3.0

2018-02-21 Thread Jean-Pierre Chrétien


Dear all,

I've completed the update of the following manuals for 2.3.0, using the 
Changelog files:

 * Additional
 * EmbeddeObjects
 * LaTeXConfig
 * Math

(Section  7.3 of Additional has never been translated, and probably will not be 
as version control users are generally fluent in English.)


Unfortunately, I've not completed (and won't be able to so before 2.3.0 is out):
 * UserGuide
 * Customization

What is missing in both manuals is mostly what was added following the excellent 
work of Jürgen on biblatex and citeengine, which produced a lot

to translate :-). xtemplate documentation is missing as well in Customization.

I began to consider examples/PDF-form.lyx following Uwe's hint, but I didn't 
find the time to complete it either.


I will continue the documentation update during maintenance releases.

--
Regards
Jean-Pierre

Re: AGU and EGS layouts

2018-02-17 Thread Jean-Pierre Chrétien

Le 17/02/2018 à 15:01, José Abílio Matos a écrit :

On Friday, 16 February 2018 10.11.32 WET Jean-Pierre Chrétien wrote:
 > You are right, there is no hurry to remove unusable layouts. Maybe the best
 > would be to remove these when a layout for agujournal and one for copernicus
 > (for EGU) are available. It seems to me that agutex.layout can be reused
 > for agujournal, I will give a try later.

I have recently looked into copernicus

https://publications.copernicus.org/for_authors/latex_instructions.html

and they have this warning:

"Authors are kindly requested to make use of the template.tex file embedded in 
the LaTeX Package since most of the definitions for the structure of manuscript 
elements are described there. Since we convert all typeset TeX files into XML, 
the expressions and markups have to be highly standardized."

Does that mean that we should provide a Docbook layout ? I guess rather that we 
should be strict about the set of interfaced commands in the layout file.

 > José, I see that you developed with Martin a layout file and a set of .inc
 > files for use with DocBook. I guess this is obsolete as well?

Which ones?

These:

agu-dtd.layout
agu_stdclass.inc
agu_stdcounters.inc
agu_stdlists.inc
agu_stdsections.inc
agu_stdtitle.inc

The idea, if I remember correctly, about the docbook layout files is to have the 
same structure as the latex layout files.

Here I must confess that I am not quite familiar with docbook.

--
Jean-Pierre

Re: LyX: LaTeX failed

2018-02-16 Thread Jean-Pierre Chrétien


Le 16/02/2018 à 06:11, elloh van a écrit :

Dear Sir/Madam,

I have just installed LyX version 2.2.3 on my laptop but when I wanted to see my 
output in other formats, i. e., View[PDF(pdflatex)], the pdflatex gives the 
following error message:


"LyX: LaTeX failed
the external program pdflatex finished with an error.
It is recommended you fix the cause of external progam's error (check the 
logs)".

Please what should I do to overcome the problem ?


You posted to the wrong list, here we discuss documentation issues.
You would get better answers on the users' list:

lyx-us...@lists.lyx.org

while providing a minimal failing example and indicating on which platform you 
are working.


--
Jean-Pierre

Re: AGU and EGS layouts

2018-02-16 Thread Jean-Pierre Chrétien


Le 15/02/2018 à 21:14, Scott Kostyshak a écrit :

On Wed, Feb 14, 2018 at 04:56:24PM +, Jean-Pierre Chrétien wrote:

Le 14/02/2018 à 00:12, Scott Kostyshak a écrit :


I think the sections in Additional.lyx about obsolete document classes
should be removed. I propose the create a new LyX file in Git's attic folder
which will contain the deleted sections.
When you delete the sections, please do t for all language versions of
Additional.lyx in branch an master.


Jean-Pierre, did you finish the work that you planned on 2.3.x regarding
this?


I'm almost done with the documentation part, I have edited all
Additional.lyx files and moved AGUTeX.lyx in templates/obsolete. I see that
I should have put an original version of Additional.lyx in the attic, I will
do it with appropriate LyX notes.

I'm going to delete jgrga.layout and agums.layout, which were used by
pre-2008 agutex.cls and reused by aguplus.cls (which is still in TeXLive,
but obsolete in CTAN, so I think it will not be part anymore of
TeXLive2018).
aguplus (1999) was in turn obsoleted by post-2008 agutex.cls, which included
jgrga and agums (and others) as class options coded in the class file
instead of  external .sty files.

Currently, here I can compile successfully AGUTeX.lyx which used
agutex.layout and post-2008 agutex.cls, that I have installed in my
texmf-local tree in 2013 when it was available.

As it is now impossible to find the agutex.cls class (agujournal.cls is the
current AGU class), the template/obsolete/AGUTeX.lyx can only be compiled if
one has kept the class file in one's texmf-local tree, and this only for the
sake of recreation of the pdf of an old paper, any new paper needing
agujournal.

So should I remove also template/obsolete/AGUTeX.lyx? What is the
compilation status of other obsoleted templates?

As for EGS, I'm going to remove egs.layout as well, the class is obsolete
since 2001, and there is no template.

I do not think that it is feasible to build a layout and template for the
new agujournal.cls and copernicus.cls classes for 2.3.0, it will involve
strings changes.

The AGUTeX wiki page

http://wiki.lyx.org/Examples/AGUTeX

is completely out of date for Linux, I will edit that also.


Thanks for this detailed update, Jean-Pierre.

I agree with your changes for AGUTeX since I was familiar with that
particular situation and since we had not decided on the final release
date. As for the other obsolete layout files and classes, now that we
have decided the final release could be in a week or so, I would prefer
to not make those changes at this point. These removals should ideally
be done at the beginning of the release cycle.  Further, I'm worried
that we could miss something (e.g. forgetting to change the Make files
or making a typo in the Make files). I'm sorry if it seemed like I gave
the green light to go through all the obsolete layout files. If both you
and Uwe disagree with me and express your disagreement by Monday and you
can complete all of the work by Monday, I could be convinced with these
extra removals. Otherwise, I would suggest going forward with the work
on master.


You are right, there is no hurry to remove unusable layouts. Maybe the best 
would be to remove these when a layout for agujournal and one for copernicus 
(for EGU) are available. It seems to me that agutex.layout can be reused for 
agujournal, I will give a try later.


As these are new layouts (and hopefully, templates), this can be done with the 
2.3 maintenance releases, it is not necessary to wait for master release.


José, I see that you developed with Martin a layout file and a set of .inc files 
for use with DocBook. I guess this is obsolete as well?


--
Jean-Pierre

Re: AGU and EGS layouts

2018-02-14 Thread Jean-Pierre Chrétien


Le 14/02/2018 à 00:12, Scott Kostyshak a écrit :


I think the sections in Additional.lyx about obsolete document classes
should be removed. I propose the create a new LyX file in Git's attic folder
which will contain the deleted sections.
When you delete the sections, please do t for all language versions of
Additional.lyx in branch an master.


Jean-Pierre, did you finish the work that you planned on 2.3.x regarding
this?


I'm almost done with the documentation part, I have edited all Additional.lyx 
files and moved AGUTeX.lyx in templates/obsolete. I see that I should have put 
an original version of Additional.lyx in the attic, I will do it with 
appropriate LyX notes.


I'm going to delete jgrga.layout and agums.layout, which were used by pre-2008 
agutex.cls and reused by aguplus.cls (which is still in TeXLive, but obsolete in 
CTAN, so I think it will not be part anymore of TeXLive2018).
aguplus (1999) was in turn obsoleted by post-2008 agutex.cls, which included 
jgrga and agums (and others) as class options coded in the class file instead of 
 external .sty files.


Currently, here I can compile successfully AGUTeX.lyx which used agutex.layout 
and post-2008 agutex.cls, that I have installed in my texmf-local tree in 2013 
when it was available.


As it is now impossible to find the agutex.cls class (agujournal.cls is the 
current AGU class), the template/obsolete/AGUTeX.lyx can only be compiled if one 
has kept the class file in one's texmf-local tree, and this only for the sake of 
recreation of the pdf of an old paper, any new paper needing agujournal.


So should I remove also template/obsolete/AGUTeX.lyx? What is the compilation 
status of other obsoleted templates?


As for EGS, I'm going to remove egs.layout as well, the class is obsolete since 
2001, and there is no template.


I do not think that it is feasible to build a layout and template for the new 
agujournal.cls and copernicus.cls classes for 2.3.0, it will involve strings 
changes.


The AGUTeX wiki page

http://wiki.lyx.org/Examples/AGUTeX

is completely out of date for Linux, I will edit that also.

--
Jean-Pierre

Re: AGU and EGS layouts

2018-02-08 Thread Jean-Pierre Chrétien


Le 31/01/2018 à 21:15, Scott Kostyshak a écrit :

On Wed, Jan 31, 2018 at 09:41:51AM +, Jean-Pierre Chrétien wrote:



I don't think that agujournal.layout and copernicus.layout (not to speak of
the corresponding templates) can be ready for 2.3.0, unless someone has done
the job already.


OK.


But editing sections 6.4 and 6.7 of Additional and moving AGUTeX.lyx to
templates/obsolete is not a big deal, and this has waited 2 years for AGU
and 15 years for EGS, so it's time to do something IMHO.


I'm fine with it if Uwe supports it. Uwe, what do you think?


Uwe, can you have a look at this thread? May I edit Additional.lyx to cope for 
obsoleted classes?


--
Jean-Pierre

Re: AGU and EGS layouts

2018-01-31 Thread Jean-Pierre Chrétien


Le 30/01/2018 à 19:09, Scott Kostyshak a écrit :

On Tue, Jan 30, 2018 at 04:59:53PM +, Jean-Pierre Chrétien wrote:


What do you think?


I am fine with whatever you suggest. Thank you for that detailed
explanation, Jean-Pierre!

Since these are somewhat big changes, perhaps let's just do them in
master, unless you have a strong preference for doing them before 2.3.0?


I don't think that agujournal.layout and copernicus.layout (not to speak of the 
corresponding templates) can be ready for 2.3.0, unless someone has done the job 
already.


But editing sections 6.4 and 6.7 of Additional and moving AGUTeX.lyx to 
templates/obsolete is not a big deal, and this has waited 2 years for AGU and 15 
years for EGS, so it's time to do something IMHO.


BTW, I can copy AGUTeX.lyx to templates/obsolete with git, but how can one 
remove a file in the repository?


--
Jean-Pierre

AGU and EGS layouts

2018-01-30 Thread Jean-Pierre Chrétien


Hello,

While translating sections 6.4 and 6.7 of the Additional manual (provided 
together with the corresponding layouts by Martin Vermeer), I understood that 
both sections are outdated:


 * AGU (American Geophysical Union) published initially agutex.cls with a set 
of ancillary .sty files (e.g. jgrga.sty) for the various journals published.
As this class missed several features, P. Daly from Max Planck Institut wrote 
class aguplus.cls to enhance the original class, keeping the references to the 
ancillary files.
Then AGU published an improved version of the same agutex.cls file which did not 
need any more the ancillary files, jgrga becoming a simple option of the 
agutex.cls file (this version of agutex.cls, dated Feb. 9, 2008 is the one 
pointed to by the link in section 6.4 of Additional). This obsoleted aguplus as 
e.g. jgrga.sty was no more available
Eventually AGU published in 2016 agujournal.cls, an up-to-date class for AGU 
papers.
So in spite of the fact that the .sty files are not available any more, the LyX 
template AGUTeX.lyx can still be compiled if the files in AGU-LaTeX.zip are 
installed. The template correctly indicates that agujournal.cls should now be used.


 * EGS became part of EGU (European Geosciences Union) in 2002, and the egs.cls 
class has been obsolete for quite a time. It is replaced by copernicus.cls, a 
class which allows to build any paper for the EGU.


What can we do about this ?
 * the AGUTeX.lyx file should be moved to obsoleted templates;
 * reference to aguplus in section 6.4 should be replaced by a short recall of 
the agutex obsolete syntax, until a layout and hopefully template is created;
 * section 6.7 should only mention the pending layout and hopefully template 
for copernicus.cls.


Unless Martin has written layouts for the new classes, maybe we should look for 
geophysicians to help us with the layouts and templates.


What do you think?

--
Jean-Pierre

Re: undertilde is not in TeXLive

2017-10-27 Thread Jean-Pierre Chrétien


Le 27/10/2017 à 11:01, John Robert Hudson a écrit :



Hi Jean-Pierre
I have TeXLive installed and the undertilde is in the wsuipa package which was
installed automatically from the openSUSE repositories. (There are other
packages which contain equivalents.)


I'm on my own with it, I dowload directly from the site.

Should I change my formulation like this ?
Replace

undertilde is not in TexLive due to licensing issues.
If you have TeXLive installed and want to see the effect of command utilde
in the output, you must fetch the package from CTAN.

by

undertilde is not in the native TexLive distribution due to licensing issues. If 
undertilde.sty is not installed on your system, and if you want to see the 
effect of command utilde in the output of this manual (sec 7.1), you must fetch 
the package from CTAN.


--
Jean-Pierre

undertilde is not in TeXLive

2017-10-27 Thread Jean-Pierre Chrétien




Hello

I found useful to add a hint about this in the Math manual
(see attached).

It's true for Linux, not on Windows if one uses MikTeX, right ?
What about MacOS ?

Uwe, OK to commit ?

--
Jean-Pierre

diff --git a/lib/doc/Changelog-Math-LyX_23.txt b/lib/doc/Changelog-Math-LyX_23.txt
index 2b6f49747b..9826b77134 100644
--- a/lib/doc/Changelog-Math-LyX_23.txt
+++ b/lib/doc/Changelog-Math-LyX_23.txt
@@ -5,6 +5,9 @@ Modified (not F, not J):
 first step:
 - sec. 17: completely rewritten
 
+second step:
+- initial note: new sentence, warning about undertilde
+
 
 For LyX 2.2.3:
 
@@ -17,6 +20,8 @@ For LyX 2.2.1:
 - sec. 23.1: new note
 
 
+
+
 For LyX 2.2.0:
 
 In the first step:
diff --git a/lib/doc/Math.lyx b/lib/doc/Math.lyx
index 8a5e896266..4f878b96cf 100644
--- a/lib/doc/Math.lyx
+++ b/lib/doc/Math.lyx
@@ -312,6 +312,19 @@ mhchem
 \end_layout
 
 \begin_layout Plain Layout
+Note that 
+\series bold
+undertilde
+\series default
+ is not in TexLive due to licensing issues.
+ If you have TeXLive installed and want to see the effect of command 
+\series bold
+utilde
+\series default
+ in the output, you must fetch it from CTAN.
+\end_layout
+
+\begin_layout Plain Layout
 The latest PDF-version of this document can be found here:
 \begin_inset Newline newline
 \end_inset
diff --git a/lib/doc/de/Math.lyx b/lib/doc/de/Math.lyx
index b99c417025..de463231b9 100644
--- a/lib/doc/de/Math.lyx
+++ b/lib/doc/de/Math.lyx
@@ -325,6 +325,21 @@ mhchem
 \end_layout
 
 \begin_layout Plain Layout
+
+\lang english
+Note that 
+\series bold
+undertilde
+\series default
+ is not in TexLive due to licensing issues.
+ If you have TeXLive installed and want to see the effect of command 
+\series bold
+utilde
+\series default
+ in the output, you must fetch it from CTAN.
+\end_layout
+
+\begin_layout Plain Layout
 Die neueste PDF-Version dieses Dokuments ist hier zu finden:
 \begin_inset Newline newline
 \end_inset
diff --git a/lib/doc/es/Math.lyx b/lib/doc/es/Math.lyx
index 9391dd9b6b..714274ca2b 100644
--- a/lib/doc/es/Math.lyx
+++ b/lib/doc/es/Math.lyx
@@ -316,6 +316,21 @@ mhchem
 \end_layout
 
 \begin_layout Plain Layout
+
+\lang english
+Note that 
+\series bold
+undertilde
+\series default
+ is not in TexLive due to licensing issues.
+ If you have TeXLive installed and want to see the effect of command 
+\series bold
+utilde
+\series default
+ in the output, you must fetch it from CTAN.
+\end_layout
+
+\begin_layout Plain Layout
 La Ãºltima versiÃ³n PDF de este documento estÃ¡ disponible en:
 \begin_inset Newline newline
 \end_inset
diff --git a/lib/doc/fr/Math.lyx b/lib/doc/fr/Math.lyx
index ed26d4a866..ff01d566b4 100644
--- a/lib/doc/fr/Math.lyx
+++ b/lib/doc/fr/Math.lyx
@@ -349,6 +349,19 @@ mhchem
 \end_layout
 
 \begin_layout Plain Layout
+Notez que 
+\series bold
+undertilde
+\series default
+ n'est pas dans TexLive pour des taisons de licence.
+ Si vous travaillez avec TeXLive et si vous voulez voir l'effet de la commande
+\series bold
+ utilde
+\series default
+ dans le rÃ©sultat, vous devez l'installer depuis CTAN.
+\end_layout
+
+\begin_layout Plain Layout
 On peut trouver la derniÃ¨re version de ce document ici:
 \begin_inset Newline newline
 \end_inset
diff --git a/lib/doc/ja/Math.lyx b/lib/doc/ja/Math.lyx
index 4f363ee980..d0b5675ee3 100644
--- a/lib/doc/ja/Math.lyx
+++ b/lib/doc/ja/Math.lyx
@@ -366,6 +366,21 @@ mhchem
 \end_layout
 
 \begin_layout Plain Layout
+
+\lang english
+Note that 
+\series bold
+undertilde
+\series default
+ is not in TexLive due to licensing issues.
+ If you have TeXLive installed and want to see the effect of command 
+\series bold
+utilde
+\series default
+ in the output, you must fetch it from CTAN.
+\end_layout
+
+\begin_layout Plain Layout
 ãã®ææ¸ã®ææ°ã®PDFçã¯
 \begin_inset Newline newline
 \end_inset
@@ -37042,7 +37057,7 @@ literal "false"
 \begin_inset CommandInset index_print
 LatexCommand printindex
 type "idx"
-name "Index"
+name "ç´¢å¼"
 literal "false"
 
 \end_inset

Re: Questions, bugs et déception pour un utilisateur débutant

2017-08-14 Thread Jean-Pierre Chrétien


Le 13/08/2017 à 23:12, Surlezi Surlezi a écrit :

Chers contributeurs de Lyx, je me permets ce message, à la fois pour en espérer
une aide, et aussi peut être pour vous permettre d’améliorer Lyx.


La liste est anglophone, mais je vous réponds exceptionnellement en français,
j'ai posté un résumé aux développeurs.




*Contexte*

J’ai utilisé LaTeX en 1999 et 2000 pour un rapport de DEA et dans le cadre
professionnel. Depuis, je n’ai plus eu l’occasion de l’utiliser, et j’ai aussi
perdu la plus grand partie de ma faible compétence en programmation du fait
d’une reconversion. Je suis par contre encore un utilisateur assez éclairé des
outils informatiques standards, Windows, Osx.


Aujourd’hui je veux aider une amie à rédiger sa thèse de doctorat en médecine
avec un rendu propre selon moi, donc LaTeX et non pas Word ou Libreoffice.

Lyx m’a semblé une facilité pour elle comme pour moi.


*Système*

Sur mon iMac 2011 (OSX 10.12.5), j’ai donc installé MacTeX (la version du 24 mai
2017), Lyx (2.2.3). J’ai Firefox comme navigateur, qui est aussi installé dans
mes machines virtuelles WinXP et Win10 qui tournent sous Parallels Desktop. Je
pense que c’est une installation tout à fait banale, mais bien faite.


OK




*Je dois dire que j’ai déchanté dès la première minute d’utilisation de Lyx.*

1- lorsque je fais « view » du fichier « splashscreen » pour le voir en pdf, je
recois le message d’erreur suivant :


Images intégrées 1

Un peu décevant pour une installation propre, mais ca peut passer, car un PDF
finit par sortir, avec seulement un défaut mineur, après avoir cliqué « afficher
la sortie malgré tout ». J’imagine qu’il manque un visualiseur SVG comme
Inkscape ? Un peu tâche quand même. Le défaut présumé :

Images intégrées 2


Oui, il manque l’icône de la barre d'outils qui n'a pas été extraite du svgz.
mais Inkscape n'est pas installé nativement sur Mac ? Apparemment su ma Debian 
Stretch il vient avec Gnome.






*2- Manuel d’apprentissage ?*

Là où je pense que l’utilisateur lambda fera demi-tour c’est quand il voudra
mettre en œuvre les recommandations du « tutorial » : Aide=>Manuel 
d’apprentissage

Au 2.1 on me parle du « répertoire examples/fr du dossier d'installation de
LyX » et de fichier « exemple_brut.lyx » .

Mais où sont ces fichiers ??! Il n’ya pas de répertoire d’installation sous Mac.


Je n'y connais rien au Mac, mais ça m'étonne beaucoup. J'ai demandé au 
développeur de LyX qui gère les paquetages sous mac.



Il n’y pas d’adresse ou de lien correct dans le tutoriel. Il n’y pas de fonction
spécifique Fichier=>Ouvrir fichier d’apprentissage dans Lyx.


Ici, Fichier>Ouvrir me propose un bouton « Exemples » qui me permet d'explorer 
le répertoires des exemples. Vous ne le voyez pas ?




Et bien oui, il faut aller ouvrir dans le dossier « applications » où j’ai mis
l’appli Lyx et il faut que j’ affiche dans le finder le contenu du paquet, pour
pouvoir naviguer dans Lyx=>Contents=>Ressources=>Examples !!!

Et comme ceci (afficher le contenu d’un paquet) n’est pas possible avec
Fichier=>Ouvrir de lyx, il faut que je copie mon dossier examples ailleurs sur
mon disque dur pour y accéder.


Ce n'est sûrement pas la procédure normale.



Nul doute qu’à ce point Lyx a déjà perdu 80 % de ses utilisateurs potentiels.


Si vous le dites...




*3- Machine virtuelle diabolique*

Là où je n’irai sans doute pas plus loin pour ma part, c’est avec ce qui suit,
pour lequel je n’ai trouvé aucune aide nulle part :

a- j’ai créé un nouveau document

b- j’ai écrit coucou

c- je suis allé dans Document=>Paramètres=>Classe de document et au lieu de
rester à « article (classe standard) » j’ai essayé autre chose, par exemple
« chapitre Docbook (SGML) », puis OK.

d- j’ai donc fait « visionner »… et pan ! Voilà ma machine virtuelle avec
windows qui démarre. Et rien qui ne se passe dedans.

Je pense que Lyx veut utiliser le Firefox de ma machine virtuelle au lieu de
celle par défaut d’OSX. Quelle idée incroyable ! Comment peut il ne pas prendre
le navigateur par défaut.

J’ai supprimé Parallels Desktop, puis Lyx, et réinstallé Lyx, et voici le
message que je recois malgré tout:



Images intégrées 3


Vous pouvez essayer Outils>Reconfigurer ? Visiblement LyX ne trouve pas votre 
Firefox Mac.

Ici j'affiche coucou tant en LyXHTML qu'en dvi.



e- je suis allé voir dans Lyx => Préférences => Gestion des fichies =>
Convertisseurs et aussi Formats de fichiers

Voilà l’incroyable charabia qu’on y trouve :


Images intégrées 4


Pas même la possibilité de comprendre ce qui ne va pas. Encore moins de choisir
une application en la désignant en navigant par le finder pour faire la tâche,
il faut comprendre le martien…


Je confirme, LyX ne trouve pas votre navigateur mac.
Cette fenêtre de dialogue est détaillée dans la section 3.1 du manuel de 
Personnalisation.





*Conclusion*

Je pense n’avoir que rarement ressenti une telle frustration face à un logiciel
quel qu’il soit, pardon si mon ton en est quelque peu

Re: Translations for 2.1.5

2016-05-26 Thread Jean-Pierre Chrétien


Le 24/05/2016 23:40, Richard Heck a écrit :


With 2.2.0 suddenly by-passing RC2 and being released, I'm afraid I'm a
bit behind asking for translations for 2.1.5, the final release in the
2.1.x series. Please prepare translations as soon as you are able: by
Friday, 3 June, if at all possible. Let me know if that timeline is too
tight.


No problem, fr.po is up to date, but as I wanted to compile branch to make a 
finale check about shortcuts, I get this when I run autogen.sh



$ ./autogen.sh
Using automake (GNU automake) 1.14.1
Using autoconf (GNU Autoconf) 2.69
Building macros...
Building config header template...
Building Makefile templates...
boost/Makefile.am:19: warning: source file 'libs/regex/src/c_regex_traits.cpp' 
is in a subdirectory,

boost/Makefile.am:19: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding 
output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same 
subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
boost/Makefile.am:19: warning: source file 'libs/regex/src/cpp_regex_traits.cpp' 
is in a subdirectory,

boost/Makefile.am:19: but option 'subdir-objects' is disabled
boost/Makefile.am:19: warning: source file 'libs/regex/src/cregex.cpp' is in a 
subdirectory,

boost/Makefile.am:19: but option 'subdir-objects' is disabled
...
[snip]
...
src/tex2lyx/Makefile.am:71: warning: source file '../version.cpp' is in a 
subdirectory,

src/tex2lyx/Makefile.am:71: but option 'subdir-objects' is disabled
Building configure...
Building po/POTFILES.in...

run "./configure && make"


Same result if I build in a fresh anonymous clone.
Any clue ?

--
Jean-Pierre

Re: Final round: Request to update docs for LyX 2.2.0

2016-02-03 Thread Jean-Pierre Chrétien


Le 03/02/2016 20:51, Uwe Stöhr a écrit :


I am not sure if you have implemented the changed name
longtable -> multi-page table
in EmbeddedObjects:

- the term "longtable" was replaced by "multi-page table"
   please rename all occurrences (including the cross-references and the
   index entries)of longtable accordingly
   occurrences: sec. 2.2, 2.6, 2.7, 4.2


Uwe, sorry I did not stress this earlier, but there is a message in po files :

LongTableNoNumber

which I translated correctly in French, but which should be changed in the 
source code (in stdinsets.inc, line 578), and translated as well in the po 
files. This translation is needed after string freeze, maybe this can wait after 
beta?


--
Jean-Pierre

Re: Math manual

2016-01-03 Thread Jean-Pierre Chrétien



Le 3 janvier 2016 09:18:36 CET, Scott Kostyshak <skost...@lyx.org> a écrit :
>On Sat, Jan 02, 2016 at 02:44:24PM +0000, Jean-Pierre Chrétien wrote:
>> Le 02/01/2016 09:07, Scott Kostyshak a écrit :
>> >On Sat, Jan 02, 2016 at 08:08:12AM +0000, Jean-Pierre Chrétien
>wrote:
>> >>Le 02/01/2016 01:31, Scott Kostyshak a écrit :

>
>Ah I see. So to confirm: the fix is that all we have to do is replace
>http://physics.nist.gov/Document/checklist.pdf
>with
>http://physics.nist.gov/Pubs/SP811/sec11.html
>?
>

Roger

-- 
Jean-Pierre

splash.lyx

2015-07-29 Thread Jean-Pierre Chrétien


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

splash.lyx

2015-07-29 Thread Jean-Pierre Chrétien


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 
Répondre à : cont...@jardinsdejade.fr
Pour : LyX Documentation Team 

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

Warnings while exporting UserGuide to pdf

2015-03-26 Thread Jean-Pierre Chrétien


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

Warnings while exporting UserGuide to pdf

2015-03-26 Thread Jean-Pierre Chrétien


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

Re: Intro manual

2015-03-09 Thread Jean-Pierre Chrétien


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

Re: Intro manual

2015-03-09 Thread Jean-Pierre Chrétien


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

splash.lyx

2015-02-12 Thread Jean-Pierre Chrétien


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

splash.lyx

2015-02-12 Thread Jean-Pierre Chrétien


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: Translations of Math environments in LyX output for LyX 2.1

2014-04-11 Thread Jean-Pierre Chrétien


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: Translations of Math environments in LyX output for LyX 2.1

2014-04-11 Thread Jean-Pierre Chrétien


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: Translations of Math environments in LyX output for LyX 2.1

2014-04-10 Thread Jean-Pierre Chrétien


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

2014-04-10 Thread Jean-Pierre Chrétien


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

Typos in Customization.lyx

2014-01-23 Thread Jean-Pierre Chrétien


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

2014-01-23 Thread Jean-Pierre Chrétien


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

Typos in Customization.lyx

2014-01-23 Thread Jean-Pierre Chrétien


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 misc %author%, “%title”. read
misc %author%, “%title%”.?

Appendix B: legend for "buttonbg" should read "Color used for button background"

--
Regards
Jean-Pierre

Re: Typos in Customization.lyx

2014-01-23 Thread Jean-Pierre Chrétien


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: Remarques sur l'intro à LyX

2013-09-15 Thread Jean-Pierre Chrétien


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

Re: Remarques sur l'intro à LyX

2013-09-15 Thread Jean-Pierre Chrétien


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

Typo

2013-05-28 Thread Jean-Pierre Chrétien


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

2013-05-28 Thread Jean-Pierre Chrétien


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

Typo

2013-05-28 Thread Jean-Pierre Chrétien


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)"
 DefaultArg"type=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)"
 DefaultArg"type=1"
   EndArgument
 End

Re: Typo

2013-05-28 Thread Jean-Pierre Chrétien


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)"
 DefaultArg"type=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)"
 DefaultArg"type=1"
   EndArgument
 End

Typo in UserGuide

2013-04-21 Thread Jean-Pierre Chrétien


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 in UserGuide

2013-04-21 Thread Jean-Pierre Chrétien


Hello,

In section 5.2 of the UserGuide, the following sentence:


For example, that is how you would construct the brackets around a matrix:

 and to make it easier to see the layers of parentheses.


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

Re: Faute de frappe dans Introduction à LyX

2013-02-02 Thread Jean-Pierre Chrétien


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

Re: Faute de frappe dans "Introduction à LyX"

2013-02-02 Thread Jean-Pierre Chrétien


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

Re: Issues with Tutorial Section 3.4 Labels and Cross-References

2012-11-30 Thread Jean-Pierre Chrétien


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

2012-11-30 Thread Jean-Pierre Chrétien


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

2012-11-30 Thread Jean-Pierre Chrétien


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: Issues with Tutorial Section 3.4 Labels and Cross-References

2012-11-30 Thread Jean-Pierre Chrétien


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 " on page " cross
reference. But you forget to tell us two things: 1, that this cross
reference will simply omit "on 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:

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).



You are however right about the crossref procedure insertion, which should be 
changed to:



If you want to know more about this document, then see Section.

Now — with the cursor after the word “Section” — choose Insert->Cross 
Reference...


--
Jean-Pierre

Re: Issues with Tutorial Section 3.4 Labels and Cross-References

2012-11-30 Thread Jean-Pierre Chrétien


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:


If you want to know more about this document, then see Section.

Now — with the cursor after the word “Section” — choose Insert->Cross
Reference...



Rather with a space before the period (an unbreakable space in fact, as 
explained further in the section):



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...


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

2012-11-30 Thread Jean-Pierre Chrétien


Le 30/11/2012 15:51, Jean-Pierre Chrétien a écrit :

Le 30/11/2012 14:41, Jean-Pierre Chrétien a écrit :




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...

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

How to mirror LyX sites Web page

2012-08-22 Thread Jean-Pierre Chrétien


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

How to mirror LyX sites Web page

2012-08-22 Thread Jean-Pierre Chrétien


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: URGENT help with LYX

2012-08-20 Thread Jean-Pierre Chrétien


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

Re: URGENT help with LYX

2012-08-20 Thread Jean-Pierre Chrétien


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

Listing of English pages in the website translation page

2012-07-03 Thread Jean-Pierre Chrétien

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

2012-07-03 Thread Jean-Pierre Chrétien


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

Listing of English pages in the website translation page

2012-07-03 Thread Jean-Pierre Chrétien

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

2012-07-03 Thread Jean-Pierre Chrétien


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

Website translated pages flag pointers

2012-05-03 Thread Jean-Pierre Chrétien


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

Website translated pages flag pointers

2012-05-03 Thread Jean-Pierre Chrétien


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

Re: lyx-docs@lists.lyx.org

2012-01-19 Thread Jean-Pierre Chrétien


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

Re: lyx-docs@lists.lyx.org

2012-01-19 Thread Jean-Pierre Chrétien


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

Documents>Settings>Bibliography>Natbib>Natbib style>numerical

[#ID] in the citation menu

and adding the keywords "sort" to the class options in
Documents>Settings>Document class>Options

will do it.

With biblatex, seems that the keywords "style=numeric-comp" in the class options 
do the trick.


--
Jean-Pierre

Re: Local Layouts - Additional Features manual?

2012-01-12 Thread Jean-Pierre Chrétien


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: Local Layouts -> Additional Features manual?

2012-01-12 Thread Jean-Pierre Chrétien


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

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

Consistency of strrings in theroems modules

2011-11-04 Thread Jean-Pierre Chrétien


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

Consistency of strrings in theroems modules

2011-11-04 Thread Jean-Pierre Chrétien


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: powerdot-example.lyx fails to compile with TL 2011/MikTeX 2.9

2011-10-09 Thread Jean-Pierre Chrétien


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

Re: powerdot-example.lyx fails to compile with TL 2011/MikTeX 2.9

2011-10-09 Thread Jean-Pierre Chrétien


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 Document>Settings>Document 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

Re: powerdot-example.lyx fails to compile with TL 2011/MikTeX 2.9

2011-10-07 Thread Jean-Pierre Chrétien


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

2011-10-07 Thread Jean-Pierre Chrétien


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: ."


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: Current values of lyx versions in I18n web page

2011-09-02 Thread Jean-Pierre Chrétien


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: Current values of lyx versions in I18n web page

2011-09-02 Thread Jean-Pierre Chrétien


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

Current values of lyx versions in I18n web page

2011-09-01 Thread Jean-Pierre Chrétien


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

Current values of lyx versions in I18n web page

2011-09-01 Thread Jean-Pierre Chrétien


Hello,

I read this in http://www.lyx.org/I18n


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.



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 @@

Re: Translation of shortcuts descriptions via Lyx info insets

2011-08-29 Thread Jean-Pierre Chrétien


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

Re: Translation of shortcuts descriptions via Lyx info insets

2011-08-29 Thread Jean-Pierre Chrétien


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 Document>Settings?
 - if I open Tools>Preferences>Editing>Shortcuts 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

Fwd: Additional manual

2011-06-21 Thread Jean-Pierre Chrétien



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

Fwd: Additional manual

2011-06-21 Thread Jean-Pierre Chrétien



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

enumitem.lyx

2011-06-15 Thread Jean-Pierre Chrétien


Hello,

There are two items in German in this example file.
Are they intended to be so?

--
Jean-Pierre

enumitem.lyx

2011-06-15 Thread Jean-Pierre Chrétien


Hello,

There are two items in German in this example file.
Are they intended to be so?

--
Jean-Pierre

1 2 >

1 - 100 of 188 matches

Mail list logo