Re: Update on 2.3.0 situation and Windows-specific issues

[Uwe Stöhr]

Am 15.03.2018 um 18:29 schrieb Richard Heck:


I was talking about whether anything would happen *as a result of
someone running
the installer*. I understand that there are *other* ways that the MiKTeX
installation can
be damaged, as happened to your mother. That is a really horrible MiKTeX
bug, and
there is nothing we can do about it.


Yes, that is exactly the case.
I fully agree that it is not the task of an installer to change existing 
installations if not really necessary. In this case however, I think 
this is necessary. Users don't even running an installer can end up with 
in a state where they cannot compile any LyX document.
Therefore the LyX 2.3.0 installer needs to trigger the package 
management update. Only this way it is possible to repair broken MiKTeX 
systems. So users end up being lost can use the LyX 2.3.0 installer to 
get back to work. Therefore my plan is to implement the repair mechanism 
in the installer for 2.2.4 too.


The installer for 2.3.1 will be the normal one not touching the package 
handling system. So at least we can provide one installer repairing 
things.  So if users e.g. don't update LyX for a long time but run into 
problems, could then use the 2.3.0 installer and install the current 
2.3.x afterwards.



I decided that I cannot stand for an installer that can send many
users into serious
troubles despite I know a way to prevent this.


The only issue here is: Do we add a dialog of the sort in question? The
installer with
that dialog cannot cause any new problems, because either: (1) the
person installs LyX
and it updates MiKTeX just as you want; (2) the person does not install
LyX, in which
case they are in the same situation they were before, because the
installer was a no-op.


That is my point. Users like e.g. my mother (who can read English but 
are not very good at it) might misunderstand the dialog and deny the 
update. Therefore they don't get the new LyX and, moreover, the 
probability is high that they end up with a screwed-up LaTeX some weeks 
later.
English is an important point here in my opinion because in such a short 
time I cannot manage to get the dialog properly translated. So e.g. 
German users get the installer in German except of the dialog you want. 
This makes it even more difficult to understand what the dialog is 
about. I also think that a dialog is not sufficient to explain all the 
details/reasons behind it. (Personally I also don't like that I have to 
issue a dialog to assure people keep the installer open until it is 
finished, because non-native speakers will have problems to understand it.)



The installer for LyX 2.3.1 will return to the old behavior.


Why? Won't that just break the installations of people still using 2.2.3?


We can add a sentence in the announcement text of LyX 2.3.1 that people 
should use the 2.3.0 installer first to avoid problems. And if users did 
not mention it and ask for help we can send them the link to the 2.3.0 
installer.
So my plan is to use the 2.3.0 installer also as repair kit. Why 2.3.? 
Because every LyX 2.3.x release can be installed over an existing 2.3.0 
installation. This installer feature is major a goal. So if this is not 
possible, there is a bug in the installer I will fix.


I am currently traveling, so please excuse delays in my responses.

regards Uwe

Re: Update on 2.3.0 situation and Windows-specific issues

[Scott Kostyshak]

On Thu, Mar 15, 2018 at 05:29:30PM +, Richard Heck wrote:

> > The installer for LyX 2.3.1 will return to the old behavior. 
> 
> Why? Won't that just break the installations of people still using 2.2.3?

I'm also confused by this. Maybe he means that in the case that an
installation of LyX 2.3.0 is detected, the 2.3.1 installer would not
need to update MiKTeX.

Scott


signature.asc
Description: PGP signature

Re: Windows Installer: Future Issues

[Scott Kostyshak]

On Thu, Mar 15, 2018 at 08:28:44AM +, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > > I agree. I will remove the Windows binaries from the FTP, and announce
> > > 2.3.0 on Friday.
> > 
> > For the announce email I'm currently planning to put something like the
> > following:
> > 
> >   Unfortunately, official Windows binaries are not available at this
> >   time.
> 
> What you plan to do with Windows section in Download page?
> Leaving 2.2.3 as it is?

Yes I think so. After the text "There are 2 Windows installer
variants:", I think we could add the similar (adding just the version
info) text as in the announcement:

  Unfortunately, official LyX 2.3.0 Windows binaries are not available
  at this time.

Should we attempt to clarify the text in order to account for the
availability of Cygwin binaries? i.e. one might consider Cygwin binaries
to be "Windows binaries", and Cygwin binaries for 2.3.0 are available.
My current opinion is to not worry about that, but I'm open.

Any other suggestions?

Scott


signature.asc
Description: PGP signature

Re: Native support for Charter font from XCharter package

[Kornel Benko]

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



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

Re: Native support for Charter font from XCharter package

[Kornel Benko]

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


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

Re: Update on 2.3.0 situation and Windows-specific issues

[Richard Heck]

On 03/15/2018 11:45 AM, Uwe Stöhr wrote:
> Am 14.03.2018 um 04:31 schrieb Richard Heck:
>
>> If this dialog is popped at the very beginning of the installation,
>> before ANYTHING is actually done, then it is impossible that the
>> MiKTeX installation
>> should be affected.
>
> This is not true and I don't get why I cannot make this clear to you.

I was talking about whether anything would happen *as a result of
someone running
the installer*. I understand that there are *other* ways that the MiKTeX
installation can
be damaged, as happened to your mother. That is a really horrible MiKTeX
bug, and
there is nothing we can do about it.

> I decided that I cannot stand for an installer that can send many
> users into serious
> troubles despite I know a way to prevent this.

The only issue here is: Do we add a dialog of the sort in question? The
installer with
that dialog cannot cause any new problems, because either: (1) the
person installs LyX
and it updates MiKTeX just as you want; (2) the person does not install
LyX, in which
case they are in the same situation they were before, because the
installer was a no-op.
Granted, they might screw up their MiKTeX installation eventually, but
that is a
MiKTeX bug and ought to be dealt with at that level.

> The installer for LyX 2.3.1 will return to the old behavior. 

Why? Won't that just break the installations of people still using 2.2.3?

Richard

Re: Native support for Charter font from XCharter package

[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
>
>

Re: Native support for Charter font from XCharter package

[Guenter Milde]

On 2018-03-15, Jürgen Spitzmüller wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> 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.

>From my first glance at the patch it seems that lyx2lyx support is missing.

Günter

Re: Update on 2.3.0 situation and Windows-specific issues

[Uwe Stöhr]

Am 14.03.2018 um 04:31 schrieb Richard Heck:


If this dialog is popped at the very beginning of the installation,
before ANYTHING
is actually done, then it is impossible that the MiKTeX installation
should be affected.


This is not true and I don't get why I cannot make this clear to you.

Maybe another example: My mother called me today. She uses LyX 2.2.3. I 
sent her a document I wrote the last days to proof-read. I don't know 
what triggered her problem, but she ended up with a broken LaTeX not 
able to compile any LyX document any longer. Maybe she had not all 
packages installed I use in the document.
However, the exact cause is not important. She did not use any 
installer. As I wrote, users just using LyX 2.2.x can screw up their 
LaTeX and I experienced this by myself.
I sent here the link to the 2.3.0 installer and it worked: the solution 
proposed by the MiKTeX developer repaired her system. So she uses now 
LyX 2.3.0 and it works for her and I am happy. This solution needs the 
updated package handling system.


As I wrote now a dozen times, the installer for 2.3.0 will be an 
exception. I have to assure that LyX users don't end up lost. 
Experienced users can be informed by two sentences in the release 
announcement. Average users cannot have the choice to deny the package 
update because if they leave their system untouched they can screw up 
their system sooner or later.

The installer for LyX 2.3.1 will return to the old behavior.

I reacted so pissed-off because I get the feeling that you and others 
don't trust me "a single meter" as we say in German that I decided the 
right thing. I made a decision because I believe this is the best for 
most users. I am also not happy that I had to change the installer's 
default behavior but it is like it is.



I am talking about average users and my mother is a good example. She 
was lost with her screwed-up LaTeX. She doesn't know anything about 
packages, dependencies, commands etc. Well, average users are just 
users. For example she became a Gimp master surprising me quite often 
but she doesn't know anything about color models, Gimp plugins etc.. 
That should not prevent users from using a program.


If I am no longer allowed to assure that average users like my mother 
get a fully functional LyX, it makes no sense for me to provide an 
installer any longer.



Please let's end the debate. I decided that I cannot stand for an 
installer that can send many users into serious troubles despite I know 
a way to prevent this.

If you don't trust me, turn on your Windows PCs and try it out by yourself.
If you don't have experiences with LyX users without knowledge of 
packages, LaTeX etc, under Windows please stop claiming what is good for 
them.
If you don't trust me at all or think I do evil things, provide your own 
installer or don't release LyX for Windows.


I have currently other problems to deal with than LyX. I already spent 
too much time with the installer because of the MiKTeX problem.


regards Uwe

Re: Native support for Charter font from XCharter package

[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

Re: Native support for Charter font from XCharter package

[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.

Jürgen


>
> Regards,
> Yuriy
>

Re: Update on 2.3.0 situation and Windows-specific issues

[racoon]

On 15.03.2018 04:13, Scott Kostyshak wrote:

On Wed, Mar 14, 2018 at 01:48:02AM +, Uwe Stöhr wrote:


Why don't you add a sentence or two to the release notes for the experienced
users that they can set in MiKTeX "never" to package updates. Experienced
users will understand this. That is the most suitable solution.


I think a dialog is more appropriate, because problems from upgrading
MiKTeX could affect anyone, not just experienced users.


I tend to agree. However, maybe the dialog should state only true things?

So, either it should come up only when the 'never' option isn't set 
(preferably), or indicate that


* MiKTeX will be updated (unless 'Install missing packages on-the-fly' 
is set to 'never')


I know, that makes things worse in one respect (complicating the dialog)...

Daniel

Re: popup IPA toolbar

[mike]

On 14/03/2018 18:59, mike wrote:

On 14/03/2018 18:45, Richard Heck wrote:

On 03/14/2018 01:19 PM, mike wrote:

On 14/03/2018 16:55, Jürgen Spitzmüller wrote:
2018-03-14 17:43 GMT+01:00 mike >:


Is there anything else I need to know on this general topic
because I intend to do some serious work using all this?


If you mean work as in "using the feature", then no. I suppose you 
have read Help > Specific Manuals > Linguistics, and you are aware 
of the wiki page http://wiki.lyx.org/LyX/LinguistLyX ?


Jürgen


Thank you very very much.  This is all totally brilliant.  Is this 
all documented in one place?  It should be.  I did look at the 
manual and the wiki but if the content of today's discussion is all 
in one place in either of them I missed it which is entirely 
possible.  Whoever developed all this is a genius/are geniuses.  I 
have to think it had to be you you are so knowledgeable about it 
all.  As for your answer to my question 'If you mean work as in 
"using the feature", then no' that's really all I need to know.  
Thanks again for all your help and especially your patience.


Yes, Jürgen did the work on IPA and a lot of the lingusitics modules. 
And yes, it's damn good work.


If there is something here that you think should be documented in one 
place, then probably the wiki would be a good place to put it. 
User-written documentation is a great thing, because it really 
reflects the experience of someone who was coming at this stuff cold.


Richard


Hi Richard

I may just do that if for no other reason than to have it all 
documented in one place for my own purposes.  But the wiki being a 
wiki others could improve on it which would also be a good thing.


Thank you for your comment on Jurgen's work and the suggestion.

Best

Mike

--
I *AM* a unique and special snowflake



--
I *AM* a unique and special snowflake

Re: Windows Installer: Future Issues

[Pavel Sanda]

Scott Kostyshak wrote:
> > I agree. I will remove the Windows binaries from the FTP, and announce
> > 2.3.0 on Friday.
> 
> For the announce email I'm currently planning to put something like the
> following:
> 
>   Unfortunately, official Windows binaries are not available at this
>   time.

What you plan to do with Windows section in Download page?
Leaving 2.2.3 as it is?

Pavel

Re: popup IPA toolbar

[Jürgen Spitzmüller]

Am 14.03.2018 6:19 nachm. schrieb "mike"

Thank you very very much.  This is all totally brilliant.  Is this all
documented in one place?  It should be.  I did look at the manual and the
wiki but if the content of today's discussion is all in one place in either
of them I missed it which is entirely possible.  Whoever developed all this
is a genius/are geniuses.  I have to think it had to be you you are so
knowledgeable about it all.  As for your answer to my question 'If you mean
work as in "using the feature", then no' that's really all I need to know.
Thanks again for all your help and especially your patience.


Thanks for the feedback. I am glad it is useful. Suggestions for
improvements are always appreciated.

Best
Jürgen


Very best


Mike

-- 
I *AM* a unique and special snowflake



-- 
I *AM* a unique and special snowflake

Re: Windows Installer: Future Issues

[Jürgen Spitzmüller]

Am 15.03.2018 4:12 vorm. schrieb "Scott


I still have the hope that we can upload the Windows binaries soon.


I certainly hope so, too!

Jürgen


Scott

Native support for Charter font from XCharter package

[Yuriy Skalko]

Hello,

In attached patch I've implemented support for Charter font from
XCharter package.

Regards,
Yuriy
From eb04379f6b0ac86733d8f0baddcff81c009ab4d6 Mon Sep 17 00:00:00 2001
From: Yuriy Skalko 
Date: Thu, 15 Mar 2018 09:34:56 +0200
Subject: [PATCH] Support Charter font from XCharter package

---
 development/FORMAT  |  3 +++
 lib/chkconfig.ltx   |  1 +
 lib/latexfonts  |  6 ++
 lib/lyx2lyx/lyx_2_4.py  | 15 ++-
 src/tex2lyx/Preamble.cpp|  8 +++-
 src/tex2lyx/test/CJK.lyx.lyx|  2 +-
 src/tex2lyx/test/CJKutf8.lyx.lyx|  2 +-
 src/tex2lyx/test/DummyDocument.lyx.lyx  |  2 +-
 src/tex2lyx/test/Dummy~Document.lyx.lyx |  2 +-
 src/tex2lyx/test/XeTeX-polyglossia.lyx.lyx  |  2 +-
 src/tex2lyx/test/algo2e.lyx.lyx |  2 +-
 src/tex2lyx/test/box-color-size-space-align.lyx.lyx |  2 +-
 src/tex2lyx/test/test-insets-basic.lyx.lyx  |  2 +-
 src/tex2lyx/test/test-insets.lyx.lyx|  2 +-
 src/tex2lyx/test/test-memoir.lyx.lyx|  2 +-
 src/tex2lyx/test/test-minted.lyx.lyx|  2 +-
 src/tex2lyx/test/test-modules.lyx.lyx   |  2 +-
 src/tex2lyx/test/test-refstyle-theorems.lyx.lyx |  2 +-
 src/tex2lyx/test/test-scr.lyx.lyx   |  2 +-
 src/tex2lyx/test/test-structure.lyx.lyx |  2 +-
 src/tex2lyx/test/test.lyx.lyx   |  2 +-
 src/tex2lyx/test/verbatim.lyx.lyx   |  2 +-
 src/version.h   |  4 ++--
 23 files changed, 50 insertions(+), 21 deletions(-)

diff --git a/development/FORMAT b/development/FORMAT
index a57d3ed66c..e907e98a5d 100644
--- a/development/FORMAT
+++ b/development/FORMAT
@@ -7,6 +7,9 @@ changes happened in particular if possible. A good example 
would be
 
 ---
 
+2018-03-14 Yuriy Skalko 
+   * Format incremented to 547: support for Charter font from XCharter 
package
+
 2018-03-10 Uwe Stöhr 
* Format incremented to 546: support for ParaType fonts.
  - \usepackage{PTSerif} > \font_roman "PTSerif-TLF"
diff --git a/lib/chkconfig.ltx b/lib/chkconfig.ltx
index 0aa948c840..e4ba2edce8 100644
--- a/lib/chkconfig.ltx
+++ b/lib/chkconfig.ltx
@@ -480,6 +480,7 @@
 \TestPackage{tipx}
 \TestPackage{tone}
 \TestPackage{txfonts}% For the txtt monospaced font
+\TestPackage{XCharter}
 % symbol packages supported by LyX for items and the special character dialog
 % see the unicodesymbols file
 \TestPackage{ascii}
diff --git a/lib/latexfonts b/lib/latexfonts
index 307b10e5e9..c31e7fa5f3 100644
--- a/lib/latexfonts
+++ b/lib/latexfonts
@@ -460,6 +460,12 @@ AltFont futj
SwitchDefault1
 EndFont
 
+Font xcharter
+   GuiName "Charter (XCharter)"
+   Family  rm
+   Package XCharter
+   OsfOption   osf
+EndFont
 
 #
 # SANS SERIF FONTS
diff --git a/lib/lyx2lyx/lyx_2_4.py b/lib/lyx2lyx/lyx_2_4.py
index 536bf106d9..377f6e7e18 100644
--- a/lib/lyx2lyx/lyx_2_4.py
+++ b/lib/lyx2lyx/lyx_2_4.py
@@ -126,6 +126,17 @@ def revert_paratype(document):
 else:
add_to_preamble(document, ["\\usepackage{PTMono}"])
 
+
+def revert_xcharter(document):
+" Revert XCharter font definitions to LaTeX "
+
+if find_token(document.header, "\\use_non_tex_fonts false", 0) != -1:
+preamble = ""
+i1 = find_token(document.header, "\\font_roman \"xcharter\"", 0)
+if i1 != -1:
+add_to_preamble(document, ["\\usepackage{XCharter}"])
+
+
 ##
 # Conversion hub
 #
@@ -133,10 +144,12 @@ def revert_paratype(document):
 supported_versions = ["2.4.0", "2.4"]
 convert = [
[545, [convert_lst_literalparam]],
-   [546, []]
+   [546, []],
+   [547, []]
   ]
 
 revert =  [
+   [546, [revert_xcharter]],
[545, [revert_paratype]],
[544, [revert_lst_literalparam]]
   ]
diff --git a/src/tex2lyx/Preamble.cpp b/src/tex2lyx/Preamble.cpp
index 247422e223..b6c0454299 100644
--- a/src/tex2lyx/Preamble.cpp
+++ b/src/tex2lyx/Preamble.cpp
@@ -144,7 +144,7 @@ const char * const known_roman_fonts[] = { "ae", 
"beraserif", "bookman",
 "ccfonts", "chancery", "charter", "cmr", "cochineal", "crimson", "fourier",
 "garamondx", "libertine", "libertineRoman", "libertine-type1", "lmodern", 
"mathdesign", "mathpazo",
 "mathptmx", "MinionPro", "newcent", "NotoSerif-TLF", "PTSerif-TLF", "tgbonum", 
"tgchorus",
-"tgpagella", "tgschola", "tgtermes", "utopia", 0 };
+"tgpagella", "tgschola", "tgtermes", "utopia", "xcharter", 0 };
 
 const char * const known_sans_fonts[] = { "avant", "berasans", "biolinum",
 "biolinum-type1", "cmbr", "cmss", "helvet", "iwona", "iwonac",