Re: 2.3.1-staging Has Been Merged

[Richard Kimberly Heck]

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 no merge commit. Was
> that because it could be rebased? I'm just curious.

Yes, I rebased before merging. Magic, that.

Richard

Re: 2.3.1-staging Has Been Merged

[Scott Kostyshak]

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? I'm just curious.

Scott


signature.asc
Description: PGP signature

Re: Trac Links to HTTPS

[Scott Kostyshak]

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

[Scott Kostyshak]

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 and works well in brief testing.

Ubuntu 16.04.

Scott


signature.asc
Description: PGP signature

Re: Windows Installer: Future Issues

[Scott Kostyshak]

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 probably irritates more than it helps, see
> http://www.lyx.org/trac/ticket/11079

I agree that the current text is confusing. I wonder if we can improve
on the confusion by just saying something like

Unfortunately, official LyX 2.3.0 Windows binaries are not available
at this time. The most recent LyX release that has official Windows
binaries is 2.2.3. There are 2 Windows installer variants:

I will make that change.

If you think that it is still too confusing, and other developers also
agree that we should hide that text, I can be convinced.

> The 2.2.3 binaries are still reachable, after all, via "Previous
> versions".

But that requires a few extra clicks.

> I'd also keep the link to the LyX for Windows wiki page, where Uwe or
> somebody else might add information should there be "inofficial"
> binaries we do not want to officially list on the website.

Agreed.

Scott


signature.asc
Description: PGP signature

Re: moderation

[Jean-Marc Lasgouttes]

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

[Richard Kimberly Heck]

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. This would also provide some kind
>> of protection against https failures.
>
> That would help when I click on one of those old links sent by trac
> notifications.
>
> Google.com or mozilla.org do redirect to https.

https redirects have now been established for lyx.org, wiki.lyx.org, and
git.lyx.org.
Please let me know if there are any problems.

Richard

2.3.1-staging Has Been Merged

[Richard Kimberly Heck]

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

[Richard Kimberly Heck]

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:
>>www-user/trunk/farm/cookbook/LyX/i18n.inc
>>
>> Modified: www-user/trunk/farm/cookbook/LyX/i18n.inc
>> =
>> =
>> --- www-user/trunk/farm/cookbook/LyX/i18n.incSat Mar 17
>> 17:14:43 2018(r41180)
>> +++ www-user/trunk/farm/cookbook/LyX/i18n.incSat Mar 17
>> 18:53:03 2018(r41181)
>> @@ -1,105 +1,105 @@
>>  >  // The current version
>> -$lyx_version = "2.2.4dev";
>> +$lyx_version = "2.2.4";
>>  // The branch tag
>>  $branch_tag = "master";
> The stats are not up to date (a8e1102dd63 is missing). Also, the
> $branch_tag should be "2.2.x" (not "master"). But then, this page
> should now cover 2.3.0 anyway ($branch_tag = "2.3.x"), shouldn't it?

I'll remerge from 2.3.x.

Richard

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

[Jürgen Spitzmüller]

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: www-user/trunk/farm/cookbook/LyX/i18n.inc
> =
> =
> --- www-user/trunk/farm/cookbook/LyX/i18n.inc Sat Mar 17
> 17:14:43 2018 (r41180)
> +++ www-user/trunk/farm/cookbook/LyX/i18n.inc Sat Mar 17
> 18:53:03 2018 (r41181)
> @@ -1,105 +1,105 @@
>// The current version
> -$lyx_version = "2.2.4dev";
> +$lyx_version = "2.2.4";
>  // The branch tag
>  $branch_tag = "master";

The stats are not up to date (a8e1102dd63 is missing). Also, the
$branch_tag should be "2.2.x" (not "master"). But then, this page
should now cover 2.3.0 anyway ($branch_tag = "2.3.x"), shouldn't it?

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Windows Installer: Future Issues

[Jürgen Spitzmüller]

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.2.3 binaries are still reachable, after all, via "Previous
versions".

I'd also keep the link to the LyX for Windows wiki page, where Uwe or
somebody else might add information should there be "inofficial"
binaries we do not want to officially list on the website.

Jürgen


signature.asc
Description: This is a digitally signed message part

Tarballs for 2.2.4

[Richard Kimberly Heck]

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

[Richard Kimberly Heck]

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)

[Richard Kimberly Heck]

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 (inputminted)
>> 
>> Also fix some whitespace issues in minted inset import.
> Again, candidate for 2.3.2-staging.

OK.

Richard

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

[Jürgen Spitzmüller]

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 minted inset import.

Again, candidate for 2.3.2-staging.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Native support for Charter font from XCharter package

[Yuriy Skalko]

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:
>>> From my first glance at the patch it seems that lyx2lyx support is
>>> missing.
>>
>> No it's there.
>>
>> Jürgen
>>
>>> Günter
> 
> These lyx2lyx tests fail:
> The following tests FAILED:
>   1411 - export/export/lyx2lyx/lyx_2_0_test_lyx16 (Failed)
>   1412 - export/export/lyx2lyx/lyx_2_0_test_lyx21 (Failed)
>   1413 - export/export/lyx2lyx/lyx_2_0_test_lyx22 (Failed)
>   1414 - export/export/lyx2lyx/lyx_2_1_test_lyx16 (Failed)
>   1415 - export/export/lyx2lyx/lyx_2_1_test_lyx21 (Failed)
>   1416 - export/export/lyx2lyx/lyx_2_1_test_lyx22 (Failed)
>   1417 - export/export/lyx2lyx/lyx_2_2_test_lyx16 (Failed)
>   1418 - export/export/lyx2lyx/lyx_2_2_test_lyx21 (Failed)
>   1419 - export/export/lyx2lyx/lyx_2_2_test_lyx22 (Failed)
> Errors while running CTest
> 
>   Kornel
> 

Re: Native support for Charter font from XCharter package

[Yuriy Skalko]

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+01:00 Jürgen Spitzmüller :
>>> 2018-03-15 8:54 GMT+01:00 Yuriy Skalko:
 In attached patch I've implemented support for Charter font from
 XCharter package.
>>>
>>> This looks very good, thank you. One minor thing: I wonder whether the
>>> GuiName shouldn't be "Bitstream Charter (XCharter)" rather than "Charter
>>> (XCharter)" only in line with the already existing two Bitstream Charter
>>> variants.
>>
>> I did this one change and committed your patch.
>>
>> Jürgen
> 
> BTW, XCharter is missing in LatexConfig.lyx.
> 
> From my POV, we will need some grouping for the supported fonts.
> Like Hebrew, Cyrillic, Latin, Korean(Hangul), Japanese, Chinese, Arabic, 
> Farsi, Hindi ...
> 
>   Kornel
> 

Re: Native support for Charter font from XCharter package

[Yuriy Skalko]

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 Charter font from
> XCharter package.
> 
> 
> This looks very good, thank you. One minor thing: I wonder whether
> the GuiName shouldn't be "Bitstream Charter (XCharter)" rather than
> "Charter (XCharter)" only in line with the already existing two
> Bitstream Charter variants.
> 
> 
> I did this one change and committed your patch.
> 
> Jürgen
>  
> 

Re: Update on 2.3.0 situation and Windows-specific issues

[Joel Kulesza]

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 earlier.  What I'm happiest about,
in the short term, is the constructive dialog.  In the longer term, it's
been a treat to watch a culturally diverse and globally distributed
development team maintain, continue to develop, and release a significant
piece of software.


> As for what to tell your colleagues, that is up to you. I'm planning to
> tell anyone who asks that there are unofficial binaries available that
> are made by a LyX developer, that have been tested and that work well,
> and I will then mention in some way (perhaps using the same text as in
> the dialog that we're discussing) that the installer will automatically
> update their MiKTeX installation.


Understood, and perhaps I missed the plan that "unofficial" ones are still
being made available.  That makes the situation more palatable while a
complete solution is sought.

Thanks,
Joel

Re: svgz files used in main IPA toolbar

[Jürgen Spitzmüller]

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 package?

Handmade.

Jürgen

> 
> Mike
> 

signature.asc
Description: This is a digitally signed message part

svgz files used in main IPA toolbar

[mike]

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

[Kornel Benko]

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 how I enter a code point like 0x0298 directly
> using the IPA inset (bilabial click that appears second on the left on
> the main IPA toolbar).  Is there a way to do this?  Also is there a way
> to enter more than one at the same time in the same inset?
> 
> I wasn't sure whether I should post this here or on lyx-users. Apologies
> if I got it wrong.
> 
> Thanks very much in advance for any help
> 
> Mike

What about
M-x unicode-insert 0x0298
?

Kornel


signature.asc
Description: This is a digitally signed message part.

entering Unicode code points directly in ipa inset

[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 how I enter a code point like 0x0298 directly 
using the IPA inset (bilabial click that appears second on the left on 
the main IPA toolbar).  Is there a way to do this?  Also is there a way 
to enter more than one at the same time in the same inset?


I wasn't sure whether I should post this here or on lyx-users. Apologies 
if I got it wrong.


Thanks very much in advance for any help

Mike

--
I *AM* a unique and special snowflake