On Fri, Oct 23, 2015 at 11:05:59PM +0200, Georg Baum wrote:
> The fix is simple: Re-add the deleted lines to set the encoding to utf8-
> plain (see attachment). Then Development.lyx compiles again for me. The
> encoding must always be utf8 for full unicode backends if non-TeX fonts are
> used.
On 2015-10-25, Scott Kostyshak wrote:
> How can I compile the Russian intro manual with polyglossia and non-TeX
> fonts? Do I need to change any encodings?
With non-TeX fonts (aka fontspec), the input encoding is utf8 and the font
encoding Unicode (pseudo fontencoding EU1 with XeTeX and EU2 with
Am Sonntag, 25. Oktober 2015 um 08:02:54, schrieb Guenter Milde
> On 2015-10-25, Scott Kostyshak wrote:
> > How can I compile the Russian intro manual with polyglossia and non-TeX
> > fonts? Do I need to change any encodings?
>
> With non-TeX fonts (aka fontspec), the input
Am Sonntag, 25. Oktober 2015 um 01:01:12, schrieb Scott Kostyshak
> On Wed, Oct 14, 2015 at 01:41:22PM +0200, Kornel Benko wrote:
> > Am Dienstag, 13. Oktober 2015 um 16:48:15, schrieb Scott Kostyshak
> >
> > > On Tue, Oct 13, 2015 at 02:03:22PM +0200,
On 2015-10-23, Georg Baum wrote:
> [-- Type: text/plain, Encoding: 7bit --]
> Guenter Milde wrote:
>> On 2015-10-21, Scott Kostyshak wrote:
>>> It compiles fine before this commit.
>> Yes, but only "per accident": Development.lyx only uses some non-ASCII
>> characters, and these are also at
Scott Kostyshak wrote:
> On Fri, Oct 23, 2015 at 10:01:42AM +0200, Jean-Marc Lasgouttes wrote:
>
>> >It saves some time because I don't need to write all the sime "see
>> >sec._" (where _ is a half space) but only "see ". Furthermore one has a
>> >larger area to click on in the PDF. personally
On 2015-10-25, Guenter Milde wrote:
> On 2015-10-25, Georg Baum wrote:
>> Guenter Milde wrote:
>>> I'll commit the patch for the patch and hope this will solve some more of
>>> the automatic XeTeX tests.
>> Please do.
> It is in.
> Scott, could you please test if this fixes some more export
Scott Kostyshak wrote:
> -% increase link area for cross-references and autoname them,
> -\AtBeginDocument{\renewcommand{\ref}[1]{\mbox{\autoref{#1
> -\addto\extrasfrench{%
> - \renewcommand*{\equationautorefname}[1]{}%
> - \renewcommand{\sectionautorefname}{sec.\negthinspace}%
> -
PhilipPirrip wrote:
> LibreOffice has it as "Special Characters". Fedora Linux has an
> application called "Character Map" that lists characters by, I believe,
> unicode blocks.
> And all those are just single characters. Symbols, though, can be one or
> more: Greek alpha or \LaTeX
> Just my 5
Am Sonntag, 25. Oktober 2015 um 12:04:36, schrieb Georg Baum
> PhilipPirrip wrote:
>
> > LibreOffice has it as "Special Characters". Fedora Linux has an
> > application called "Character Map" that lists characters by, I believe,
> > unicode blocks.
> > And all
Uwe Stöhr wrote:
> Hi Georg,
>
> it is OK with me if you reverted this for good reasons, I only want to
> understand why you reverted and how the feature I implemented will be
> available now.
I reverted to get rid of a regression you introduced. If you want more
details, please read the
Hi Richard,
I'd like to backport this change to 2.1.x.
This is another attempt to fix tickets like #8637.
http://www.lyx.org/trac/ticket/8637
Is it ok?
Stephan
Am 09.10.2015 um 10:07 schrieb Stephan Witt :
> commit 989c72530e789abf234cca5e6084e585cc073bb6
> Author: Stephan
On 2015-10-25, Georg Baum wrote:
> Guenter Milde wrote:
>> I'll commit the patch for the patch and hope this will solve some more of
>> the automatic XeTeX tests.
> Please do.
It is in.
Scott, could you please test if this fixes some more export tests?
> BTW, the braces around the equality
Scott Kostyshak wrote:
> The following tests are currently expected to fail because of issues with
> nested language handling and polyglossia. Georg, if you still have
> interest and time for fixing this type of issue, take a look at these:
>
> export/doc/nb/Intro_pdf5_systemF
>
Guenter Milde wrote:
> Just to be sure we don't misunderstand: The question is about tests
> compiling the documentation "as-is" (i.e. with *TeX fonts*) using
> XeTeX.
Thanks for the clarification, I think we misunderstood. For XeTeX + TeX
fonts I agree.
> For me, Development.lyx compiles fine
On 2015-10-25, Kornel Benko wrote:
> Am Sonntag, 25. Oktober 2015 um 08:02:54, schrieb Guenter Milde
>
>> On 2015-10-25, Scott Kostyshak wrote:
>> > How can I compile the Russian intro manual with polyglossia and non-TeX
>> > fonts? Do I need to change any encodings?
>>
Am Sonntag, 25. Oktober 2015 um 11:31:09, schrieb Guenter Milde
> On 2015-10-25, Georg Baum wrote:
> > Guenter Milde wrote:
>
> >> I'll commit the patch for the patch and hope this will solve some more of
> >> the automatic XeTeX tests.
>
> > Please do.
>
> It is in.
>
>
polyglossia supports the Khmer (Cambodian) language. LyX can therefore
support this language too easily.
OK to go on?
regards Uwe
diff --git
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\lanB3F1.tmp\\languages-27ce44d-left"
"b/D:\\LyXGit\\Master\\lib\\languages"
index
Le 25/10/2015 21:58, Uwe Stöhr a écrit :
This is not about ERT. It is about preamble code I use. This code saves
work and the user benefits from it in the PDF.
Preamble is ERT, actually.
The LyX manuals cannot be references for clean LyX documents. It is a
hard task to describe all the many
Your call. I know nothing about this stuff.
On 10/25/2015 09:27 AM, Stephan Witt wrote:
Hi Richard,
I'd like to backport this change to 2.1.x.
This is another attempt to fix tickets like #8637.
http://www.lyx.org/trac/ticket/8637
Is it ok?
Stephan
Am 09.10.2015 um 10:07 schrieb Stephan
Le 25/10/2015 15:37, Paul A. Rubin a écrit :
Pavel Sanda lyx.org> writes:
This would be nice to have, though I am wondering whether such feature doesn't
belong directly to menu, next to 'Show changes in output'. More work, I
know...
I was hoping it would be a menu choice in an upcoming
Vincent van Ravesteijn wrote:
I thought we always wanted to support as many compilers as reasonably
possible in order to allow newcomers to easily compile LyX and to let
them contribute.
Please, take also into account other factors determining the
attractiveness to newcomers, such as
Am 25.10.2015 um 22:22 schrieb Vincent van Ravesteijn:
Why do you choose the option by which you feel offended ? Georg just
considers to improve the support, so maybe to teach LyX about autoref,
instead of using preamble code. He does not judge you.
The sound makes the music. I read often
On 2015-10-25, Georg Baum wrote:
> Guenter Milde wrote:
>> Actually, the patch does now what Georg expected the old patch to do:
>> set encoding to ASCII for every use of XETEX, also with non-TeX fonts.
>> This fails with characters without a LICR defined by "xunicode".
>> So the current best
Le 24/10/2015 17:17, Guy Rutenberg a écrit :
Hi,
I've encounter a minor bug in the previewing of math macro: That is,
after you create a math macro it would normally exapand the macro in
normal math mode to the LyX representation of the macro. However, if the
macro name is a single digit (e.g.
On Sun, Oct 25, 2015 at 09:43:50PM +0100, Uwe Stöhr wrote:
> Am 25.10.2015 um 11:05 schrieb Georg Baum:
>
> >I reverted to get rid of a regression you introduced. If you want more
> >details, please read the commit log and the thread I referred to in the
> >commit log, since we discussed the
On Fri, Oct 23, 2015 at 07:31:49PM +, Guenter Milde wrote:
> On 2015-10-23, Scott Kostyshak wrote:
> > On Tue, Oct 20, 2015 at 09:10:05PM +, Guenter Milde wrote:
> >> On 2015-10-20, Scott Kostyshak wrote:
> >> > On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote:
> >> >> commit
Am 25.10.2015 um 23:42 schrieb Jean-Marc Lasgouttes:
> What I say is that this code should not be used as a convenience, but
only when it is a necessity.
Well, LyX itself is a convenience product. My professor once forced me
to TeX a file and this is how I came to LyX because this was the
The attached patch adds support for the modernCV features introduced by
version 1.5 from April 2013.
I think it is safe enough to support 2 years old features and would
therefore like to put it in.
Since a style is added, this would be a simple fileformat change.
OK to go on?
regards Uwe
On Sun, Oct 25, 2015 at 11:17:15AM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > -% increase link area for cross-references and autoname them,
> > -\AtBeginDocument{\renewcommand{\ref}[1]{\mbox{\autoref{#1
> > -\addto\extrasfrench{%
> > - \renewcommand*{\equationautorefname}[1]{}%
>
On Mon, Oct 26, 2015 at 03:50:43AM +0100, Uwe Stöhr wrote:
> The attached patch adds support for the modernCV features introduced by
> version 1.5 from April 2013.
>
> I think it is safe enough to support 2 years old features and would
> therefore like to put it in.
Do we have any policy on
On Sun, Oct 25, 2015 at 11:10:56AM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
>
> > The following tests are currently expected to fail because of issues with
> > nested language handling and polyglossia. Georg, if you still have
> > interest and time for fixing this type of issue, take a
On Sun, Oct 25, 2015 at 01:21:01PM +0100, Kornel Benko wrote:
> Am Sonntag, 25. Oktober 2015 um 11:31:09, schrieb Guenter Milde
>
> > On 2015-10-25, Georg Baum wrote:
> > > Guenter Milde wrote:
> >
> > >> I'll commit the patch for the patch and hope this will solve some more
Dear all,
I just added an entry to the wiki
(http://wiki.lyx.org/Layouts/Modules#toc2, "Printing change bars") that
contains two links awaiting approval. None of the passwords I (vaguely)
remember seem to work for this, so if someone could bless them, I'd be
grateful.
Thanks,
Paul
Am Sonntag, 25. Oktober 2015 um 16:48:39, schrieb Guenter Milde
> On 2015-10-25, Guenter Milde wrote:
> > On 2015-10-25, Kornel Benko wrote:
> >> Am Sonntag, 25. Oktober 2015 um 08:02:54, schrieb Guenter Milde
> >>
> >>> On 2015-10-25, Scott Kostyshak
On 2015-10-25, Guenter Milde wrote:
> On 2015-10-25, Kornel Benko wrote:
>> Am Sonntag, 25. Oktober 2015 um 08:02:54, schrieb Guenter Milde
>>
>>> On 2015-10-25, Scott Kostyshak wrote:
>>> > How can I compile the Russian intro manual with polyglossia and non-TeX
>>> > fonts?
Guenter Milde wrote:
> Actually, the patch does now what Georg expected the old patch to do:
>
> set encoding to ASCII for every use of XETEX, also with non-TeX fonts.
>
> This fails with characters without a LICR defined by "xunicode".
>
> So the current best known version would be to admit
Guenter Milde wrote:
> It turned out, that the problem is the preamble code:
>
> \usepackage{ifpdf} % part of the hyperref bundle
> \ifpdf % if pdflatex is used
>
> % set fonts for nicer pdf view
> \IfFileExists{lmodern.sty}{\usepackage{lmodern}}{}
>
> \fi % end if pdflatex is
Am 25.10.2015 um 17:03 schrieb Paul A. Rubin:
I just added an entry to the wiki
(http://wiki.lyx.org/Layouts/Modules#toc2, "Printing change bars") that
contains two links awaiting approval. None of the passwords I (vaguely)
remember seem to work for this, so if someone could bless them, I'd be
Am 25.10.2015 um 11:05 schrieb Georg Baum:
I reverted to get rid of a regression you introduced. If you want more
details, please read the commit log and the thread I referred to in the
commit log, since we discussed the possible alternatives in detail over the
last days.
Well, of course I
Am 23.10.2015 um 10:01 schrieb Jean-Marc Lasgouttes:
Besides portability to other contexts, there is an advantage in reducing
the amount of ERT: the manuals can be used as demonstration of a LyX
document. Using lots of ERT just gives the message that LyX support of
LaTeX is weak. And in some
Am 25.10.2015 um 11:08 schrieb Georg Baum:
And if something is wrong with them, we should invest the time and improve
our formatted references support, instead of fiddling with the premable.
I set up
www.lyx.org/trac/ticket/9817
for this issue.
And no, using a feature of a well-known package
Am 25.10.2015 um 06:10 schrieb Scott Kostyshak:
The system font I use is FreeSans (I use it for all three). I just added
a conditional in the preamble so now it should work for both babel and
polyglossia.
Thanks for finding this solution. I did not know about this.
It saves some time
Op 25-10-2015 om 22:12 schreef Uwe Stöhr:
Am 25.10.2015 um 11:08 schrieb Georg Baum:
And if something is wrong with them, we should invest the time and
improve
our formatted references support, instead of fiddling with the premable.
I set up
www.lyx.org/trac/ticket/9817
for this issue.
And
On 10/25/2015 07:43 AM, Kornel Benko wrote:
Am Sonntag, 25. Oktober 2015 um 12:04:36, schrieb Georg Baum
PhilipPirrip wrote:
LibreOffice has it as "Special Characters". Fedora Linux has an
application called "Character Map" that lists characters by, I
Pavel Sanda lyx.org> writes:
>
> This would be nice to have, though I am wondering whether such feature doesn't
> belong directly to menu, next to 'Show changes in output'. More work, I
know...
I was hoping it would be a menu choice in an upcoming release. Besides
needing someone to do the
On 2015-10-25, Richard Heck wrote:
...
>> "Special Character" itself feels OK. Maybe also "Special Symbols" ...
> What makes less sense to me is that use of "Symbols..." for what gets
> you to the dialog. I think maybe "Symbol Chooser..." would make it
> clearer what this was going to do.
I
On 10/25/2015 07:31 AM, Guenter Milde wrote:
On 2015-10-25, Georg Baum wrote:
BTW, the braces around the equality comparison are not needed, so
to my eyes
if (!params().useNonTeXFonts && runparams.flavor == OutputParams::XETEX)
is more readable.
I don't know the operator precedence in C++,
On 2015-10-25, Georg Baum wrote:
> Guenter Milde wrote:
>> It turned out, that the problem is the preamble code:
>> \usepackage{ifpdf} % part of the hyperref bundle
>> \ifpdf % if pdflatex is used
>> % set fonts for nicer pdf view
>> \IfFileExists{lmodern.sty}{\usepackage{lmodern}}{}
Richard Heck wrote:
> On 10/25/2015 07:31 AM, Guenter Milde wrote:
>> On 2015-10-25, Georg Baum wrote:
>>> BTW, the braces around the equality comparison are not needed, so
>>> to my eyes
>>> if (!params().useNonTeXFonts && runparams.flavor == OutputParams::XETEX)
>>> is more readable.
>> I don't
Op 24-10-2015 om 7:13 schreef Peter Kümmel:
Am 23.10.2015 um 21:34 schrieb Vincent van Ravesteijn:
support of MSVC2010.
I think I don't need to tell Peter about MSVC support for
C++11 (I guess he knows better than me).
The message was really meant for you: if you introduce C++11
features
Vincent van Ravesteijn wrote:
> I thought we always wanted to support as many compilers as reasonably
> possible in order to allow newcomers to easily compile LyX and to let
> them contribute. Does it make sense to still support Qt 4.5, but to
> require the last version of the Microsoft compiler
52 matches
Mail list logo