Re: "section" in lyx for win10

[Jean-Marc Lasgouttes]

Le 01/04/2024 à 05:24, shanze_gao a écrit :

Dear sir or madam,

I am new for lyx. I read doc/Tutorial. In "2.2.1 Sections and 
Subsections", it says "Now hit Return. Note that the Environment box 
changes from 'Section' back to 'Standard'." It does not work so in my 
computer. In fact, a new section environment appear in a new line. Maybe 
the docs should be updated for lyx 2.3.1 for win10.


Anyway, I like lyx and hope it becomes better. Thanks for your efforts.


Dear Shanze,

Are you actually using LyX 2.3.1? You could try to update to 2.3.7.
I tried with it and did not see the bug you mention.

Regards,
Jean-Marc

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

Re: affichage

[Jean-Marc Lasgouttes]

Le 10/11/2023 à 15:57, blondot a écrit :
Bonjour pourquoi l' aide objets insérées n' arrive pas à à s' afficher 
ni en postscipt ni en pdf  soit parce que les figures en png soit pour 
d' autres raisons obscures . Avec linuxmint  j' arrive à un résultat 
avec pdflatex mais sur débian 12.1 cela ne marche pas ! Merci pour la 
réponse . Bernard Blondot  (ps avec d' anciennes versions de linux et de 
lyx je n' avais aucun problème )


[For the others: it is a problem with previewing the EmbeddedObjects 
manual. Probably a missing tool]


Bonjour,

Je soupçonne qu'il y a un programme ou un package manquant quelque part. 
Y a-t-il un message d'erreur ? Ou un message sur la console en lançant 
LyX depuis un  terminal ?


JMarc

PS : idéalement, c'est mieux d'écrire sur lyx-users (en Anglais) ou 
lyx-fr (en Français) pour de genre de question.

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

Re: Using dynamic text in manuals: yes or no?

[Jean-Marc Lasgouttes]

Le 18/09/2023 à 22:13, Dan a écrit :

Attached to this e-mail is a showcase file (chapter 2 of Tutorial, current 
version in master branch), so that everyone can have a look and tinker with it.
This example already displays some of the benefits I pointed out previously, 
namely automatic update of strings in UI (see Text Properties in attached file).


This is nice indeed.


Some limits should be placed to the usage of info insets, though, as the 
example makes clear.
*Localized GUI strings*, is the exact string in souce code, metacharacters included 
(&, |, [[context]]); plus, the string may not be unique either. So this should 
be used with caution
     + DOs: for unique and seldom used/changed strings such as names of 
manuals, template or example files.
     + DONTs: I would never use this, say, for environment names or button names 
(find & replace, for instance).


If there was a way to browse all strings in the info inset dialog, with 
a search fields, it might be easier.



Some things to note:
   - When using info insets, spaces between words are normal, instead of 
non-breaking, which is the usual in the docs for menu names and the like.


Isn't it the opposite? It is the reason IMO why info insets are not used 
more in documentation, they do not break on screen and this does not 
look good. Having insets that can break on screen has been on some TODO 
list forever (so called three-parts-insets, or something like that). I 
think that I know how to do it, by using a mechanism similar to 
addToMathRow() for math insets with allows to linearize macros in 
equations. But I have no idea about when this could be implemented. And 
of course this creates practical issues about how to do it right (in 
terms of display mainly).



   - Not all references to menus are paired with a function in LyX, for instance 
File > Export.


We could add an info type "submenu", this wold not be difficult (but it 
is a format change, of course)



   - The actual language the info insets are displayed in is the UI's, not the 
document's. This is definitely a drawback for languages with limited 
translation support.


But these languages will have the same issue in the real UI, right? So 
it is faithful to what the user gets.



   - If a localized GUI string is not found or is not yet translated, it is 
displayed in English; therefore there is no danger of leaving blank text in 
place of info insets.


Right.

Thanks for investigating that.

JMarc

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

Re: Shortcuts.lyx and a problem with names of keys

[Jean-Marc Lasgouttes]

Le 27/08/2023 à 14:52, Jean-Marc Lasgouttes a écrit :

Le 27/08/2023 à 14:37, Dan a écrit :

EXPECTED BEHAVIOUR
---
Both PDF files should be exactly equal: changing the UI language 
should affect neither the output of the document, nor the displayed 
names of the keys in the LyX editor view.


Hello Dan,

This is on purpose, when considering that the user creates the 
documentation for his own use. Of course, one has to be careful when 
creating a documentation for general use.


It makes much sense for menu entries, but I understand how it may seem 
strange for key codes.


JMarc



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

Re: Shortcuts.lyx and a problem with names of keys

[Jean-Marc Lasgouttes]

Le 27/08/2023 à 14:37, Dan a écrit :

EXPECTED BEHAVIOUR
---
Both PDF files should be exactly equal: changing the UI language should affect 
neither the output of the document, nor the displayed names of the keys in the 
LyX editor view.


Hello Dan,

This is on purpose, when considering that the user creates the 
documentation for his own use. Of course, one has to be careful when 
creating a documentation for general use.


JMarc

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

Re: Out-of-date image in Intro.lyx

[Jean-Marc Lasgouttes]

Note that we plan to revert the change for now. Please don't change yet.
JMarc


Le 25 août 2023 15:29:42 GMT+02:00, Pavel Sanda  a écrit :
>On Wed, Aug 23, 2023 at 09:03:57PM +0200, Dan wrote:
>> Hello,
>> 
>> I have found an out-of-date image in the English version of Intro.lyx: the 
>> appearance of the footnotes in the Lyx editor view 
>> (https://www.lyx.org/trac/browser/lyxgit/lib/doc/Intro.lyx#L1048).Footnotes 
>> are no longer displayed like that 
>> (https://www.lyx.org/trac/browser/lyxgit/lib/doc/clipart/footnote.png) but 
>> rather as a superscript number in an inset.
>
>I am happy to commit the fix if you can prepare the patch
>Pavel
>-- 
>lyx-docs mailing list
>lyx-docs@lists.lyx.org
>http://lists.lyx.org/mailman/listinfo/lyx-docs
-- 
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Re: Documentation

[Jean-Marc Lasgouttes]

[Please keep Ronan in Cc:, he is not subscribed to the list]

Le 05/05/2022 à 15:05, Pavel Sanda a écrit :

On Thu, May 05, 2022 at 11:37:55AM +, Ronan Conroy wrote:

I???ve started learning to use LyX, and am impressed by it as a editor. 
However, as someone who has written documentation for software, I would like to 
point out a couple of things

  1.  Tutorial material is prolix. There is simply too much prose. Focus each 
paragraph on acquiring a definable skill, and use each skill to teach a useful 
concept. Focus on the skills that the person needs to get going.
  2.  Tutorial material is inaccurate as regards word processors. It describes 
making a list, for example, as the tedious process of numbering and indenting 
items. This has not been true of standard word processors (Libre Office, Pages, 
Word) for decades. Save space by leaving word processors out of the material. 
People are using LyX because they want a TeX interface. They have a word 
processor and know its limitations.
  3.  My first software documentation job was to take the manual for the word 
processor (DSR ??? a mainframe markup program running on an old Dec-20 
mainframe) and write an instruction manual that could be printed on one side of 
an A4 card. It was wildly successful. You need one of these.

The app is great. You just need people to write cheerful, lucid documentation. 
I itch to volunteer, but I???m already over-committed!


Dear Ronan, thanks for your feedback.

Let me introduce you to our situation :)
Currently we do not have any person actively working on our primary 
documentation or even 'overseeing' it.
That means when currently someone codes new feature he adds few paragraphs 
about its existence into some of the manuals and that's it.
And coders are usually not the best writers for general public, most of us are 
not even native english speakers...

Once in a decade someone pops up, says 'Hi guys, your manuals need editing 
work, I can review it for you.'
We include his fixes, send our thanks and then manuals rot for next couple 
years :)

So any help appreciated, whether fixes/rewrite our A4 cheat card, whatever 
you'd enjoy!

Cheers,
Pavel


I can only concur with Pavel, the manuals are kind of up to date, but 
there is no editorial vision anymore.


Documentation is one of our soar points, and we need someone who can 
improve it.


JMarc

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

[Important] New behavior for spam handling on this list

[Jean-Marc Lasgouttes]

Dear all,

Until now, the handling of the list was like: messages from subscribers 
go through, other  messages are put on hold, so that I had to have a 
look at all the moderated mails (~40 spams and sometimes a message) daily.


Now that I have been made aware (by the OSUOSL people) that there is 
actually a X-Spam-Flag header we can rely on, I am trying something new 
on this list:


- spams are automatically discarded; please notify the list if a message 
of yours just disappears. I have first tried this method on lyx-devel, 
and it seems to work there;

- members posts not qualified as spam go through as usual;
- remaining non-member posts are held for moderation.

Comments welcome.

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

Re: Text style menu entry

[Jean-Marc Lasgouttes]

Le 16/05/2021 à 23:06, JP a écrit :

Hello Jean-Marc

You may have seen that I restored the dynamic insets, as one can always  
run


$LC_ALL=C lyx

to create e.g. a manual to upload to the wiki.



Great!

As you can guess, I am trying to catch up and read messages out of order :)

JMarc

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

Re: Text style menu entry

[Jean-Marc Lasgouttes]

Le 14/05/2021 à 18:47, JP a écrit :

Why not? If the manual describes the French UI, isn't this what is
wanted?


Not in the English manual, I guess.


The manual adapts itself to the UI used by the user. If we produce PDF 
files to put in our web site, we have to be careful about such things, 
of course.


JMarc

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

Re: Help with Lyx file- Missing packages

[Jean-Marc Lasgouttes]

Le 12/01/2021 à 23:46, Kerry A. Bowman a écrit :

Dear Lyx Customer Service,


Dear Kerry,

First, I am sorry to admit that we do not have a customer service. The 
best you can do when you have issues like this one is to send a message 
to the lyx-us...@lists.lyx.org list, where other users (or developers) 
will be happy to assist.



I am having trouble viewing and saving the attached file in PDF form. When I go to 
view the file in PDF I get an error message about missing packages. I looked online 
and saw that in Document>Settings>Latex preamble, but it says to contact you 
here and not edit the preamble.


I am curious to know where you get this last information. I suspect that 
it is in the code of one of our manual, but it is unfortunate that it 
can be construed as general advice.


To go back to your problem, there is not much we can do to help unless 
you tell us what is your operating system and are the packages that are 
marked as missing.


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

Re: Help with Lyx file- Missing packages

[Jean-Marc Lasgouttes]

Le 12/01/2021 à 23:46, Kerry A. Bowman a écrit :

Dear Lyx Customer Service,


Dear Kerry,

First, I am sorry to admit that we do not have a customer service. The 
best you can do when you have issues like this one is to send a message 
to the lyx-us...@lists.lyx.org list, where other users (or developers) 
will be happy to assist.



I am having trouble viewing and saving the attached file in PDF form. When I go to 
view the file in PDF I get an error message about missing packages. I looked online 
and saw that in Document>Settings>Latex preamble, but it says to contact you 
here and not edit the preamble.


I am curious to know where you get this last information. I suspect that 
it is in the code of one of our manual, but it is unfortunate that it 
can be construed as general advice.


To go back to your problem, there is not much we can do to help unless 
you tell us what is your operating system and are the packages that are 
marked as missing.


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

Re: Lyx version in preparation

[Jean-Marc Lasgouttes]

Le 13/12/2020 à 17:39, Jean-Pierre Chrétien a écrit :

Dear all,

In

https://www.lyx.org/RoadMap

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


You are right. I changed it.

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

Re: Bug in LyX

[Jean-Marc Lasgouttes]

Le 04/11/2020 à 22:23, Rt Ecker a écrit :

Hello,

I have a bug in LyX and saw I'm supposed to notify you about it, can you 
please help?


Hello,

If you are positive that it is a bug, please report it at 
https://www.lyx.org/trac, our bug tracker.


Another possibility is to write the the users mailing list 
lyx-us...@lists.lyx.org. This list is about the LyX documentation.


Regards,
Jean-Marc
--
lyx-docs mailing list
lyx-docs@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-docs

Testing archives

[Jean-Marc Lasgouttes]

Just a quick message to see whether archiving works again.

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

Re: maybe a space

[Jean-Marc Lasgouttes]

Le 14/02/2019 à 01:32, Scott Kostyshak a écrit :

I think it serves two purposes:

  1. It keeps the entry in the table of contents short. With the full
  length entry, it looks slightly strange.

  2. For those who use PDF bookmarks, without the short title, the
  bookmarks tab takes up more space.

See the attached screenshot.


Sure, but having a table of contents entry different from the section 
title should be a last resort decision. It is disruptive to the reader.


We could also use the short title everywhere.

JMarc

Re: maybe a space

[Jean-Marc Lasgouttes]

Le 13/02/2019 à 02:59, Scott Kostyshak a écrit :

The correct fix is to remove the useless "short title" inset.


Do you mean remove the "\texorpdfstring"?


I do not see the point of the whole inset (with a different title). I 
tried to remove it and I do not see the problem that creates.


But yes, at least the handmade texorpdfstring should go. We should 
probably audit all uses of that in the docs and remove those that are 
not necessary anymore.


JMarc

Re: maybe a space

[Jean-Marc Lasgouttes]

Le 11/02/2019 à 03:19, Scott Kostyshak a écrit :

On Sat, Jan 05, 2019 at 03:14:34PM +, Meng, Li (mengle) wrote:

Hello,


Good morning!

Maybe there should be a space in the red rectangle. This is the introduction 
PDF file in LYX.


Good morning (a month later) :)

Thanks for this report, Li Meng. I can reproduce here. I'm not sure what
is wrong with our LaTeX code:

   \subsection[\texorpdfstring{\protect\LyX}{LyX} and Other Word 
Processors]{Differences between \protect\LyX{} and Other Word Processors}

Making the space a protected space fixes the problem, but I'm guessing
there's a more LaTeX-correct fix. I'll wait to see if someone knows the
correct fix, otherwise I'll add the protected space.


The correct fix is to remove the useless "short title" inset. It may 
have been useful when the \LyX command was not suitable for PDF, but now 
it only causes problems IMO.


JMarc

Re: Introduction to LYX - suggested revision

[Jean-Marc Lasgouttes]

Le 09/06/2018 à 04:45, Scott Kostyshak a écrit :

I have copied your first paragraph in section 1.1, but used the Standard
English 'mother' rather than the US vernacular 'mom'. LYX is a product for
many nations, so Standard English is preferred for the English version. The
other sections and paragraphs are my own.


Did anyone take a look at this?


As with many documentation suggestions, nothing happened. I read the 
text at the time, and I was not sure at the time that I liked it. 
However, writing documentation in English is not something that I am 
comfortable with.


JMarc

Re: Sweave homepage does not exist anymore (remove URL?)

[Jean-Marc Lasgouttes]

Le 06/10/2017 à 07:57, Scott Kostyshak a écrit :

I propose to change

 The homepage of Sweave is at
 http://www.stat.uni-muenchen.de/~leisch/Sweave/

to

 The Sweave user manual is at
 https://stat.ethz.ch/R-manual/R-devel/library/utils/doc/Sweave.pdf

Go ahead.

JMarc

Re: LyX Tutorial, LyX settings

[Jean-Marc Lasgouttes]

Le 06/07/2016 à 15:58, Richard Heck a écrit :

·Any chance of LyX to allow **import** of Jupyter notebooks? Here,
I’m referring to “static” import?

·Any chance of LyX supporting **live** Jupyter notebooks?


No clue about this one.


Me, either, but if it is possible that these can be handled via
"external templates".
See secion 6 of the Customization manual (under Help).


Or maybe using literate programming support like we do for Sweave.

JMarc

Re: Translations for 2.1.5

[Jean-Marc Lasgouttes]

Le 26/05/2016 à 11:19, Jean-Pierre Chrétien a écrit :

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


It is hamless (and fixed in 2.2). We did not backport the fix to 2.1 at 
the time.


JMarc

Re: mailing-list policy

[Jean-Marc Lasgouttes]

Le 18/05/2016 à 18:26, mn a écrit :

Every mail (with attachments) in the last few days I sent to the docs-
and devel-mailinglists was bounced.

The message always said:
SMTP error from remote server for TEXT command, host: thales.memphis.edu
(141.225.8.55) reason: 554 This message contains prohibited content

This error message is – maybe misleading?
There was no illegal stuff nor any profanity I could detect in the
bounced mails.

Since I didn’t find any offical statement on the policy regarding
attachment types, their size or contents for the mailing list:

What is the policy on this here?
Why did I get those bounces?
Can you please clarify this 554 in the future?
Please make the policy on this more visible, easier to find.

If it is a problem with the size of the attachments (simply a zipped
lyx-doc, less than 50K) please increase the size of allowed attachments.


The list maintainer is at a conference until next week, but he will 
check what policy is in place when he returns. It might be that we 
decided at some time that zip files were bad. You could just send a lyx 
file when you need it.


JMarc

Re: mailing-list policy

[Jean-Marc Lasgouttes]

Le 18/05/2016 à 18:26, mn a écrit :

Every mail (with attachments) in the last few days I sent to the docs-
and devel-mailinglists was bounced.

The message always said:
SMTP error from remote server for TEXT command, host: thales.memphis.edu
(141.225.8.55) reason: 554 This message contains prohibited content


Hi,

Could you forward this message (with all headers) to me?

JMarc

Re: de-UserGuide improvements

[Jean-Marc Lasgouttes]

Le 29/04/2016 à 17:05, mn a écrit :

This refers primarily but not exclusively to German Userguide.


I cannot comment on this one unfortunately. Mn, please feel free to open 
a bug report on www.lyx.org/trac about the quotes.


JMarc


In this section 3.9.3 the usage of the "-sign differs from the rest of
the doc insofar as it is not enclosed in quotation marks.

It would be nice if there were some hints as to which languages usually
prescribe which style.
The first line of examples gives a wrong quotation mark after doppelt
(sic!: ”doppelt”)

The shortcut for creating a single quotation mark in LyX cannot be as
universal as the wording implies.
And it does not use the "-sign!
On Mac with German-keyboard-layout the given shortcut Opt-" gives a
correct closing-double quotation mark
\textquotedblleft{} (“) and LyX does not transform this in any way to
opening or closing single quotation marks.
Since the Shift is only implied this is also a bug imho, since in the
menus it says ^+"
So this would be more correct to read ideally Ctrl-Shift-2, or
Ctrl-Shift-", or ^- – but not Alt/Opt-something.

% IMHO, usage of quotation marks is inconsistent over all.
% Some times they are there, some times not.
% I would try to get rid of them in most cases.

However, in the attached file only clearly incorrect marks should have
been replaced.
When there were single q-marks that are on the same logical level as the
double-marks otherwise, those have been replaced.
Several wrong en-dashes have been replaced.
The constant usage of LyX' was redone to read LyX’.
Since the document already had some ligature breaks, 42 new ones are added.
Also, some of the worst offenders in margin violations should be attenuated.
For example, 6.5.6 causes some headaches still
\addto\captionsngerman{\renewcommand{\indexname}{Stich\-wort\-ver\-zeich\-nis}}

mn

Re: en UserGuide.lyx: quotation marks, ellipses, spelling and dashes

[Jean-Marc Lasgouttes]

Le 27/04/2016 à 18:54, mn a écrit :

Some minor corrections to the usage of dots, single- and double
quotation marks, and dashes. One grammar/spelling/typo.


These should go in too. Uwe?

JMarc

Re: improving typography and layout in tutorial.lyx

[Jean-Marc Lasgouttes]

1. There are a few minor typographical problems – catched with (builtin)
chktex.
En-dashes, footnote-spacing, excess space(~).

These are hopefully improved upon in the attached .lyx-file.


Uwe, do you intend to take these changes into account? I think it is 
important to adhere to good typography principles in our docs. I can 
apply the changes if you do not have time to look after it. It is better 
to do it right now than to let the documents bitrot.



(From the existing I deduced that the desired behavior was to conform to
Bringhurst‘s guide: endash surrounded with spaces.)


2. Then there are problems with lines running into the margin:

These are the following: occuring with default a4-papersize.

– Exercise: Fix the section and subsection headings in example_raw.lyx.

– Exercise: Correctly typeset the Quote, LYX-Code, and Verse in
example_raw.lyx


All the Exercise entries could read "in example_raw.lyx, do this and 
that". That would solve these problems.



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


This is from 3.4.2. We should either break the line by ourselves or use 
a Quote environment instead of LyX-Code. This line going in the margin 
is ridiculous.




These I did not try to fix in the attached file since I didn’t find
something like a style-guide for LyX-documentation.

3. In section 3.2 designating paragraphs deviates (only optically?) from
the rest of the document in apparently using indention and skips.
For my own documents I would insert a pagebreak there.


Mn, I do not see what you mean here.

Uwe, please let me know if you plan to handle these changes or if I 
should do them.


JMarc

Re: improving typography and layout in tutorial.lyx

[Jean-Marc Lasgouttes]

Le 21/04/2016 18:03, mn a écrit :

My current understanding is that maybe you mistook my issues for
something they were not intended to be? I offered a kind of proof-reading.

The issue I raised called “2.” points to a commmon problem in several
LyX-documentation-docs, not only tutorial(en):
Lines running into the margin.
This is really bad, both optically and as an example. Of course,
guessing that it is not meant as one of multiple examples of what can go
wrong, when you start using LaTeX/LyX!


I wholeheartedly agree with you. Our manuals should be a showcase for 
LyX and how to use it correctly.


I did not have time to look at your changes, but I think something has 
to be done.


JMarc

Re: Lyx v2.1.4 Voluntary Product Accessibilty Template (VPAT)

[Jean-Marc Lasgouttes]

Le 25/02/2016 16:45, Yellin, Gary a écrit :

Good morning,

I am trying to determine if Lyx has a VPAT on file identifying an issues
which relate the US federal guidelines regarding 508 compliance, which
is having software be accessible by people with disabilities (e.g.;
visual impairments).


Dear Gary,

Unfortunately, there is never been any serious work related to 
accessibility in LyX. Since our work area is drawn with custom, there is 
little hope to make it work with a screen reader, for example. That 
would be an interesting project, but we have never been approached about 
that.


Best regards,
JMarc

Re: Updated pt_BR.po (Brazilian Portuguese) translation for 2.1.5

[Jean-Marc Lasgouttes]

Le 13/09/15 17:02, Uwe Stöhr a écrit :

There is a bug in newer IM versions so that PDF images are not displayed
within LyX. I reported this several times but the IM people did not
reply. The problem is that IM doesn't have a bug tracker and if the
devels don't have time after one reported a bug, nothing will be done
later on.


Did you try graphicsmagick instead? It is a fork that is supposed to be 
better.


JMarc

Re: AW: splash.lyx

[Jean-Marc Lasgouttes]

Le 12/02/15 20:00, Uwe Stöhr a écrit :


Von: Jean-Marc Lasgouttes
Gesendet: Donnerstag, 12. Februar 2015 10:08‎


Using an info inset would solve the problem in a more elegant way, I guess.


The policy is not ro use any special LyX inset in the splash file because it is 
designed for absolute newbies‎. They don't know anything about LyX and the very 
special inset info only raises questions we can't answer for newbies.

The same applies for the intro manual.


The icon used there is an info inset...

JMarc

Re: splash.lyx

[Jean-Marc Lasgouttes]

Le 12/02/15 09:51, Jean-Pierre Chrétien a écrit :

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.


Using an info inset would solve the problem in a more elegant way, I guess.

JMarc

Re: your Lyx introduction

[Jean-Marc Lasgouttes]

07/05/2014 05:17, Barry Brent:

Hi—

I downloaded your manual "Introduction to Lyx” (dated July, 18, 2006)
from URL http://wiki.lyx.org/LyX/Manuals today. (The file name was
“intro.pdf”.)

Is there a more recent version?

Near the end of section 2.2 of the 2006 version, you say:

"LATEX configuration

LYX investigates your system upon installation. This file contains info
on what LYX learned about your installation. Check it to see if you’re
missing something you might like to have. "

But I can’t tell how to find this LaTeX configuration file.


Hello,

As Siegfried mentioned, you should really use the Help menu. And we 
should update the documentation on our web site :)


JMarc

Re: Translations of Math environments in LyX output for LyX 2.1

[Jean-Marc Lasgouttes]

11/04/2014 10:48, Vincent van Ravesteijn:

Well, it might also be that the exception is French, because the word
"Tableau" loses its distinct meaning that it has in English.


Yes, but you are supposed to pronounce it with the accent of an English 
speaker uttering a French word.


JMarc

Re: Typos in Customization.lyx

[Jean-Marc Lasgouttes]

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)

JMarc

Re: [PATCH] Fix a few typos in French docs

[Jean-Marc Lasgouttes]

06/04/2013 23:18, Scott Kostyshak:

Ah I see what you mean. That makes sense but since neither of us seems
too confident, I'll wait to see if a native French speaker comes
along. If not, I think I'll commit the original patch since it at
least corrects the discordance of singular/plural without trying to do
anything more.


What about "Ces archives sont en fait au format zip" ?

JMarc

Re: LyX 2.0.1 Wednesday

[Jean-Marc Lasgouttes]

On mar. 14 juin 2011 15:11:23 CEST, Richard Heck wrote:
I intend to build and tag LyX 2.0.1 on Wednesday---or at least try to do 
so, as it will be my first time. (Pavel, Jurgen, please check your 
email!) So if you have anything you'd like included, please say so now.


I have small changes for sweave to backport (and yes I know you allowed 
mne to do so).


It is a pity that I did not manage to solve more problems in time...

JMarc

Re: \spce macro in user guide

[Jean-Marc Lasgouttes]

Le 10 nov. 10 à 17:53, Uwe Stöhr a écrit :
Yes, because there is no version of a serif font and typewriter font  
that can display the character. So even when using Arial Unicode MS,  
the character would disappear when setting ti as roman or typewriter  
font.


The right thing to do is to add a new "visible space" type to  
InsetSpace. I would be quite easy.


These \spce macro look bad when reading the manual in LyX.

JMarc

Re: \spce macro in user guide

[Jean-Marc Lasgouttes]

Le 10/11/2010 17:09, Uwe Stöhr a écrit :

Maybe Arial Unicode MS is standard with Win 7, but I still use XP and
have the same problems with Vista.


I read that it comes with office.

Anyway, the idea does not work...

JMarc

Re: \spce macro in user guide

[Jean-Marc Lasgouttes]

Le 10/11/2010 05:03, Uwe Stöhr a écrit :

I checked that and the problem is that one can insert this character but
it cannot be displayed with the fonts available on Windows. We are there
using by default the fonts Times Nwe Roman, Arial and Courier New. None
of these fonts include the \textvisiblespace character. I had a closer
look and none of the fonts available by default on Windows can display it.


Hmm, bad microsoft. But do these fonts have any interesting unicode 
character? I read that Arial Unicode MS is the version that contains the 
interesting characters (distributed with office).


Since you were able to select the right character, it seems that you 
used a font that contained it (in the dialog). Which font is that. Isn't 
it trebuchet?


JMarc

\spce macro in user guide

[Jean-Marc Lasgouttes]

Uwe,

Now that we do utf8, it seems to me that the correct character can be  
directly
used in the document instead of the own-grown \spce macro. I tried it  
out
and it seems to work, but since you may have other reasons I do not  
want to

step on your toes.

JMarc

Re: xypic.lyx in French update

[Jean-Marc Lasgouttes]

Le 27/11/2009 03:58, Uwe Stöhr a écrit :

One tip: When you need to use a multiplication sign like in "3x3"
matrix, you can insert it via the menu Insert->Special
Character->Symbols. I therefore replaced the formula with this sign in
your file.


I am not sure I understand what the gain is. I thought it was advised in 
general to put numbers in math formulas anyway. A typical example is
when text uses oldstyle numerals. Most of the time, one would not want 
this 3x3 to use it...


JMarc

Re: French translation of the web site

[Jean-Marc Lasgouttes]

Jean-Pierre Chrétien  writes:
> The translation is quite complete and up to date, thanks to Siegfried
> and Alain:
> http://www.lyx.org/SiteTranslation#toc5

Congratulations!

> Is there a way to display the French pages if the browser is
> French-speaking ?

I have proposed this in the past, but Christian was not sure he wanted
it. I still think we should (at least for languages that are considered
to be complete enough)

JMarc

Re: HowToUseSVN LyX web site page - autogen issue

[Jean-Marc Lasgouttes]

Uwe Stöhr  writes:

> Jean-Pierre Chrétien schrieb:
>
>> In HowToUseSVN, I find these lines unclear, and in fact dangerous
>
> This needs to be discussed on the lyx-devel list. I'm forwarding this
> email to this list:

The new text makes sense to me. It should additionally be pointed out
that LyX can be run without installation (but then the l10n will be
wrong).

JMarc

Re: Cosmetic problem of CJK po files for Mac OS X

[Jean-Marc Lasgouttes]

> Thank you for your suggestion. If it is possible to set up such an
> automated procedure, it would be nicer because when a writer
> translates, say, ja-mac.po, he would have to rely on sed or
> something,
> anyway.

What I had in mind is a simple way to generate the menu entry for windows and
linux: the menu entry in the menu definition has 2 parts (label and shortcut).
Example "File|F" yields "File" and "F".

We could have a special string that can be translated for each language telling 
how to make the menu entry, like:

* for non CJK "%s"
* for CJK "%s (%s)"

The string would be used printf-style with two arguments which are the label and
the shortcut. This means that CJK translators would have to change a single
translation to have this effect on all manu entries.

Would this scheme cover the different formats you have described in the rest of
your message?

JMarc

Re: Cosmetic problem of CJK po files for Mac OS X

[Jean-Marc Lasgouttes]

Le 21 juin 09 à 18:53, KYokota a écrit :

At compile time, the underline for the menu accelerator in Latin menus
is automatically removed for Mac, but the above problem is not
automatically handled for, at least, CJK languages.

So, for example, is it possible to use independent po files for Mac to
solve this problem? I.e., setting up ja-mac.po file for Japanese in
Mac instead of ordinary ja.po file? Or can there be other solutions?


Hello,

I did not answer yet, because I am still searching for a good idea :)
I do not think that having a separate ja-mac translation is a good idea,
because it would mean more work. OTOH, we could imagine that the  
string in

parenthesis is generated by LyX from the shortcut only in cjk-like
environments. I think I can come up with some regexp-based solution.

JMarc

Re: LyX Web site

[Jean-Marc Lasgouttes]

Le 28/04/2009 20:13, Jean-Pierre Chrétien a écrit :

Hello,

I recently begun the translation of the site to French, and I have a
suggestion: use &mdash instead of -- wherever it happens (currently I
found some in http://www.lyx.org/WhatIsLyX ).


It seems that pmwiki can have automatic support for that.

Christian?

JMarc

Re: once upon a time a fully translated LyX...

[Jean-Marc Lasgouttes]

Ignacio García  writes:
> I mean some shorcuts in Shortcuts.lyx.
> I don't understand well: is it a bug? As you said on Jan, 6
> (http://mail.google.com/mail/h/1ifwk297wx2b7/?v=c&th=11eaa04f4688af08)
> the InsetInfo insets used in Shorcuts are only for developpers
> and they are no translatables.

There are two different issues: the language of the inset wrt lyx (which
is a minor bug) and the translation of things like Shift or Ctrl, which
we should fix. On what platform are you working (Mac, Windows, Linux)?

JMarc

Re: Part of "Translation" web page needs update

[Jean-Marc Lasgouttes]

Christian Ridderström  writes:
> It looks good to me, but this is more Uwe's area, so I'll let him
> judge. To make it easer for him, here's the new text (on line 36):

Looks good to me.

JMarc

Re: Rectification manuel lyx =)

[Jean-Marc Lasgouttes]

Le 28 déc. 08 à 13:01, Sophie Lefebvre a écrit :

bonjour


Bonjour,

Je réponds tout de suite, avant qu'un anglophone ne fasse remarquer  
qu'il faut écrire en

anglais sur cette liste :)

Il semble qu'il y a eu en effet un changement de correction du mot  
"foot" (pour footnote, note de
bas de page). C'est vrai qu'il est un peu difficile de trouver une  
bonne traduction.


Je mets la liste lyx-fr en copie pour voir si un consensus émerge...

JMarc



je commence aujourd'hui à m'initier à LyX, merci de votre manuel hyper
détaillé et précis
je me permets de vous envoyer cette info, concernant une erreur qui  
a bien

failli me décourager

dans l'intro (doc/fr/Intro.lyx) le contenu de la boîte grise "pied  
12" fait
référence à une boîte grise qui contient le mot "bas", que j'ai  
cherché en
vain, puisque, à l'aide de mon cher fiston, j'ai découvert qu'il  
s'agissait

en fait du mot "pied"

j'ai découvert aussi que je me décourageais très  facilement :)))

je retourne à mon exploration de ces terres bien pire qu'inconnues,  
puisque
connues du temps de ma jeunesse étudiante quand j'ai rédigé ma  
thèse en
1991, avec le merveilleux LateX, mais sans WYSIWIG à l'époque, ce  
qui m'a

laissé un souvenir un peu traumatisant...
depuis je me suis empressée de tout oublier, entre l'enseignement  
et les

enfants, les soucis de la vie d'adulte... ça aide
et maintenant, je veux reprendre en main cet outil merveilleux,  
d'autant que

WYSIWYM!!!

encore merci, et mes excuses pour ce long mail qui est aussi un  
moyen de

jouer la montre, honte à moi :((

Re: [PATCH] Re: specific help menu entry

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller  writes:

> Jean-Marc Lasgouttes wrote:
>> Branch too?
>
> Yes, please.

Done.

JMarc

Re: [PATCH] Re: specific help menu entry

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller  writes:

> Jean-Marc Lasgouttes wrote:
>> > I think I'd prefer the latter.
>>
>> Like that?
>
> Yes, this looks good. Put it in if it works.

Yes it works. Branch too?

JMarc

[PATCH] Re: specific help menu entry

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller  writes:
> Pavel Sanda wrote:
>> this is because specific manuals are in examples directory.
>> two ways how to fix it:
>> 1. move those files into doc directory. the distinction between examples
>>    or manuals is unclear in those cases.
>> 2. enhance the way how help-open lfun works, ie enhance searching
>>    of system directories.
>
> I think I'd prefer the latter.

Like that?

JMarc

svndiff src/LyXFunc.cpp lib/ui/

Index: src/LyXFunc.cpp
===
--- src/LyXFunc.cpp	(revision 27857)
+++ src/LyXFunc.cpp	(working copy)
@@ -1034,7 +1034,10 @@ void LyXFunc::dispatch(FuncRequest const
 setErrorMessage(from_utf8(N_("Missing argument")));
 break;
 			}
-			FileName const fname = i18nLibFileSearch("doc", arg, "lyx");
+			FileName fname = i18nLibFileSearch("doc", arg, "lyx");
+			if (fname.empty()) 
+fname = i18nLibFileSearch("examples", arg, "lyx");
+
 			if (fname.empty()) {
 lyxerr << "LyX: unable to find documentation file `"
 			 << arg << "'. Bad installation?" << endl;
Index: lib/ui/stdmenus.inc
===
--- lib/ui/stdmenus.inc	(revision 27857)
+++ lib/ui/stdmenus.inc	(working copy)
@@ -532,10 +532,10 @@ Menuset
 	End
 
 	Menu "examples"
-		Item "Linguistics Manual|L" "help-open ../examples/linguistics.lyx"
-		Item "Braille Manual|B" "help-open ../examples/Braille.lyx"
-		Item "XY-pic Manual|X" "help-open ../examples/xypic.lyx"
-		Item "Multicolumn Manual|M" "help-open ../examples/multicol.lyx"
+		Item "Linguistics Manual|L" "help-open linguistics"
+		Item "Braille Manual|B" "help-open Braille"
+		Item "XY-pic Manual|X" "help-open xypic"
+		Item "Multicolumn Manual|M" "help-open multicol"
 	End
 
 

Re: specific help menu entry

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller  writes:

> Pavel Sanda wrote:
>> > This is probably a bug.
>>
>> this is because specific manuals are in examples directory.
>> two ways how to fix it:
>> 1. move those files into doc directory. the distinction between examples
>>    or manuals is unclear in those cases.
>> 2. enhance the way how help-open lfun works, ie enhance searching
>>    of system directories.
>
> I think I'd prefer the latter.

Yes, I think help-open should first look in doc/ and then in examples/.

JMarc

Re: fr.po for 1.6.0

[Jean-Marc Lasgouttes]

Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes:

> I've seen Jûrgen's message about 1.5.7.
> Here is an updated version of fr.po for branch.

Thanks, it is in.

> I need a little more time to backport my review of 1.6.0 messages
> in 1.5.7, when will the release of 1.5.7 take place ?

Not sure.


> I have also a slight problem with the translation of
> "Extended features": seems to me the the name of this manual
> has changed  to "Additional features" in 1.6.0 (I changed the French
> translation from "Options avancées" to "Fonctionnalités
> supplémentaires").
> But I still see the "Extended features" message in the 1.6.0 pot file.
> Maybe it would be better to stick to "Options avancées" for
> "Additional features" (as the title of the manuel).

I do not know about that either, therefore I cc to lyx-docs.

JMarc

Re: Typo in Math.lyx

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

>> In this case, it should be \Bra{\psi
>
> Why? \Bra{\psi is all you need. To type in more to the formula you can
> use the arrow keys, space, or the mouse. But this is independent from
> the example.

This spreads the idea that there is no need to close a group and that
LyX/TeX can do it by magic. Of course this is wrong, since TeX needs }
and LyX needs cursor movement to go out of the group. In some sense,
\Bra\psi would be a more faithful example.

I am not going to argue this farther though.

JMarc

Re: Typo in Math.lyx

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> Jean-Marc Lasgouttes schrieb:
>
>> In section 22.4 (physical vectors) of Math.lyx, I see examples like
>> "\Bra{\psi". Why is the final "}" missing?
>
> It is not missing. Type exactly the command and you can see that it is
> correct. (LyX automatically adds the closing brace).

So this text is supposed to reflect what the user types, rather that
what gets entered into LyX, right? In this case, it should be
\Bra{\psi

JMarc

Typo in Math.lyx

[Jean-Marc Lasgouttes]

In section 22.4 (physical vectors) of Math.lyx, I see examples like
"\Bra{\psi". Why is the final "}" missing?

JMarc

Re: incorporating PSTricks

[Jean-Marc Lasgouttes]

Le 15 août 08 à 17:27, Christian Ridderström a écrit :
Don't worry about contacting me or the documenatation list, but  
could you tell me exactly where you saw this?  We should probably  
correct that piece of documentation to more clearly point to the  
user's list.


I think this mention is in qll the preambles of the documentation  
files. I am not sure what

it is intended to mean, though :)

JMarc

Re: Approaching LyX 1.5.6

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:

> There are no critical issues left anymore (at least no reproducable ones), 
> except for this (patch from Jean-Marc exists and should go in): 
> http://bugzilla.lyx.org/show_bug.cgi?id=4662

I think I fixed it after all. This is only in branch, trunk will have
to wait a bit.

BTW Juergen, after releasing 1.5.6, make sure to close only bugs that
are also fixed in trunk (I guess most are).

JMarc

Re: translate to arabic

[Jean-Marc Lasgouttes]

hatim ali <[EMAIL PROTECTED]> writes:

> Dear lyx team
> thanks for your best latex program.
> i want to translate "lyx" to arabic language but i don't know if there are 
> any translation to arabic Previously.
> and where can i get ar.po or en.po to used it in the translation.

Hello,

We do not have an arabic translation up to now, and it would be a
great thing...

As far as I know, there is no current translation to arabic. Since
this is a fresh start, I would consider starting from the 1.6.0svn po
file (1.6.0 is expected for the end of the summer. Depending on your
environment, we can either provide an empty template, or you could
download the upcoming lyx1.6.0beta4, or just get access to our svn
repository.

What is the best for you?

JMarc

Re: chktex in UserGuide.lyx

[Jean-Marc Lasgouttes]

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:

> It is not a greyed out menu, it is set to disappear. I guess the
> userguide needs to be updated.

Or rather the extended manual.

JMarc

Re: chktex in UserGuide.lyx

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

> No, I don't. However, the Extended Feature manual says there should be
> a grayed-out menu, but I cannot see such a thing.
>
> Will it appear once I install chktex?

It is not a greyed out menu, it is set to disappear. I guess the
userguide needs to be updated.

JMarc

Re: chktex in UserGuide.lyx

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

> Hi,
>
> Section 3.8.3.1 of the User Guide says there should be Tools -> Check
> TeX function, but I could not find it anywhere in 1.6svn.
>
> Has it moved anywhere?

Do you have the chktex program installed on your system?

JMarc

Re: patch for ro.po rev25242

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> Jean-Marc Lasgouttes schrieb:
>
>> OK, the new state of things is:
>> /etc/aliases:po-updates:lasgouttes,uwestoehr,spitz
>
> So I get emails sent to po-updates-at-lists.lyx.org forwarded to my web.de 
> email address?

No, all the emails sent to po-updates-at-lyx.org get forwarded to your
lyx.org email address. Is that OK?

> I've done this the last months, but the best would be when we 4 get
> these emails, and the one who is the first having time commits it.
> Then we have redundance when some of us in vacation or whatever.

We can do that an we'll see.

JMarc

Re: patch for ro.po rev25242

[Jean-Marc Lasgouttes]

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:

> [EMAIL PROTECTED] wrote:
>> I was referring to you actually. But I can add pavel too if needed. My
>> idea was to have few people here: Juergen, so that he knows what
>> happens, one person who is supposed to do the job (can be you if you
>> like), and another one as backup in case the first one is away (can be
>> pavel or me or...). If we have too many people there, we are going to
>> step on each other's toes.
>
> Yes, please add me, if only for information purposes.

OK, the new state of things is:
/etc/aliases:po-updates:lasgouttes,uwestoehr,spitz

Uwe, do you want to be the primary po file committer? Otherwise Pavel
could maybe do it.

JMarc

Re: patch for ro.po rev25242

[Jean-Marc Lasgouttes]

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:

>>>To: lyx-docs@lists.lyx.org
>>>Subject: Re: patch for ro.po rev25242
>>>From: Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
>>>Date: Thu, 03 Jul 2008 09:59:11 +0200
> [...]
>>>2/ send (as we have done in the past) a message to all translators
>>>before each release.
>
> That's OK for me.
> BTW, when is planned the next event (beta or rc).
> July 1st, 2008 is behind us.

I have no idea.

JMarc

Re: patch for ro.po rev25242

[Jean-Marc Lasgouttes]

Pavel Sanda <[EMAIL PROTECTED]> writes:

>> >not easily. next time it would be the best to post the whole ro.po file to 
>> >[EMAIL PROTECTED] .
>> 
>> Huh, I've never heard of that email adress.
>
> i used that address regularly, we have it also in our README.localisation.
>
>> How can I read messages sent to this adress?
>
> its under JMarc's control.

Hmm, yes, and I have been lazy about adding the relevant people
there... But I duly apply everything that arrives. 

Currently, we have:
/etc/aliases:po-updates:larsbj,lasgouttes,schmitt

I can remove lars and michael, and add juergen and yourself instead.

>> I additionally prefer when people send a message about po updates to the 
>> lyx-docs list because then every translator is remembered to update his 
>> translations for e.g. new releases and all developers notice that there is 
>> an update available.

I am not sure it is so useful. The idea of the list was to avoid
sending big things to public lists. If we want to remind translators
we shall either:

1/ make sure that all translators are subscribed to lyx-docs and post
there.

or

2/ send (as we have done in the past) a message to all translators
before each release.

JMarc

Re: First five minutes with Lyx....

[Jean-Marc Lasgouttes]

"Dr Dave" <[EMAIL PROTECTED]> writes:

> I am not on a Lyx-bashing spree here, but simply giving you my thoughts as a
> first-time user who has relevant background and experience in industry as
> well as science and technology.

Very good.

>  I expected this introductory document to be a finely-honed work of
> perfection with the purpose of not only aiding the new user in becoming
> familiar with Lyx, but to convince him of the correctness of choosing Lyx.

The Intro is certainly not perfect. Did you read the Tutorial too?

> My first "bad experience" with Lyx was the inability to display matching
> "double quotes", as the colloquial jargon calls them. You can see on the
> attached IMG01 that a different character is being used for the opening and
> closing quotation symbols; really, I would not expect to see such a faux pas
> in either the document or the Lyx application at less than five minutes
> out-of-the-box.

Last time I checked, quotes in English language were not symmetrical
(as in most languages, actually). 

> In addition, for whatever reason, I see inconsistent indentation behavior
> for Standard style. For example, the first Standard paragraph following a
> Subsection is flush-left, but each subsequent Standard paragraph is indented
> 5 spaces. What kind of style convention is that? How can a "set style"
> possibly be allowed to have two different behaviors?

This is a feature of the particular document class (the standard LaTeX
one). Other classes make different typographical choices. 

> And, how about missing characters (or maybe it is a character that should be
> removed)? I see a closing parenthesis with no opening parenthesis. Take a
> look at Section 2 Navigating the Document, second paragraph, the last
> character.

Well spotted.

> Also, I found it rather odd to have footnotes marked with red text "foot" on
> a grey background. I rather would have expected to see numerals, or at least
> a numeral along with the text. I can see the utility if the document is
> intended for electronic viewing and navigation, but not if it is to be
> printed. I suspect that at print time the footnote references are converted
> to numerals; I did not check that at this point.

This is implemented in forthcoming version 1.6.0. However, not
everybody thinks that we should do that.

> You try to make the case of the user applying character-based manual
> formatting to a document, I suspect because that is indeed what an
> *untrained* user tends to do. But, as the Lyx documentation makes
> clear, *training *is a must for using Lyx.

My view is that word makes is easy to do "finger-painting" and
possible to do correct style-based formatting. LyX tries to do the
opposite.

Thanks for your comments.

JMarc

Re: Language switcher for po files has gone?

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

> Jean-Marc Lasgouttes wrote:
>> It is in the code as far as I can see.
>
> Yes, indeed. As some strings in dialogs and menus are also not
> extracted to the pot file, something may have gone wrong in extracting
> strings.

Check whether you have an empty po/POTFILES.in. If you do, remove it.

JMarc

Re: Typo in GuiApplication.cpp

[Jean-Marc Lasgouttes]

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:

> Hello,
>
> As the subject says

Thanks, fixed.

JMarc

Re: Language switcher for po files has gone?

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

> Jean-Marc Lasgouttes wrote:
>> It is in the code as far as I can see.
>
> Yes, indeed. As some strings in dialogs and menus are also not
> extracted to the pot file, something may have gone wrong in extracting
> strings.

Note that I have made changes in this dept recently... I'll have a
look tomorrow.

JMarc

Re: Language switcher for po files has gone?

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:
> It seems the above entry is somehow not present in the current SVN's
> .pot file, so Help files don't switch to the current language.

It is in the code as far as I can see.

JMarc

Re: Untranslateble messages in interface

[Jean-Marc Lasgouttes]

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:

> I mixed versions prefixes, all is right with the last svn version,
> "New Line"/"Line Break" have been replaced by "Ragged/Justified Line Break".

OK, fine.

JMarc

Re: Untranslateble messages in interface

[Jean-Marc Lasgouttes]

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:

> In fact, compiling/installing lyx-1.6.0svn leads to this:
>
> Menu warning: menu entries "New Line|e" and "Espace Insécable|E" share the 
> same 
> shortcut 

I cannot reproduce this problem. Do you have menu definition files in
your .lyx/ directory?

JMarc

Re: Untranslateble messages in interface

[Jean-Marc Lasgouttes]

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes:
> Seems that 
>
> New Line|e
> Line Break|B
>
> became obsolete in trunk, so they can't be translated any more...
> There may be others, I didn't check.

What do you mean? Why is this a problem?

JMarc

Re: [doc] New translation to Japanese: Intro.lyx

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

 And also, Help menu doesn't seem to display the localized version
 even if locale is ja. I have no idea to correct this. Can this be
 fixed as well?
   

The bug is fixed in the version of ja.po I just committed. The
relevant line is:

#: src/support/filetools.cpp:247
msgid "[[Replace with the code of your language]]"
msgstr "ja"

This entry of ja.po is used by LyX to know what is the language used
by the interface. By adding the "ja" as msgstr, I have allowed LyX to
search for the right documentation.

JMarc

Re: Customization Manual

[Jean-Marc Lasgouttes]

rgheck <[EMAIL PROTECTED]> writes:

> 2. I've dramatically shortened and simplified the External Material
> section. Much of this was no longer needed because of the Embedded
> Objects manual. What's left are the parts that talk about how to
> define your own templates. (Is this stuff much used now?)

Yes, I think there are many power users who make clever uses of this
mechanism.

JMarc

Re: list request

[Jean-Marc Lasgouttes]

Pavel Sanda <[EMAIL PROTECTED]> writes:

> hi,
>
> who is the admin of lyx-doc list?  any time i send something i got two spams
> from conexol domain, about nonexisting addresses. seems conexol admins never
> listened about the difference between envelope From and header From: .
>
> anyway could some admin remove Celeb at conexcol.com & mbare at conexcol.com
> from the list?

What you get is not spam, just error message because the users do not
exist any more.

JMarc

Re: list request

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> Pavel Sanda schrieb:
>
>> who is the admin of lyx-doc list?
>
> Matej Cepl (have a look in the archives for his recent Email adress)

Almost. Mate Wierdl. Th standard address is
[EMAIL PROTECTED] I'll send you privately a direct address
to reach him efficiently.

JMarc

Re: Approaching LyX 1.5.3 [status update #3]

[Jean-Marc Lasgouttes]

[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:

> Developers, please let me know if you have pending patches;

I have the two following patches in my tree.

- last.diff is just documenting the fact that last files are not kept
  when upgrading (forgot the bug number)

- here.diff fixes the case where Here placement of floats s required
  only at global level see report:
   http://article.gmane.org/gmane.editors.lyx.general/42994
  the only potential problem is that float.sty is now loaded later
  than it was.

JMarc

svndiff UPGRADING

Index: UPGRADING
===
--- UPGRADING	(revision 22043)
+++ UPGRADING	(working copy)
@@ -12,6 +12,9 @@ able to read old preferences files, but 
 format, so it is not possible to run LyX 1.4.x and 1.5.x with the same
 personal configuration directory.
 
+The list of recently open files is now stored in a different location.
+It will therefore be reset when upgrading from LyX 1.4.x.
+
 The format of the layout files has also changed, but LyX 1.5.x uses a
 converter layout2layout.py written in python that will convert old layout
 files on the fly (see below, section "Document transfer").
svndiff src/LaTeXFeatures.cpp

Index: src/LaTeXFeatures.cpp
===
--- src/LaTeXFeatures.cpp	(revision 22043)
+++ src/LaTeXFeatures.cpp	(working copy)
@@ -418,7 +418,6 @@ char const * simplefeatures[] = {
 	"floatflt",
 	"varioref",
 	"prettyref",
-	"float",
 	"booktabs",
 	"dvipost",
 	"fancybox",
@@ -810,6 +809,11 @@ BufferParams const & LaTeXFeatures::buff
 
 void LaTeXFeatures::getFloatDefinitions(ostream & os) const
 {
+	if ((isRequired("floats") 
+	 || params_.float_placement.find('h') != string::npos)
+	&& !params_.getTextClass().provides("floats"))
+		os << "\\usepackage{floats}\n";
+
 	FloatList const & floats = params_.getTextClass().floats();
 
 	// Here we will output the code to create the needed float styles.

Re: [LyX wiki] recent notify posts

[Jean-Marc Lasgouttes]

[EMAIL PROTECTED] writes:

> I think I've fixed it now. From now on, when pages are modified it
> should show up on this page... I hope :-)

Thanks.

JMarc

Re: [LyX wiki] recent notify posts

[Jean-Marc Lasgouttes]

Apache <[EMAIL PROTECTED]> writes:

> All recent posts: http://wiki.lyx.org/Site/AllRecentChanges

This page does not exist... What is supposed to be found there?

JMarc

Re: Notifications of modified files

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> [EMAIL PROTECTED] schrieb:
>
>> However, if you are careful and look at the general mail, there is
>> no need for a separate mail of course.
>
> I prefer what we already have, because then more people will have a look.

If I see a change on this page and he author indicates "uwe" as name,
I will not even take a look.

JMarc

Re: Notifications of modified files

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> Jean-Marc Lasgouttes schrieb:
>
>> BTW, did you see the message "Download pages shouldn't be in wiki" a
>> month ago on this list? Should we password protect better the pages
>> for windows and mac download?
>
> No, currently the wiki works as a Wiki should work: Vandalism and
> wrong entries will be removed by the users quickly.

Except that I do not think that the official download page should be
on a wiki. What happens if somebody puts a file with a virus there?

JMarc

Re: Apparently sane po file makes lyx crash

[Jean-Marc Lasgouttes]

Koji Yokota <[EMAIL PROTECTED]> writes:

> Hi,
>
> I'm currently updating the Japanese message file and facing an error in
> which the updated message file causes lyx to crash. Can anyone tell me
> whether this can happen because of any problem in the message file or it
> can be a bug in LyX? Conversion of the po file by msgfmt emits no error
> messages and any grammatical checks by the editor (KBabel) returns OK.
> Encoding also seems OK.

The problematic entry is

#: src/support/filetools.cpp:310
msgid "[[Replace with the code of your language]]"
msgstr "[[ã䜿ãã®èšèªã®ã³ãŒãã§çœ®æãŠãã ãã]]"

Here is the relevant entry from the new README.localization file:

-
4) WHAT SHOULD I DO WITH THE '&', '|', '$, '%' AND [[]] CHARACTERS?

'&' stands for underlined characters (shortcut) in dialog boxes.
'|' stands for underlined characters in menus.

These chars should be somehow used in your translations, however you'll have to 
invent your own working shortcuts for dialog and menu entries and resolve 
possible conflicts of the same shortcut chars in one menu... 

Note also that there are already used global shortcuts (such as p k x c m) and
you should avoid to use these characters for first-level menu shortcuts.

'$' and '%' are usually used as handlers for formatting or variables to be 
inserted into the strings. Character sequences like %1$s or %1$d MUST also 
appear in your translations! Please take them exactly as they are or you may 
experience crashes when running LyX.

[[Context]] is used to distinguish otherwise identical strings, which could
have different translation dependent on the Context. [[Context]] appears only
in msgid string and should not be repeated in the translated version.
-

You should leave it as it was in the file:

#: src/support/filetools.cpp:313
msgid "[[Replace with the code of your language]]"
msgstr "ja"

It is used internally by LyX to find out what language has been
loaded.

Is it clear?

JMarc

Re: Notifications of modified files

[Jean-Marc Lasgouttes]

[EMAIL PROTECTED] writes:

> Below you can see that I've activate the notification of files, so
> from now on, whenever files are changed in the wiki, this list should
> get a message.

Good idea.

BTW, did you see the message "Download pages shouldn't be in wiki" a
month ago on this list? Should we password protect better the pages
for windows and mac download?

JMarc

Re: Problem testing translation

[Jean-Marc Lasgouttes]

Le 30 sept. 07 à 18:32, Martin Vermeer a écrit :

On Sun, Sep 30, 2007 at 04:51:36PM +0200, Ran Rutenberg wrote:

Hi,

After much work I've isolated the string that is causing the  
trouble. The
string id is 3569. The string itself is "[[Replace with the code  
of your
language]]". No matter what I'm writing as a translation (I even  
tried to
omit the square brackets) I'm getting the error I've described. If  
I don't

translate the string the error disappears.
I hope someone can help me get around this problem.



As martin pointed out, using 'he' as translation is a fix. However,  
there is code in
Message.cpp to remove [[text]] from the translated string. I am not  
sure why it does not work.


namespace {
boost::regex const reg("^([^\\[]*)\\[\\[[^\\]]*\\]\\]$");
};

qnd then

// Some english words have different translations,
// depending on context. In these cases the original
// string is augmented by context information (e.g.
// "To:[[as in 'From page x to page y']]" and
// "To:[[as in 'From format x to format y']]".
// This means that we need to filter out everything
// in double square brackets at the end of the
// string, otherwise the user sees bogus messages.
// If we are unable to honour the request we just
// return what we got in.
boost::smatch sub;
if (regex_match(m, sub, reg))
translated = from_ascii(sub.str(1));
else
translated = from_ascii(tmp);

JMarc

Re: dvips and absolute paths in linux

[Jean-Marc Lasgouttes]

"Giuseppe Pagnoni" <[EMAIL PROTECTED]> writes:

> A quick solution is to modify LyX preferences to use, instead of "dvips",
> the command "dvips -R0" which instructs dvips to behave like the former
> version.

Could you enter a bug at bugzilla.lyx.org? This is definitely
something we should fix.

JMarc

Re: Background of website

[Jean-Marc Lasgouttes]

Siegfried MEUNIER-GUTTIN-CLUZEL <[EMAIL PROTECTED]> writes:

> My main problem with the LyX main web site : it is not really up to date !
> - graphic tour of version 1.3
> - development news of 2005

Very true. 

JMarc

Re: Background of website

[Jean-Marc Lasgouttes]

David Krebs <[EMAIL PROTECTED]> writes:

> Hi there,
>
> it's just a little thing I have to mention: Could you *please* change the 
> background of the Lyx website? It hurts my eyes. ;)
> No, it's not the color. I really like green. But: It's extremely ehausting to 
> read through white text on ground of a repeating white/black/green LyX logo.

Did you try the 'fewer images' link?

Hmm, I see now that this variable value is not passed to links on
which one clicks. This is very very wrong.

Our website is in a really poor shape, to be frank.

JMarc

[PATCH] fix M-Return (was Re: UserGuide-test hints and questions, 2)

[Jean-Marc Lasgouttes]

> Jean-Marc Lasgouttes schrieb:
>> M-Return is supposed to be do for commands what Return would do for
>> Environments and do for environments what Return would do for
>> commands.
>>
>> However, I see now that it does not do anything interesting for
>> enumerations. I'll have to double check that.

Here is a patch that implements proper functionning of M-Return (at
least as I see it: like Return, but inverting role of environment and
non-environment). I'd be interested to have some feedback on it. This
is potentially for trunk and branch.

This is basically bug 2445
http://bugzilla.lyx.org/show_bug.cgi?id=2445
but not everybody agrees on what the behaviour should be.

JMarc

svndiff src

Index: src/Text.cpp
===
--- src/Text.cpp	(révision 20240)
+++ src/Text.cpp	(copie de travail)
@@ -356,7 +356,7 @@ double Text::spacing(Buffer const & buff
 }
 
 
-void Text::breakParagraph(Cursor & cur, bool keep_layout)
+void Text::breakParagraph(Cursor & cur, bool inverse_logic)
 {
 	BOOST_ASSERT(this == cur.text());
 
@@ -381,11 +381,9 @@ void Text::breakParagraph(Cursor & cur, 
 		cpar.eraseChar(cur.pos(), cur.buffer().params().trackChanges);
 
 	// What should the layout for the new paragraph be?
-	int preserve_layout = 0;
-	if (keep_layout)
-		preserve_layout = 2;
-	else
-		preserve_layout = layout->isEnvironment();
+	bool keep_layout = inverse_logic ? 
+		!layout->isEnvironment() 
+		: layout->isEnvironment();
 
 	// We need to remember this before we break the paragraph, because
 	// that invalidates the layout variable
@@ -395,7 +393,7 @@ void Text::breakParagraph(Cursor & cur, 
 	bool const isempty = cpar.allowEmpty() && cpar.empty();
 
 	lyx::breakParagraph(cur.buffer().params(), paragraphs(), cpit,
-			 cur.pos(), preserve_layout);
+			 cur.pos(), keep_layout);
 
 	// After this, neither paragraph contains any rows!
 
Index: src/Text3.cpp
===
--- src/Text3.cpp	(révision 20240)
+++ src/Text3.cpp	(copie de travail)
@@ -574,13 +574,13 @@ void Text::dispatch(Cursor & cur, FuncRe
 
 	case LFUN_BREAK_PARAGRAPH:
 		cap::replaceSelection(cur);
-		breakParagraph(cur, 0);
+		breakParagraph(cur, false);
 		cur.resetAnchor();
 		break;
 
 	case LFUN_BREAK_PARAGRAPH_KEEP_LAYOUT:
 		cap::replaceSelection(cur);
-		breakParagraph(cur, 1);
+		breakParagraph(cur, true);
 		cur.resetAnchor();
 		break;
 
@@ -591,7 +591,7 @@ void Text::dispatch(Cursor & cur, FuncRe
 		if (cur.pos() == 0)
 			cur.paragraph().params().labelWidthString(docstring());
 		else
-			breakParagraph(cur, 0);
+			breakParagraph(cur, false);
 		cur.resetAnchor();
 		break;
 	}
Index: src/paragraph_funcs.h
===
--- src/paragraph_funcs.h	(révision 20240)
+++ src/paragraph_funcs.h	(copie de travail)
@@ -27,9 +27,9 @@ class ParagraphList;
 /**
  * This breaks a paragraph at the specified position.
  * The new paragraph will:
- * get the default layout, when flag == 0
- * will inherit the existing one, except for depth, when flag == 1
- * will inherit the existing one, including depth, when flag == 2
+ * - Decrease depth by one (or chenge layout to default layout when 
+ *keep_layout == false  
+ * - keep current depth and layout when keep_layout == true
  * Be aware that the old or new paragraph does not contain any rows
  * after this.
  */
@@ -37,7 +37,7 @@ void breakParagraph(BufferParams const &
 		ParagraphList & paragraphs,
 		pit_type par,
 		pos_type pos,
-		int flag);
+		bool keep_layout);
 
 ///
 void breakParagraphConservative(BufferParams const & bparams,
Index: src/paragraph_funcs.cpp
===
--- src/paragraph_funcs.cpp	(révision 20240)
+++ src/paragraph_funcs.cpp	(copie de travail)
@@ -60,7 +60,8 @@ static bool moveItem(Paragraph & fromPar
 
 
 void breakParagraph(BufferParams const & bparams,
-	ParagraphList & pars, pit_type par_offset, pos_type pos, int flag)
+		ParagraphList & pars, pit_type par_offset, pos_type pos, 
+		bool keep_layout)
 {
 	// create a new paragraph, and insert into the list
 	ParagraphList::iterator tmp =
@@ -76,7 +77,7 @@ void breakParagraph(BufferParams const &
 	tmp->setInsetOwner(par.inInset());
 
 	// layout stays the same with latex-environments
-	if (flag) {
+	if (keep_layout) {
 		tmp->layout(par.layout());
 		tmp->setLabelWidthString(par.params().labelWidthString());
 		tmp->params().depth(par.params().depth());
@@ -90,7 +91,7 @@ void breakParagraph(BufferParams const &
 
 	bool const isempty = (par.allowEmpty() && par.empty());
 
-	if (!isempty && (par.size() > pos || par.empty() || flag == 2)) {
+	if (!isempty && (par.size() > pos || par.empty())) {
 		tm

Re: UserGuide-test hints and questions, 2

[Jean-Marc Lasgouttes]

Uwe Stöhr <[EMAIL PROTECTED]> writes:

> Ignacio García schrieb:
>
>> I send you more small patchs and doubts about UserGuide:
>>
>> 3.3.6.1 "The nesting depth is typically reset, however. If you want to keep 
>> both
>>   the current nesting depth and paragraph environment, you should use
>>   M-Return to break paragraphs."
>>  I see no difference between M-Return and Return
>
> Oh, it should be C-Return, I fixed this.

No, C-Return is something else. The behaviour of M-Return has been
changed (by me) some time ago, but I did not change the documentation. 

The place where it is different is normal commands: if you type
M-Return after a section, for example, it will still be a section (or
a standard environment), and the depth (yes, I know that nesting a
section is weird) will be kept.

M-Return is supposed to be do for commands what Return would do for
Environments and do for environments what Return would do for
commands.

However, I see now that it does not do anything interesting for
enumerations. I'll have to double check that.

JMarc

Re: history of TeX and LaTeX

[Jean-Marc Lasgouttes]

> "Nicolas" == Nicolas Le Novere <[EMAIL PROTECTED]> writes:

Nicolas> Dear authors, The inaccuracy in the dating of TeX and LaTeX
Nicolas> creation is really itching me. I first reporting the error in
Nicolas> 2001 or 2002 I think, but nothing has been done.

Hello Nicolas,

You are right that such things should be corrected.

Nicolas> Maybe there is an entry about the publication of the first
Nicolas> book but LaTeX was created way before that. The book itself
Nicolas> was decided by Addison-Wesley in 1983
Nicolas> (http://research.microsoft.com/users/lamport/pubs/pubs.html#latex)
Nicolas> The first LaTeX manual was written in december 1983 and the
Nicolas> version 2.06a was released on september 1984.

It would probably be fair to mention the release date of LaTeX 2e (1994?).

Nicolas> Regarding TeX, it is much worse of course. LyX manual says:
Nicolas> "a typesetting language called TeX, created by Donald Knuth
Nicolas> in 1984."

Nicolas> I have not a clue how this date came on. Knuth first
Nicolas> description of TeX was given in 1978 (later published in
Nicolas> Bull. AMS, vol. 1 (March 1979), no. 2, pp. 337--372)

But TeX78 is not really TeX as we know it, right? Isn't 1982 a more
reasonable date?

Nicolas> Please correct the dates. It does not do LyX any good to
Nicolas> alienate (La)TeX community on such simple errors.

It would be great if you could propose us a new wording of these
paragraphs :)

JMarc

Re: translating lyx-1.5.0

[Jean-Marc Lasgouttes]

>>>>> "Ramon" == Ramon Flores <[EMAIL PROTECTED]> writes:

Ramon> Jean-Marc Lasgouttes wrote:
Uwe> The commands itself like "\linebreak" are not translated, the
Uwe> rest is usually translated. Michael and JMarc can tell you more
Uwe> about this.
>>  The commands should not be translated indeed. What are typical
>> examples of commands?

Ramon> #: lib/ui/stdtoolbars.inc:316 msgid "overline" msgstr ""

Yes, I have found them since then... I am not sure how we could mark
them as non translatable.

JMarc

Re: translating lyx-1.5.0

[Jean-Marc Lasgouttes]

> "Uwe" == Uwe Stöhr <[EMAIL PROTECTED]> writes:

Uwe> Ramon Flores schrieb:
>> If the writer know the latex name for a symbol, is quicker to write
>> it with the keyboard that to select it with the mouse. So, as there
>> is not a galician version of LaTeX, I considered more useful not to
>> translate these messages. So the user can learn the names of the
>> symbols, and enter them by keyboard.
>> 
>> So I would know what the other translators think about the
>> following questions:
>> 
>> 1) Are LaTeX command translated to any language?.

Uwe> The commands itself like "\linebreak" are not translated, the
Uwe> rest is usually translated. Michael and JMarc can tell you more
Uwe> about this.

The commands should not be translated indeed. What are typical
examples of commands?

JMarc

Re: Menu Separator in the Hebrew documentation.

[Jean-Marc Lasgouttes]

> "Ran" == Ran Rutenberg <[EMAIL PROTECTED]> writes:

Ran> On 5/8/07, Juergen Spitzmueller <[EMAIL PROTECTED]> wrote:
>> 2. in InsetSpecialChar::latex, check whether you are in LtR mode or
>> not, and request lyxarrow or lyxlarrow accordingly. Same in
>> plaintext and probably something similar in docbook.

We could also try to define a \lyxarrow that does the right thing
depending on rtl status.

>> 4. in InsetSpecialChar::metrics, do likewise for screen drawing
>> (just play with that painting coordinates).

Ran> Where are all these files located? I can't find them in the src
Ran> directory.

Look at src/insets/InsetSpecialChar.cpp

JMarc

Re: Menu Separator in the Hebrew documentation.

[Jean-Marc Lasgouttes]

> "Ran" == Ran Rutenberg <[EMAIL PROTECTED]> writes:

Ran> Hi, The Documentation Project Style Sheet states the one should
Ran> use the menu separator character when referring to menus. Alas,
Ran> this character is good only for LTR languages and is not suitable
Ran> to RTL languages (see: bug
Ran> 3560) . I thought
Ran> about overcoming this problem using the vartriangleleft character
Ran> from the AMS Relations. Is this okay?

What about changing the latex and screen code to revert the direction
of the arrow in LtR mode?

JMarc

Re: Updated he.po

[Jean-Marc Lasgouttes]

> "Ran" == Ran Rutenberg <[EMAIL PROTECTED]> writes:

Ran> Hi, A newer version of the he.po file is available here:
Ran> http://www.yousendit.com/download/TEhVT0NVdVVTRTQwTVE9PQ.

Ran> Now it is possible to use LyX almost entirely in Hebrew.

Hi Ran,

The file is in now. Thanks.

JMarc

Re: hu.po update for 1.5

[Jean-Marc Lasgouttes]

> "Alex" == Alex  <[EMAIL PROTECTED]> writes:

Alex> Dear Jean-Marc, Here, I send you an update of the po file for
Alex> 1.5

This one is in too.

JMarc