Re: 2.3.1-staging Has Been Merged

On 03/17/2018 10:28 PM, Scott Kostyshak wrote: > On Sat, Mar 17, 2018 at 08:01:58PM +, Richard Kimberly Heck wrote: >> Commits intended for 2.3.1 should now just go to 2.3.x, with my nod, as >> usual. Note that 2.3.2-staging is still live. > How did you do the merging? I'm surprised there was n

Re: 2.3.1-staging Has Been Merged

On Sat, Mar 17, 2018 at 08:01:58PM +, Richard Kimberly Heck wrote: > Commits intended for 2.3.1 should now just go to 2.3.x, with my nod, as > usual. Note that 2.3.2-staging is still live. How did you do the merging? I'm surprised there was no merge commit. Was that because it could be rebased

Re: Trac Links to HTTPS

On Sat, Mar 17, 2018 at 08:44:52PM +, Richard Kimberly Heck wrote: > Please let me know if there are any problems. In brief testing, it works well! Thanks, Scott signature.asc Description: PGP signature

Re: Tarballs for 2.2.4

On Sat, Mar 17, 2018 at 06:13:06PM +, Richard Kimberly Heck wrote: > Sources for LyX 2.2.4 are available here: > >     ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/ > > Please let me know if you have any problems with them. And please > prepare binaries. I'll release when they are ready. Compiles

Re: Windows Installer: Future Issues

On Sat, Mar 17, 2018 at 06:15:20PM +, Jürgen Spitzmüller wrote: > Am Donnerstag, den 15.03.2018, 15:08 -0400 schrieb Scott Kostyshak: > > > Leaving 2.2.3 as it is? > > > > Yes I think so. > > I suggest to hide the text mentioning the two installer variants (and > pointing to 2.2.3). It proba

Re: moderation

Le 16/03/2018 à 15:21, mike a écrit : Hello Can someone tell me if this list is moderated please? Hi Mike, No it is not. JMarc

Re: Trac Links to HTTPS

On 02/22/2018 04:24 PM, Jean-Marc Lasgouttes wrote: > Le 22/02/2018 à 20:59, Richard Heck a écrit : >> Do we necessarily want to do that? I'm not sure why someone would prefer >> to access via http instead of https, but I'm also not sure why we >> shouldn't >> permit them to do so, if they so wish.

2.3.1-staging Has Been Merged

Commits intended for 2.3.1 should now just go to 2.3.x, with my nod, as usual. Note that 2.3.2-staging is still live. Richard

Re: r41181 - www-user/trunk/farm/cookbook/LyX

On 03/17/2018 02:29 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 17.03.2018, 18:53 +0100 schrieb rgh...@lyx.org: >> Author: rgheck >> Date: Sat Mar 17 18:53:03 2018 >> New Revision: 41181 >> URL: http://www.lyx.org/trac/changeset/41181 >> >> Log: >> * i18n.inc: update stats >> >> Modified: >>

Re: r41181 - www-user/trunk/farm/cookbook/LyX

Am Samstag, den 17.03.2018, 18:53 +0100 schrieb rgh...@lyx.org: > Author: rgheck > Date: Sat Mar 17 18:53:03 2018 > New Revision: 41181 > URL: http://www.lyx.org/trac/changeset/41181 > > Log: > * i18n.inc: update stats > > Modified: >www-user/trunk/farm/cookbook/LyX/i18n.inc > > Modified: ww

Re: Windows Installer: Future Issues

Am Donnerstag, den 15.03.2018, 15:08 -0400 schrieb Scott Kostyshak: > > Leaving 2.2.3 as it is? > > Yes I think so. I suggest to hide the text mentioning the two installer variants (and pointing to 2.2.3). It probably irritates more than it helps, see http://www.lyx.org/trac/ticket/11079 The 2.

Tarballs for 2.2.4

Sources for LyX 2.2.4 are available here:     ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/ Please let me know if you have any problems with them. And please prepare binaries. I'll release when they are ready. Richard

2.2.x Closed

The 2.2.x branch is now closed so I can prepare the release of 2.2.4. I'll send another note when binaries are available. Richard

Re: [LyX/master] tex2lyx: complete minted support (inputminted)

On 03/17/2018 11:48 AM, Jürgen Spitzmüller wrote: > Am Samstag, den 17.03.2018, 16:45 +0100 schrieb Juergen Spitzmueller: >> commit f3c5bcd2be4edc37dec4c78422f31e07b322b298 >> Author: Juergen Spitzmueller >> Date: Sat Mar 17 16:44:09 2018 +0100 >> >> tex2lyx: complete minted support (inputmi

Re: [LyX/master] tex2lyx: complete minted support (inputminted)

Am Samstag, den 17.03.2018, 16:45 +0100 schrieb Juergen Spitzmueller: > commit f3c5bcd2be4edc37dec4c78422f31e07b322b298 > Author: Juergen Spitzmueller > Date: Sat Mar 17 16:44:09 2018 +0100 > > tex2lyx: complete minted support (inputminted) > > Also fix some whitespace issues in mi

Re: Native support for Charter font from XCharter package

As I understand Jürgen already fixed this issue. Are there any docs, I should read to account all these details when adding new fonts? On 15.03.2018 19:40, Kornel Benko wrote: > Am Donnerstag, 15. März 2018 17:09:27 CET schrieb Jürgen Spitzmüller > : >> 2018-03-15 17:05 GMT+01:00 Guenter Milde: >

Re: Native support for Charter font from XCharter package

Recently I've added a table with TeX fonts, that have good Cyrillic support, to the wiki: https://wiki.lyx.org/Tips/Cyrillic. It can be useful in this case. On 15.03.2018 19:38, Kornel Benko wrote: > Am Donnerstag, 15. März 2018 15:47:00 CET schrieb Jürgen Spitzmüller > : >> 2018-03-15 15:23 GMT+

Re: Native support for Charter font from XCharter package

Thank you for committing. You're right, that name will be better. On 15.03.2018 16:47, Jürgen Spitzmüller wrote: > 2018-03-15 15:23 GMT+01:00 Jürgen Spitzmüller >: > > 2018-03-15 8:54 GMT+01:00 Yuriy Skalko: > > In attached patch I've implemented support for Ch

Re: Update on 2.3.0 situation and Windows-specific issues

On Fri, Mar 16, 2018 at 8:31 PM, Scott Kostyshak wrote: > > Thanks for those arguments, Joel. You make good points. However, I think > we should still go forward with the release. Understood, and as I said: I held unpopular opinions. If I felt strongly, I would have contributed these thoughts

Re: svgz files used in main IPA toolbar

Am Samstag, den 17.03.2018, 09:25 + schrieb mike: > This is really just a question out of curiosity. Where did they > come > from? I can't find anything like them on the IPA website > (https://www.internationalphoneticassociation.org/content/ipa-fonts). > > Were they lifted from the tipa

svgz files used in main IPA toolbar

Hello This is really just a question out of curiosity.  Where did they come from?  I can't find anything like them on the IPA website (https://www.internationalphoneticassociation.org/content/ipa-fonts). Were they lifted from the tipa package? Mike -- I *AM* a unique and special snowflake

Re: entering Unicode code points directly in ipa inset

Am Samstag, 17. März 2018 09:02:16 CET schrieb mike : > Hello > > So I've read "Using LyX to Display Phonetic Characters (IPA)" > (https://wiki.lyx.org/LyX/LinguistLyX#toc4) specifically about the > different ways of entering glyphs, etc. with the IPA inset but what > still isn't clear to me is ho

entering Unicode code points directly in ipa inset

Hello So I've read "Using LyX to Display Phonetic Characters (IPA)" (https://wiki.lyx.org/LyX/LinguistLyX#toc4) specifically about the different ways of entering glyphs, etc. with the IPA inset but what still isn't clear to me is how I enter a code point like 0x0298 directly using the IPA ins