Abdelrazak Younes a écrit :
On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
Hello,
Using the spellchecker window, I get this quite often when I hit
'Ignore all':
cite
We reached the end of the document, would you like to continue from
the beginning?
/cite
If I say yes, it restars
Abdelrazak Younes a écrit :
On 04/03/2011 08:38 PM, Jean-Pierre Chrétien wrote:
Hello,
Using the spellchecker window, I get this quite often when I hit
'Ignore all':
We reached the end of the document, would you like to continue from
the beginning?
If I say yes, it restars
is I want, but it's a bore to
acknowledge the message all the time.
Found nothing on Trac, new bug ?
--
Jean-Pierre
. Much clearer
that a diff between the files themselves.
Great feature, really !
Would be nice to incorporate it in Trac to diff revisions...
--
Jean-Pierre
, but it's a bore to
acknowledge the message all the time.
Found nothing on Trac, new bug ?
--
Jean-Pierre
. Much clearer
that a diff between the files themselves.
Great feature, really !
Would be nice to incorporate it in Trac to diff revisions...
--
Jean-Pierre
in fr.comp.text.tex without success, I was surprised that
nobody raised what is an issue IMHO.
Also:
Acknowledgement Remerciement
In French, Remerciements is almost always plural, I think.
You're right I guess, I will correct this both in branch and trunk.
--
Jean-Pierre
, but it depends on the style of the table. We might discuss this further
on lyx-fr, where this kind of topic belongs.
--
Jean-Pierre
ot; is almost always plural, I think.
You're right I guess, I will correct this both in branch and trunk.
--
Jean-Pierre
quot;Table", I think it's also an
> acceptable translation.
Maybe, but it depends on the style of the table. We might discuss this further
on lyx-fr, where this kind of topic belongs.
--
Jean-Pierre
{{\scshape Table}}%
These inconsistent definitions have been there for years. Would it be possible
to add to LyX a redefinition of \tablename as Tableau to make LyX consistent in
the translation of the table stuff ?
--
Jean-Pierre
another problem, coming from babel this time: native
translations in the frenchb.ldf file read:
\def\listtablename{Liste des tableaux}%
\def\tablename{{\scshape Table}}%
These inconsistent definitions have been there for years. Would it be possible
to add to LyX a redefinition of \tablename as Tableau to make LyX consistent in
the translation of the table stuff ?
--
Jean-Pierre
Jürgen Spitzmüller spitz at lyx.org writes:
OK. I committed this to branch.
Does trunk need the same?
Sure
--
Jean-Pierre
Jürgen Spitzmüller spitz at lyx.org writes:
I see no ticket about this.
Shouldn't exist one, following earlier threads on the subject ?
Yes, it should, and it should point to target 2.0.
Done (ticket #7275)
--
Jean-Pierre
Jürgen Spitzmüller lyx.org> writes:
> OK. I committed this to branch.
>
> Does trunk need the same?
Sure
--
Jean-Pierre
Jürgen Spitzmüller lyx.org> writes:
> > I see no ticket about this.
> > Shouldn't exist one, following earlier threads on the subject ?
>
> Yes, it should, and it should point to target 2.0.
Done (ticket #7275)
--
Jean-Pierre
the
document is in letter format instead of the (global) a4 format set in TeXLive.
IMHO, it should not send any option.
Does this deserve a ticket ?
--
Jean-Pierre
the
document is in letter format instead of the (global) a4 format set in TeXLive.
IMHO, it should not send any option.
Does this deserve a ticket ?
--
Jean-Pierre
a command like
lyx-2.0.0svn -i latex foo.tex
I see that tex2lyx-1.6.8 is used instead of tex2lyx-2.0.0svn.
I can of course call tex2lyx-2.0.0svn directly, but is this behaviour correct ?
--
Jean-Pierre
hen I use a command like
lyx-2.0.0svn -i latex foo.tex
I see that tex2lyx-1.6.8 is used instead of tex2lyx-2.0.0svn.
I can of course call tex2lyx-2.0.0svn directly, but is this behaviour correct ?
--
Jean-Pierre
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
I have a warning with View DVI:
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from this command added by LyX to the preamble:
\special
instead of:
Page size: 595.276 x 841.89 pts (A4)
If I remove these two lines in the pdflatex export of the document, A4 is
obtained all right.
--
Jean-Pierre
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
I have a warning with "View DVI":
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from this command added by LyX to the preamble
e size: 524.409 x 814.006 pts
instead of:
Page size: 595.276 x 841.89 pts (A4)
If I remove these two lines in the pdflatex export of the document, A4 is
obtained all right.
--
Jean-Pierre
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
Attached.
Thanks. Committed to branch and trunk.
I have a warning with View DVI:
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This comes from
Jürgen Spitzmüller a écrit :
Jean-Pierre Chrétien wrote:
Attached.
Thanks. Committed to branch and trunk.
I have a warning with "View DVI":
xdvi-xaw: Warning: Invalid papersize special `0.0pt,0.0pt'
Harmless because the DVI file is displayed all right and is
in A4 format.
This
EndPreamble
--
Jean-Pierre
Jürgen Spitzmüller a écrit :
Hello,
Jean-Pierre Chrétien wrote:
Here is a patch:
Please send a real patch (as an attachment) or the whole layout file.
Attached.
--
Jean-Pierre
--- lib/layouts/lettre.layout.orig 2010-11-20 08:52:53.0 +0100
+++ lib/layouts/lettre.layout 2010-11-20
EndPreamble
--
Jean-Pierre
Jürgen Spitzmüller a écrit :
Hello,
Jean-Pierre Chrétien wrote:
Here is a patch:
Please send a real patch (as an attachment) or the whole layout file.
Attached.
--
Jean-Pierre
--- lib/layouts/lettre.layout.orig 2010-11-20 08:52:53.0 +0100
+++ lib/layouts/lettre.layout 2010-11-20
*’
--
Jean-Pierre
nversion from string
constant to ‘char*’
--
Jean-Pierre
.
--
Jean-Pierre
.
--
Jean-Pierre
a cfg-alike file.
Plus we'd still need the fallback in other cases.
Why create a fallback when we know that we provide a command ?
--
Jean-Pierre
a cfg-alike file.
Plus we'd still need the fallback in other cases.
Why create a fallback when we know that we provide a command ?
--
Jean-Pierre
Jean-Marc Lasgouttes lasgouttes at lyx.org writes:
Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit :
Is there some way we could provide translatability (in LyX's po
files) of theorem here?
For the time being, we need a restricted set of declarations and
translations
in LyX
, as the current test works for label like {:foo} and not for
{foo}. I posted a patch in bug #6609.
--
Jean-Pierre
Jean-Marc Lasgouttes lyx.org> writes:
>
> Le 28 oct. 10 à 18:24, Jean-Pierre Chrétien a écrit :
> >> Is there some way we could provide translatability (in LyX's po
> >> files) of "theorem" here?
> >
> > For the time being, we need a rest
in InseRef.cpp: if the label has no prefix at all, we get
the label as prefix, as the current test works for label like {:foo} and not for
{foo}. I posted a patch in bug #6609.
--
Jean-Pierre
Pavel Sanda sanda at lyx.org writes:
i moved .po files which were newer in branch to trunk.
once beta1 is out i will write .po maintainers to start work
on 2.0 translations.
Can I safely replace my current local version (up to date for trunk)
with the repository version ?
--
Jean-Pierre
Pavel Sanda sanda at lyx.org writes:
i didn't get what you are trying to acheive. fr.po was not touched
at all (except remerge).
Fine, I understood that you replaced po files in trunk by po files in branch.
--
Jean-Pierre
.
The messages do not stop make anyway, that was just to keep developers informed
of unusual compilations. If this kind of info is not useful, please let me know.
--
Jean-Pierre
soon.
Translation of beginning-of-sentence strings from English is NOT a simple
capitalization (and I'm not sure that this was well understood by translators,
see e.g. the Italian translation in refstyle.cfg).
Lastly, the par/part and cha/chap issue is still open...
--
Jean-Pierre
prefixes ?
--
jean-Pierre
Pavel Sanda lyx.org> writes:
> i moved .po files which were newer in branch to trunk.
> once beta1 is out i will write .po maintainers to start work
> on 2.0 translations.
Can I safely replace my current local version (up to date for trunk)
with the repository version ?
--
Jean-Pierre
Pavel Sanda lyx.org> writes:
> i didn't get what you are trying to acheive. fr.po was not touched
> at all (except remerge).
Fine, I understood that you replaced po files in trunk by po files in branch.
--
Jean-Pierre
nfigure is not to use LyX's boost library.
The messages do not stop make anyway, that was just to keep developers informed
of unusual compilations. If this kind of info is not useful, please let me know.
--
Jean-Pierre
more line in the
selection of the type of the reference) so it could be implemented soon.
Translation of beginning-of-sentence strings from English is NOT a simple
capitalization (and I'm not sure that this was well understood by translators,
see e.g. the Italian translation in refstyle.cfg).
Lastly, the par/part and cha/chap issue is still open...
--
Jean-Pierre
as soon as possible, so I vote for the first option.
Any other option possible ?
Are there other packages than prettyref using prefixes ?
--
jean-Pierre
Jean-Pierre Chrétien a écrit :
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
Oops, LyX should redefine \newrefformat is refstyle is selected (in case
of user-defined \newrefformat).
The simplest
Richard Heck a écrit :
On 11/04/2010 04:30 AM, Jean-Pierre Chrétien wrote:
Oops, LyX should redefine \newrefformat is refstyle is selected (in
case of user-defined \newrefformat).
The simplest (and easily reversible) solution seems to keep prettyref
package loaded even if refstyle
Richard Heck a écrit :
On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote:
I forgot to mention that I could make convert_prettyref.patch work.
So what is the idea behind this one? It seems to have a few different
parts.
I know there is a part/par chap/cha issue here somewhere. But I'm
Jean-Pierre Chrétien a écrit :
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
Oops, LyX should redefine \newrefformat is refstyle is selected (in case
of user-defined \newrefformat).
The simplest
Richard Heck a écrit :
On 11/04/2010 04:30 AM, Jean-Pierre Chrétien wrote:
Oops, LyX should redefine \newrefformat is refstyle is selected (in
case of user-defined \newrefformat).
The simplest (and easily reversible) solution seems to keep prettyref
package loaded even if refstyle
Richard Heck a écrit :
On 11/03/2010 01:28 PM, Jean-Pierre Chrétien wrote:
I forgot to mention that I could make convert_prettyref.patch work.
So what is the idea behind this one? It seems to have a few different
parts.
I know there is a part/par chap/cha issue here somewhere. But I'm
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
OK, so, for the time being, anyway, we think refstyle support is
complete? Or am I misremembering some other issue?
Extra \makeatother/\makeatletter in LaTeXFeatures.cpp and problem
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
OK, so, for the time being, anyway, we think refstyle support is
complete? Or am I misremembering some other issue?
Extra \makeatother/\makeatletter
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
OK, so, for the time being, anyway, we think refstyle support is
complete? Or am I misremembering some other issue?
Extra \makeatother/\makeatletter in LaTeXFeatures.cpp and problem
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 11/02/2010 02:01 PM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
OK, so, for the time being, anyway, we think refstyle support is
complete? Or am I misremembering some other issue?
Extra \makeatother/\makeatletter
Richard Heck a écrit :
On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
So do we have an extra \makeatletter somewhere?
Yes, exporting my example file in LaTeX reads:
cite
\makeatletter
%% LyX specific LaTeX commands
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
I got an anwer from Danie, I was mistaken about the multilingual feature
of refstyle: it works all right (as \def commands are encapsulated
Richard Heck a écrit :
On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
So do we have an extra \makeatletter somewhere?
Yes, exporting my example file in LaTeX reads:
\makeatletter
%% LyX specific LaTeX commands
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 10/31/2010 06:38 AM, Jean-Pierre Chrétien wrote:
Jean-Pierre Chrétien a écrit :
I got an anwer from Danie, I was mistaken about the multilingual feature
of refstyle: it works all right (as \def commands are encapsulated in
\extras
Uwe Stöhr a écrit :
I haven't followed this thread, but have you seen that the new version
0.4 of refstyle supports now French:
http://article.gmane.org/gmane.comp.tex.ctan.announce/8109
Sure, this follows a private mail exchange with Danie Els.
--
Jean-Pierre
Uwe Stöhr a écrit :
I haven't followed this thread, but have you seen that the new version
0.4 of refstyle supports now French:
http://article.gmane.org/gmane.comp.tex.ctan.announce/8109
Sure, this follows a private mail exchange with Danie Els.
--
Jean-Pierre
Jean-Pierre Chrétien a écrit :
I'll post a tentative file with bug #6609 to illustrate the idea
(tentative because it's not working right now).
I performed some tests to make this file work and I corrected some typos in the
file.
However, the current version does not work with LyX
Jean-Pierre Chrétien a écrit :
I'll post a tentative file with bug #6609 to illustrate the idea
(tentative because it's not working right now).
I performed some tests to make this file work and I corrected some typos in the
file.
However, the current version does not work with LyX
Richard Heck a écrit :
On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote:
Perhaps we can do this: (i) Try to get translations from our own
translators of theorem and lemma, if that covers everything prettyref
does, that we can hardcode into LaTeXFeatures.cpp, so that we at least
do
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
Are there other things besides theorems we should define that aren't
in refstyle.cfg?
To be prettyref-coherent, lemmas.
Lemmas and theorems are OK now (but untranslated), thanks.
--
Jean-Pierre
Richard Heck a écrit :
On 10/28/2010 12:24 PM, Jean-Pierre Chrétien wrote:
Perhaps we can do this: (i) Try to get translations from our own
translators of theorem and lemma, if that covers everything prettyref
does, that we can hardcode into LaTeXFeatures.cpp, so that we at least
do
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
Are there other things besides theorems we should define that aren't
in refstyle.cfg?
To be prettyref-coherent, lemmas.
Lemmas and theorems are OK now (but untranslated), thanks.
--
Jean-Pierre
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote:
When I look at the exported latex file test_french_refstyle.tex, I see this:
\...@ifundefined{ hmref}
{\def\RSthmtxt{theorem~}\newref{thm}{name = \RSthmtxt}}
which creates
Richard Heck a écrit :
I'm not seeing the difference
Anyway, I'm going to do the other thing I suggested, I think.
The problem with : has vanished, but theorems are now unknown:
?? is returned in my bug #6609 example.
--
Jean-Pierre
for
update in CTAN.
--
Jean-Pierre
Jean-Pierre Chrétien a écrit :
Richard Heck a écrit :
On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote:
When I look at the exported latex file test_french_refstyle.tex, I see this:
\...@ifundefined{ hmref}
{\def\RSthmtxt{theorem~}\newref{thm}{name = \RSthmtxt}}
which creates
Richard Heck a écrit :
I'm not seeing the difference
Anyway, I'm going to do the other thing I suggested, I think.
The problem with ":" has vanished, but theorems are now unknown:
?? is returned in my bug #6609 example.
--
Jean-Pierre
Danie Els for
update in CTAN.
--
Jean-Pierre
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
Richard Heck rgheck at comcast.net writes:
OK, one last try at a refstyle patch.
Comments welcome.
I'll investigate more with my examples.
Tested with French.
The \lyxref encapsulation does not work when
Richard Heck a écrit :
On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote:
Tested with French.
The \lyxref encapsulation does not work when : is active.
I'm trying to find a workaround, I'll keep you posted.
OK. Please let me know. We may need some \catcode thing in there?
Sure, that's
Jean-Pierre Chrétien free.fr> writes:
>
> Richard Heck comcast.net> writes:
>
> >
> >
> > OK, one last try at a refstyle patch.
> >
> > Comments welcome.
> I'll investigate more with my examples.
>
Tested with French.
The \lyxref
Richard Heck a écrit :
On 10/27/2010 04:17 AM, Jean-Pierre Chrétien wrote:
Tested with French.
The \lyxref encapsulation does not work when ":" is active.
I'm trying to find a workaround, I'll keep you posted.
OK. Please let me know. We may need some \catcode thing in the
Richard Heck rgheck at comcast.net writes:
OK, one last try at a refstyle patch.
Comments welcome.
Tried on a simple fresh document.
Seems that package ifthen should be included, due to the tests in the preamble.
I'll investigate more with my examples.
--
Jean-Pierre
Richard Heck comcast.net> writes:
>
>
> OK, one last try at a refstyle patch.
>
> Comments welcome.
Tried on a simple fresh document.
Seems that package ifthen should be included, due to the tests in the preamble.
I'll investigate more with my examples.
--
Jean-Pierre
://www.lyx.org/I18n
I hope I covered fairly well the discussions that took place on the
developers' list. What is your opinion about the various points that I
raised ?
Regards
--
Jean-Pierre
e, see e.g.
http://www.lyx.org/I18n
I hope I covered fairly well the discussions that took place on the
developers' list. What is your opinion about the various points that I
raised ?
Regards
--
Jean-Pierre
command name .
Warning: InsetCommand Error:
Incompatible command name.
--
Jean-Pierre
ams.cpp(256): InsetCommand: Incompatible command name .
Warning: InsetCommand Error:
----
Incompatible command name.
--
Jean-Pierre
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
And to be cosnisten
Jean-Pierre Chrétien free.fr> writes:
>
> > This will use all variants of varioref page handling.
>
> Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
> here (nor with \reftextfaraway in fact, page~xxx can be on the nest line).
>
handling.
--
Jean-Pierre
Jean-Pierre Chrétien jeanpierre.chretien at free.fr writes:
Why not
{\nameref{#1}~\vpageref{#1}}
This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway in fact, page~xxx
gt; }
Why not
{\nameref{#1}~\vpageref{#1}}
This will use all variants of varioref page handling.
--
Jean-Pierre
Jean-Pierre Chrétien free.fr> writes:
>
> Why not
>
> {\nameref{#1}~\vpageref{#1}}
>
> This will use all variants of varioref page handling.
Rather {\nameref{#1} \vpageref{#1}}, the unbrealkable space is not necessary
here (nor with \reftextfaraway
to ‘char*’
insets/InsetCitation.cpp:206: warning: deprecated conversion from string
constant to ‘char*’
--
Jean-Pierre
: deprecated conversion from string
constant to ‘char*’
insets/InsetCitation.cpp:206: warning: deprecated conversion from string
constant to ‘char*’
--
Jean-Pierre
parentheses around
within ||
HTH
--
Jean-Pierre
Cursor&, lyx::FuncRequest&)’:
insets/InsetTabular.cpp:3694: warning: suggest parentheses around &&
within ||
HTH
--
Jean-Pierre
Pavel Sanda a écrit :
Jean-Pierre Chrétien wrote:
Btw, the named link pointed to in section 1 is toc11, not toc7.
which link?
gpg-signed in The tarballs are gpg-signed.
--
Jean-Pierre
Pavel Sanda a écrit :
Jean-Pierre Chrétien wrote:
Hello,
I just translated in French this new section of
http://www.lyx.org/Download
and I had a try with this new procedure. I'm new to gpg, so where do I find
te keyserver ? Should not this information be added to the paragraph ?
it should
601 - 700 of 1080 matches
Mail list logo
