Le 10/07/2024 à 19:45, Udicoudco a écrit :
Removing the language switches inside the index entries
in the document should solve the problem.
Sorry for overlooking these. I guess that when I mark a sentence including an
index reference for change of language, something goes wrong in the
On Wed, Jul 10, 2024 at 08:48:24PM GMT, Udicoudco wrote:
> On Wed, Jul 10, 2024 at 8:45 PM Udicoudco wrote:
> >
> > On Wed, Jul 10, 2024 at 6:54 PM Scott Kostyshak wrote:
> > >
> > > The French Additional manual fails to compile after 18ce7a2e with system
On Wed, Jul 10, 2024 at 8:45 PM Udicoudco wrote:
>
> On Wed, Jul 10, 2024 at 6:54 PM Scott Kostyshak wrote:
> >
> > The French Additional manual fails to compile after 18ce7a2e with system
> > fonts and with either XeTeX or LuaTeX. I do not think that commit i
On Wed, Jul 10, 2024 at 6:54 PM Scott Kostyshak wrote:
>
> The French Additional manual fails to compile after 18ce7a2e with system
> fonts and with either XeTeX or LuaTeX. I do not think that commit is at
> fault, my guess is that it triggered an (already present) issue with our
&g
The French Additional manual fails to compile after 18ce7a2e with system
fonts and with either XeTeX or LuaTeX. I do not think that commit is at
fault, my guess is that it triggered an (already present) issue with our
LaTeX export?
It does still compile with pdflatex. I get the following error
when I use TeX-Fonts (that is, the box "Do not use TeX-Fonts
(via XeteX or LuaTeX)" is *not* checked).
But when I check that box and want to use Non-TeX-Fonts, the export
option to docx or odt via pandoc disappears.
The reason for this is that, if you use non-TeX fonts, then the
Am Sat, 7 Jan 2023 03:19:39 +0100
schrieb Thibaut Cuvelier :
> > What could you do, is to call xmlParser.pl directly to check if it working
> >
> > $ perl D:/LyX/lyx-unstable/development/autotests/xmlParser.pl
> > some_test_file.xml This should give the same error. In this case check if
On Sun, 1 Jan 2023 at 13:02, Kornel Benko wrote:
> Am Tue, 27 Dec 2022 02:13:15 +0100
> schrieb Thibaut Cuvelier :
>
> > Dear list,
> >
> > To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached
> patch.
> > Basically, LyX now considers the order of font tags when closing them,
> >
Am Tue, 27 Dec 2022 02:13:15 +0100
schrieb Thibaut Cuvelier :
> Dear list,
>
> To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached patch.
> Basically, LyX now considers the order of font tags when closing them,
> otherwise you get strange results like in the ticket. The bug is
On Tue, Dec 27, 2022 at 07:36:41PM +0100, Kornel Benko wrote:
> Am Tue, 27 Dec 2022 10:23:59 -0500
> schrieb Scott Kostyshak :
>
> > On Tue, Dec 27, 2022 at 10:12:15AM +0100, Kornel Benko wrote:
> > > Am Tue, 27 Dec 2022 00:03:40 -0500
> > > schrieb Scott Kostyshak :
> > >
> > > > On Tue, Dec
Am Tue, 27 Dec 2022 10:23:59 -0500
schrieb Scott Kostyshak :
> On Tue, Dec 27, 2022 at 10:12:15AM +0100, Kornel Benko wrote:
> > Am Tue, 27 Dec 2022 00:03:40 -0500
> > schrieb Scott Kostyshak :
> >
> > > On Tue, Dec 27, 2022 at 02:13:15AM +0100, Thibaut Cuvelier wrote:
> > > > Dear list,
> >
On 12/27/22 10:55, Thibaut Cuvelier wrote:
On Tue, 27 Dec 2022 at 05:42, Richard Kimberly Heck
wrote:
On 12/26/22 21:46, Thibaut Cuvelier wrote:
On Tue, 27 Dec 2022 at 03:20, Richard Kimberly Heck
wrote:
On 12/26/22 20:13, Thibaut Cuvelier wrote:
> Dear list,
On Tue, 27 Dec 2022 at 05:42, Richard Kimberly Heck
wrote:
> On 12/26/22 21:46, Thibaut Cuvelier wrote:
>
> On Tue, 27 Dec 2022 at 03:20, Richard Kimberly Heck
> wrote:
>
>> On 12/26/22 20:13, Thibaut Cuvelier wrote:
>> > Dear list,
>> >
>> > To solve https://www.lyx.org/trac/ticket/12585, I
On Tue, Dec 27, 2022 at 10:12:15AM +0100, Kornel Benko wrote:
> Am Tue, 27 Dec 2022 00:03:40 -0500
> schrieb Scott Kostyshak :
>
> > On Tue, Dec 27, 2022 at 02:13:15AM +0100, Thibaut Cuvelier wrote:
> > > Dear list,
> > >
> > > To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached
Am Tue, 27 Dec 2022 00:03:40 -0500
schrieb Scott Kostyshak :
> On Tue, Dec 27, 2022 at 02:13:15AM +0100, Thibaut Cuvelier wrote:
> > Dear list,
> >
> > To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached patch.
> > Basically, LyX now considers the order of font tags when closing
On Tue, Dec 27, 2022 at 02:13:15AM +0100, Thibaut Cuvelier wrote:
> Dear list,
>
> To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached patch.
> Basically, LyX now considers the order of font tags when closing them,
> otherwise you get strange results like in the ticket. The bug
On 12/26/22 21:46, Thibaut Cuvelier wrote:
On Tue, 27 Dec 2022 at 03:20, Richard Kimberly Heck
wrote:
On 12/26/22 20:13, Thibaut Cuvelier wrote:
> Dear list,
>
> To solve https://www.lyx.org/trac/ticket/12585, I wrote the
attached
> patch. Basically, LyX now considers
On Tue, 27 Dec 2022 at 03:20, Richard Kimberly Heck
wrote:
> On 12/26/22 20:13, Thibaut Cuvelier wrote:
> > Dear list,
> >
> > To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached
> > patch. Basically, LyX now considers the order of font tags when
> > closing them, otherwise you
On 12/26/22 20:13, Thibaut Cuvelier wrote:
Dear list,
To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached
patch. Basically, LyX now considers the order of font tags when
closing them, otherwise you get strange results like in the ticket.
The bug is quite serious, actually,
Dear list,
To solve https://www.lyx.org/trac/ticket/12585, I wrote the attached patch.
Basically, LyX now considers the order of font tags when closing them,
otherwise you get strange results like in the ticket. The bug is quite
serious, actually, even though I don't believe many users will hit
>From 6f6e2162a34f573316bbd1a3d81a7966c393b94f Mon Sep 17 00:00:00 2001
From: John R Hudson
Date: Sat, 24 Dec 2022 12:25:54 +
Subject: [PATCH] Insert entries for Section boxes, Variable-width minipages,
Fix Computer Modern Fonts, LaTeX Kernel fixes, Minimalistic Insets and Ti
Font caladea
> > + GuiName "Caladea"
> > + Family rm
> > + Package caladea
> > +EndFont
>
> How can I fix this? I tried reconfiguring / recompiling to no avail.
I forgot: You also need to add the font package to lib/chkconfig
Il 30/08/22 08:58, Jürgen Spitzmüller ha scritto:
Am Montag, dem 29.08.2022 um 22:44 +0200 schrieb Lorenzo Bertini:
Hello,
I noticed there are some fonts available for Latex that do not appear
in
Lyx's document settings: an example is Caladea Font. This font comes
in
"texlive-font-
Am Montag, dem 29.08.2022 um 22:44 +0200 schrieb Lorenzo Bertini:
> Hello,
>
> I noticed there are some fonts available for Latex that do not appear
> in
> Lyx's document settings: an example is Caladea Font. This font comes
> in
> "texlive-font-extra" packa
Hello,
I noticed there are some fonts available for Latex that do not appear in
Lyx's document settings: an example is Caladea Font. This font comes in
"texlive-font-extra" package in Debian, so it's something commonly used.
Right now I use "\usepackage{caladea}" in an &q
re. I like molecular gastronomy.
The last issue I have for now is InsetTabular. There is no reason for it
to be inheritFont==false, since the real one does inherit fonts. And
HTML/DocBook do the same.
In the current state of things, output of tabulars that are in an
inherited font (see my example with
Am Mo., 12. Apr. 2021 um 23:53 Uhr schrieb Enrico Forestieri :
> Apparently, "too many cooks spoil the broth" ;)
>
Sometimes sppoiled brot makes life interesting :-)
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
ueller
> Date: Sun Aug 16 11:18:49 2020 +0200
>
> Take out inheritFont() condition
>
>
> This was the right thing to do indeed, since inheritFont has nothing to
> do with the need to close fonts before an inset.
>
Yes. If this works now: great. This font ahndling is so nastily complex
2020 +0200
>
> Take out inheritFont() condition
Apparently, "too many cooks spoil the broth" ;)
> This was the right thing to do indeed, since inheritFont has nothing to do
> with the need to close fonts before an inset.
>
> I have to add that I do not unde
812ff7de7550f7c5370584294e61d59d8bbb8700
Author: Juergen Spitzmueller
Date: Sun Aug 16 11:18:49 2020 +0200
Take out inheritFont() condition
This was the right thing to do indeed, since inheritFont has nothing to
do with the need to close fonts before an inset.
I have to add that I do
Le 10/04/2021 à 10:46, Enrico Forestieri a écrit :
I think you reintroduced https://www.lyx.org/trac/ticket/10263
This is getting interesting. After getting half mad trying to understand
this issue, I tried something a bit radical: what about reverting the
fix 001f5a47 to ticket #10263?
On Sun, Apr 11, 2021 at 08:39:32PM +0200, Jean-Marc Lasgouttes wrote:
> Le 11/04/2021 à 15:41, Enrico Forestieri a écrit :
> > There is also this approach alternative to inheritFont:
> > https://www.lyx.org/trac/attachment/ticket/10263/10263-3.diff
> > but I am not motivated to work on it.
>
>
Le 11/04/2021 à 20:39, Jean-Marc Lasgouttes a écrit :
This is already set to true in the layout file. Note that I set it
explicitly to false for the \thanks case, but it does not seem necessary
anymore. This was ticket #2666. Can anyone confirm that \thanks allows
multiple paragraphs now and
Le 11/04/2021 à 15:41, Enrico Forestieri a écrit :
There is also this approach alternative to inheritFont:
https://www.lyx.org/trac/attachment/ticket/10263/10263-3.diff
but I am not motivated to work on it.
I'll try to go step by step.
First a simple question: why do you force allowMultiPar
count the work done by others.
>
> Of course. This is why I reverted and post a message here instead of trying
> things.
>
> First thing I would like to try: see what happens if InsetTabular inherits
> fonts. I have to create a document and see what changes.
>
> The footn
if InsetTabular
inherits fonts. I have to create a document and see what changes.
The footnote thing is obviously more complicated, but I would have to
check what the different calls to inheritFont do.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Sat, Apr 10, 2021 at 01:43:27PM +0200, Jean-Marc Lasgouttes wrote:
> Le 10/04/2021 à 10:46, Enrico Forestieri a écrit :
> > I think you reintroduced https://www.lyx.org/trac/ticket/10263
>
> Probably. I'll revert for now, but it is time to act and separate
> inheritFonts personalitities.
Le 10/04/2021 à 10:46, Enrico Forestieri a écrit :
I think you reintroduced https://www.lyx.org/trac/ticket/10263
Probably. I'll revert for now, but it is time to act and separate
inheritFonts personalitities. Exorcism or divorce, as you prefer.
JMarc
--
lyx-devel mailing list
On Fri, Apr 09, 2021 at 07:00:32PM +0200, Jean-Marc Lasgouttes wrote:
> commit 59f63602f5bc4a9dd3426761dceb9cb5aa4e656a
> Author: Jean-Marc Lasgouttes
> Date: Fri Apr 9 19:06:28 2021 +0200
>
> The foot inset does not inherit fonts
>
> Fixes bug #12238
>> Date: Sun Feb 14 06:08:36 2021 +0100
> >>
> >> DocBook: mark dates to disallow fonts inside.
> > Shouldn't this be the kind of task to be performed by layout2layout.py?
>
> Yes, probably. Thibaut, this should be reverted and replaced by a
> layout2
On 2/14/21 5:25 AM, Enrico Forestieri wrote:
> On Sun, Feb 14, 2021 at 06:05:12AM +0100, Thibaut Cuvelier wrote:
>> commit 5297862855f89ed44e62e7667e83b5fc1fd16e16
>> Author: Thibaut Cuvelier
>> Date: Sun Feb 14 06:08:36 2021 +0100
>>
>> DocBook: ma
On Sun, Feb 14, 2021 at 06:05:12AM +0100, Thibaut Cuvelier wrote:
> commit 5297862855f89ed44e62e7667e83b5fc1fd16e16
> Author: Thibaut Cuvelier
> Date: Sun Feb 14 06:08:36 2021 +0100
>
> DocBook: mark dates to disallow fonts inside.
Shouldn't this be the kind of task
On Thu, Jan 07, 2021 at 03:58:54PM -0500, Richard Kimberly Heck wrote:
> On 1/7/21 1:46 PM, Scott Kostyshak wrote:
> > On Wed, Jan 06, 2021 at 01:18:13AM -0500, Scott Kostyshak wrote:
> > > On current master, to reproduce open the French User Guide and without
> > >
On 1/7/21 1:46 PM, Scott Kostyshak wrote:
On Wed, Jan 06, 2021 at 01:18:13AM -0500, Scott Kostyshak wrote:
On current master, to reproduce open the French User Guide and without using
system fonts, compile with LuaTeX. It fails for me, although it passed a couple
of days ago.
Actually
On Wed, Jan 06, 2021 at 01:18:13AM -0500, Scott Kostyshak wrote:
> On current master, to reproduce open the French User Guide and without using
> system fonts, compile with LuaTeX. It fails for me, although it passed a
> couple of days ago.
Actually default output format (pdflatex) f
On current master, to reproduce open the French User Guide and without using
system fonts, compile with LuaTeX. It fails for me, although it passed a couple
of days ago.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org
On Wed, Dec 02, 2020 at 03:04:03PM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, dem 18.10.2020 um 12:16 -0400 schrieb Scott Kostyshak:
> > Starting with this commit, a "\normalsize" is added.
>
> Fixed.
Thanks,
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
Am Sonntag, dem 18.10.2020 um 12:16 -0400 schrieb Scott Kostyshak:
> Starting with this commit, a "\normalsize" is added.
Fixed.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Sun, Aug 02, 2020 at 09:47:45AM +0200, Juergen Spitzmueller wrote:
> commit aba8c81290a3c1f8faee7d9f6dbd214440dc523d
> Author: Juergen Spitzmueller
> Date: Sun Aug 2 10:12:19 2020 +0200
>
> Next attempt at correctly setting fonts in insets depending on
> inheritFont
On Thu, Sep 03, 2020 at 03:54:58PM -0400, Richard Kimberly Heck wrote:
> On 9/3/20 3:01 PM, Enrico Forestieri wrote:
> >
> > I would also like to backport the changes to the autocorrect file made
> > at 9bf8c873, 3b1ee921, 16d87a61, and 1df3151b. These are collected in
> > the attached patch.
> >
c9e08809c02bb3682ac50439d97951
>>>> Author: Enrico Forestieri
>>>> Date: Tue Sep 1 12:12:55 2020 +0200
>>>>
>>>> Adjust debug output for fonts
>>>>
>>>> This restores the debug output as it was intended before th
> >> Date: Tue Sep 1 12:12:55 2020 +0200
> >>
> >> Adjust debug output for fonts
> >>
> >> This restores the debug output as it was intended before the
> >> introduction of the LYXERR macro that was unconditionally outpu
On Thu, Sep 03, 2020 at 06:22:40PM +0200, Jean-Marc Lasgouttes wrote:
> Le 03/09/2020 ?? 17:32, Enrico Forestieri a écrit :
> >commit a9afdbb73c7ee568eeabd2848e9996322e4d5c85
> >Author: Enrico Forestieri
> >Date: Thu Sep 3 17:46:30 2020 +0200
> >
> > Persona
On 9/3/20 4:55 AM, Enrico Forestieri wrote:
> On Tue, Sep 01, 2020 at 11:54:46AM +0200, Enrico Forestieri wrote:
>> commit 8039b34802c9e08809c02bb3682ac50439d97951
>> Author: Enrico Forestieri
>> Date: Tue Sep 1 12:12:55 2020 +0200
>>
>>
On Tue, Sep 01, 2020 at 11:54:46AM +0200, Enrico Forestieri wrote:
> commit 8039b34802c9e08809c02bb3682ac50439d97951
> Author: Enrico Forestieri
> Date: Tue Sep 1 12:12:55 2020 +0200
>
> Adjust debug output for fonts
>
> This restores the debug output as i
On Tue, Jul 14, 2020 at 07:37:22PM +0200, Kornel Benko wrote:
> Am Tue, 14 Jul 2020 10:09:58 -0400
> schrieb Scott Kostyshak :
>
> > On Tue, Jul 14, 2020 at 03:50:09PM +0200, Jürgen Spitzmüller wrote:
> > > Am Dienstag, den 14.07.2020, 09:19 -0400 schrieb Scott Kostyshak:
> > > > To reproduce,
Am Tue, 14 Jul 2020 10:09:58 -0400
schrieb Scott Kostyshak :
> On Tue, Jul 14, 2020 at 03:50:09PM +0200, Jürgen Spitzmüller wrote:
> > Am Dienstag, den 14.07.2020, 09:19 -0400 schrieb Scott Kostyshak:
> > > To reproduce, do you have to type on the keyboard to filter the font
> > > when
On Tue, Jul 14, 2020 at 03:50:09PM +0200, Jürgen Spitzmüller wrote:
> Am Dienstag, den 14.07.2020, 09:19 -0400 schrieb Scott Kostyshak:
> > To reproduce, do you have to type on the keyboard to filter the font
> > when selecting?
> >
> > I see a problem when filtering and not with no filtering. I
Am Dienstag, den 14.07.2020, 09:19 -0400 schrieb Scott Kostyshak:
> To reproduce, do you have to type on the keyboard to filter the font
> when selecting?
>
> I see a problem when filtering and not with no filtering. I am not
> sure it is the same problem though. I cannot even do your last steps
.
> >
> > > What is your QT-Version (here 5.9.5)?
> >
> > 5.15.0.
> >
> > Jürgen
>
> Interesting. I tried also 5.14.0, but same result.
> The only workaround here is
> Select all tex-fonts
> [Apply]
> select all non-tex-fonts
> [OK]
en
Interesting. I tried also 5.14.0, but same result.
The only workaround here is
Select all tex-fonts
[Apply]
select all non-tex-fonts
[OK]
restart lyx, now all seems OK.
Other interesting thing is that the try to change the tex font (after setting
the
non-tex-font) shows the non-tex-fonts list.
Ther
Am Dienstag, den 14.07.2020, 12:27 +0200 schrieb Kornel Benko:
> You didn't forget to apply on each step?
No.
> What is your QT-Version (here 5.9.5)?
5.15.0.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Am Tue, 14 Jul 2020 12:27:23 +0200
schrieb Kornel Benko :
> Am Tue, 14 Jul 2020 11:08:08 +0200
> schrieb Jürgen Spitzmüller :
>
> > Am Dienstag, den 14.07.2020, 10:48 +0200 schrieb Kornel Benko:
> > > Master branch.
> > > New document
> > > Documen
Am Tue, 14 Jul 2020 11:08:08 +0200
schrieb Jürgen Spitzmüller :
> Am Dienstag, den 14.07.2020, 10:48 +0200 schrieb Kornel Benko:
> > Master branch.
> > New document
> > Document->Settings->Fonts
> > Select noto serif
> > Apply
> > Check non tex fonts i
Am Dienstag, den 14.07.2020, 10:48 +0200 schrieb Kornel Benko:
> Master branch.
> New document
> Document->Settings->Fonts
> Select noto serif
> Apply
> Check non tex fonts in "Document->Settings->Fonts"
> Select Noto Serif [GOOG]
> Apply
> Unc
Master branch.
New document
Document->Settings->Fonts
Select noto serif
Apply
Check non tex fonts in "Document->Settings->Fonts"
Select Noto Serif [GOOG]
Apply
Uncheck non tex fonts
Now the list for serif fonts is screwed (at least missing "noto serif")
Am Thu, 9 Jul 2020 11:22:38 +0200 (CEST)
schrieb Juergen Spitzmueller :
> commit 8cb9a6d3f6463321cdaf49a3cedb854b09c51275
> Author: Juergen Spitzmueller
> Date: Thu Jul 9 11:46:07 2020 +0200
>
> Add support for the libertinus family of fonts (#11899)
This must be a typo
Am Samstag, den 02.05.2020, 13:28 +0200 schrieb Kornel Benko:
> Sorry, too late for this mail. Already pushed. Should I move?
I see you did. Thanks!
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
Am Sat, 02 May 2020 13:22:39 +0200
schrieb Jürgen Spitzmüller :
> Am Samstag, den 02.05.2020, 13:13 +0200 schrieb Jürgen Spitzmüller:
> > Am Samstag, den 02.05.2020, 11:47 +0200 schrieb Kornel Benko:
> > > Is that an OK to commit?
> >
> > No objections from me.
>
> However, I think
Am Samstag, den 02.05.2020, 13:13 +0200 schrieb Jürgen Spitzmüller:
> Am Samstag, den 02.05.2020, 11:47 +0200 schrieb Kornel Benko:
> > Is that an OK to commit?
>
> No objections from me.
However, I think development/tools is more appropriate than lib/scripts
(the former has scripts for
Am Samstag, den 02.05.2020, 11:47 +0200 schrieb Kornel Benko:
> Is that an OK to commit?
No objections from me.
Jürgen
signature.asc
Description: This is a digitally signed message part
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Am Sat, 02 May 2020 08:43:39 +0200
schrieb Jürgen Spitzmüller :
> Am Freitag, den 01.05.2020, 20:35 -0400 schrieb Scott Kostyshak:
> > As for the implementation, I can look into QFontDatabase and see how
> > it
> > compares to the output from Kornel's script. If it is reliable, I can
> >
Am Freitag, den 01.05.2020, 20:35 -0400 schrieb Scott Kostyshak:
> As for the implementation, I can look into QFontDatabase and see how
> it
> compares to the output from Kornel's script. If it is reliable, I can
> understand Jürgen's point that there are advantages to that. On the
> other hand,
tant to get a useful subset of the
> > list
> > provided by lyx.
> > like get a list of fonts with Hebrew and German.
>
> I see. Makes sense (for this purpose).
I can take care of the GUI work if we decide to go forward with this and
we decide on the interface. Just to
Am Freitag, den 01.05.2020, 16:08 +0200 schrieb Kornel Benko:
> No GUI at the moment. (I am not good in programming GUI, as you
> probably know)
>
> For a tester it is sometimes important to get a useful subset of the
> list
> provided by lyx.
> like get a list of fonts with
t supposed to be used, then?
>
> Jürgen
No GUI at the moment. (I am not good in programming GUI, as you probably know)
For a tester it is sometimes important to get a useful subset of the list
provided by lyx.
like get a list of fonts with Hebrew and German.
$ listFontWithLang.p
Am Freitag, den 01.05.2020, 15:38 +0200 schrieb Kornel Benko:
> At a start, it is only for the devels. (that is it should not be
> included in the list of provided files)
So no GUI support? How is it supposed to be used, then?
Jürgen
signature.asc
Description: This is a digitally signed
Am Fri, 1 May 2020 09:27:55 -0400
schrieb Scott Kostyshak :
> On Fri, May 01, 2020 at 03:16:21PM +0200, Jürgen Spitzmüller wrote:
> > Am Freitag, den 01.05.2020, 14:59 +0200 schrieb Kornel Benko:
> > > In the struggle of gathering the relevant info from the fonts,
> >
Am Freitag, den 01.05.2020, 09:27 -0400 schrieb Scott Kostyshak:
> Regarding the questions about
> QFontDatabase and font-config, I don't know.
Both have access to the same font information. QFontDatabase does not
need an external script (and reconfiguring to update), and users do not
need to
On Fri, May 01, 2020 at 03:16:21PM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, den 01.05.2020, 14:59 +0200 schrieb Kornel Benko:
> > In the struggle of gathering the relevant info from the fonts,
> > I came up with a perl script, I would like to commit into
> > lib/script
Am Freitag, den 01.05.2020, 14:59 +0200 schrieb Kornel Benko:
> In the struggle of gathering the relevant info from the fonts,
> I came up with a perl script, I would like to commit into
> lib/scripts.
Why don't you use QFontDatabase to get this information? In any case,
if this is
In the struggle of gathering the relevant info from the fonts,
I came up with a perl script, I would like to commit into lib/scripts.
Following features are handled
1.) language: Select list of desired lang codes (lang1,lang2,... (e.g. de,ko))
2.) name: select list the font name should match
On Thu, Sep 05, 2019 at 07:47:02AM -, Guenter Milde wrote:
> On 2019-09-05, Scott Kostyshak wrote:
> > On Wed, Sep 04, 2019 at 08:37:57PM -, Guenter Milde wrote:
> >> On 2019-09-04, Scott Kostyshak wrote:
> >> > On Wed, Sep 04, 2019 at 03:04:35PM +0200, Kornel Benko wrote:
> >> >> Am
; > It is passing with 'Noto Sans Devanagari'
> >
> > However, as Noto Devenagari exists in two families, Serif and Sans
> > using Noto Sans Devenagari as "roman" font for Devenagari is not correct.
> >
> > In Debian, both "Noto * Devenagari&qu
; LaTeX.cpp (742): Log line: Check the spelling, where the font is installed
> > etc. etc.
>
>
> > It is passing with 'Noto Sans Devanagari'
>
> However, as Noto Devenagari exists in two families, Serif and Sans
> using Noto Sans Devenagari as "roman" font
On 2019-09-05, Scott Kostyshak wrote:
> On Wed, Sep 04, 2019 at 08:37:57PM -, Guenter Milde wrote:
>> On 2019-09-04, Scott Kostyshak wrote:
>> > On Wed, Sep 04, 2019 at 03:04:35PM +0200, Kornel Benko wrote:
>> >> Am Mittwoch, 4. September 2019, 12:02:02 CEST schrieb Guenter Milde:
>> >> >
On Wed, Sep 04, 2019 at 08:37:57PM -, Guenter Milde wrote:
> On 2019-09-04, Scott Kostyshak wrote:
> > On Wed, Sep 04, 2019 at 03:04:35PM +0200, Kornel Benko wrote:
> >> Am Mittwoch, 4. September 2019, 12:02:02 CEST schrieb Guenter Milde:
>
> >> > Please try the updated "supported-languages"
On 2019-09-04, Scott Kostyshak wrote:
> On Wed, Sep 04, 2019 at 03:04:35PM +0200, Kornel Benko wrote:
>> Am Mittwoch, 4. September 2019, 12:02:02 CEST schrieb Guenter Milde:
>> > Please try the updated "supported-languages" tests.
Here, I get
The following tests FAILED:
366 -
f Lao
>> >> >> > > Regular/OT:script=lao;l
>> >> >> >
>> >> >> > > I'm confused how this test passes for both Günter and Kornel,
>> >> >> > > but not me. I am using the noto fonts from the Ubuntu
>>
gari exists in two families, Serif and Sans
using Noto Sans Devenagari as "roman" font for Devenagari is not correct.
In Debian, both "Noto * Devenagari" fonts are part of the "fonts-noto-core"
package since "Debian/buster".
Alternatively, you can download from
https://noto-website-2.storage.googleapis.com/pkgs/NotoSerif-hinted.zip
and unpack into ~/.fonts .
Günter
>> > > There is no . in font Noto Serif Lao
> > >> >> > > Regular/OT:script=lao;l
> > >> >> >
> > >> >> > > I'm confused how this test passes for both Günter and Kornel,
> > >> >> > > but
> >> >> >
> >> >> > > I'm confused how this test passes for both Günter and Kornel,
> >> >> > > but not me. I am using the noto fonts from the Ubuntu
> >> >> > > packages. Perhaps you two are using newer versio
M -0400, Scott Kostyshak wrote:
>
> ...
>
> >> >> > > I still have a "Missing character" error as follows:
> >> >> >
> >> >> > > There is no . in font Noto Serif Lao
> >> >> > > Regular/OT:script=lao;l
>
"Missing character" error as follows:
>> >> >
>> >> > > There is no . in font Noto Serif Lao
>> >> > > Regular/OT:script=lao;l
>> >> >
>> >> > > I'm confused how this test passes for both Günter and Kornel,
>>
9fa556050bce1e594d2b0e592a5b3f
> > >> Author: Günter Milde
> > >> Date: Sun May 26 01:45:35 2019 +0200
> >
> > >> CJK package is never used with non-TeX fonts.
> >
> > >> Prepare for languages that use CJK with TeX fonts
te: Sun May 26 01:45:35 2019 +0200
>
> >> CJK package is never used with non-TeX fonts.
>
> >> Prepare for languages that use CJK with TeX fonts and Polyglossia
> >> with non-TeX fonts.
>
> >> Korean is already supported by Polyglossia
On 2019-08-21, Scott Kostyshak wrote:
> On Sun, May 26, 2019 at 01:41:42AM +0200, Günter Milde wrote:
>> commit c83765163f9fa556050bce1e594d2b0e592a5b3f
>> Author: Günter Milde
>> Date: Sun May 26 01:45:35 2019 +0200
>> CJK package is never used with non
On Sun, May 26, 2019 at 01:41:42AM +0200, Günter Milde wrote:
> commit c83765163f9fa556050bce1e594d2b0e592a5b3f
> Author: Günter Milde
> Date: Sun May 26 01:45:35 2019 +0200
>
> CJK package is never used with non-TeX fonts.
>
> Prepare for languages that u
this
> > format?
> >
> > To reproduce:
> >
> > 1. Open lib/doc/ru/Tutorial.lyx
> > 2. Document > Settings > Fonts > check "Use non-TeX fonts"
> > 3. View PDF (LuaTeX)
> >
> > I get the following error dialog:
> >
> > T
; 2. Document > Settings > Fonts > check "Use non-TeX fonts"
> 3. View PDF (LuaTeX)
>
> I get the following error dialog:
>
> The external program
> lualatex
> finished with an error. It is recommended you fix the cause of the external
> program's er
1 - 100 of 1756 matches
Mail list logo
