Re: Issue on the LyX download page

[Pavel Sanda]

Pavel Sanda wrote:
> I will kick it out of the page once back home.

Should be fixed now.

> Pavel

Re: Changing trac defaults

[Scott Kostyshak]

On Sat, Mar 21, 2015 at 06:27:17PM -0400, Richard Heck wrote:
> On 03/21/2015 05:59 PM, Scott Kostyshak wrote:
> > On Mon, Mar 16, 2015 at 9:02 PM, Richard Heck  wrote:
> > > On 03/16/2015 07:43 PM, Scott Kostyshak wrote:
> > > > 2. version. Currently it defaults to 2.1.3. I propose to have it
> > > > default to blank.
> > > > - I prefer to have the user choose the version. Otherwise they might
> > > > just have skipped choosing it or did not want or know how to find the
> > > > version they are using.
> > > 
> > > Same issue. If there has to be a default, then current version makes 
> > > sense.
> > > 
> > > If there's some way to have a "blank" default that I'm not seeing, I'm not
> > > opposed.
> > How about "unspecified" (which is already an option)? In fact I wonder
> > if at some point it was the default.
> 
> Not an option, either, in the Admin panel that allows one to set such
> things. Only the milestones we've created are choices.

Now the default milestone is blank, which is great. Can we also have the
version be blank by default? I think this would help, as discussed
before, so that we know if there is a version specified the user likely
has that version. Currently the default version is 2.2.0 and it's hard
to know whether that is the version of the user or if the user just did
not go to the trouble of changing it (or just didn't see it).

Scott


signature.asc
Description: PGP signature

Re: Tarballs for LyX 2.2.0 are on FTP

[Scott Kostyshak]

On Thu, Jun 02, 2016 at 02:00:20AM +0200, Uwe Stöhr wrote:
> There are 2 large security holes in ImageMagick (and also GraphicsMagick)
> that have been fixed:
> (article in German: 
> http://www.heise.de/newsticker/meldung/Luecke-in-ImageMagick-und-GraphicsMagick-ermoeglicht-erneute-Angriffe-3223811.html)
> 
> I therefore decided to release a new installer for LyX 2.2.0. This installer
> also fixes an uninstaller bug and maybe http://www.lyx.org/trac/ticket/9961
> 
> Could you please put it on ftp.lyx.org from here?:
> http://ftp.lyx.de/LyX%202.2.0/
> 
> thanks and regards
> Uwe

Done.

Scott


signature.asc
Description: PGP signature

Re: Issue on the LyX download page

[Pavel Sanda]

Uwe Stöhr wrote:
>> Try to click on a Mac OS X link for instance. It seems related to
>> oswatershed, probably their domain expired and something weird is going
>> on.
>
> I cannot reproduce any problems. All Mac OS links for for me.

I can reproduce it. We used watershed to display snippet of available
versions under various distros. It is dead now and either there is
some unfortunate interaction with the code for the snippet or new
owner exploited the publicly known snippet code to sneak into all
pages which did not stop use watershed.

I will kick it out of the page once back home.

Pavel

Re: Issue on the LyX download page

[Uwe Stöhr]

Am 02.06.2016 um 01:38 schrieb Alessandro Di Federico:


Hi, long time no see, since the last (?) dev meeting in Milan.


Hi Alessandro,

nice to hear from you again. You do a great job with the LyX courses!


http://www.lyx.org/Download

Try to click on a Mac OS X link for instance. It seems related to
oswatershed, probably their domain expired and something weird is going
on.


I cannot reproduce any problems. All Mac OS links for for me.

regards Uwe

Re: Tarballs for LyX 2.2.0 are on FTP

[Uwe Stöhr]

There are 2 large security holes in ImageMagick (and also 
GraphicsMagick) that have been fixed:
(article in German: 
http://www.heise.de/newsticker/meldung/Luecke-in-ImageMagick-und-GraphicsMagick-ermoeglicht-erneute-Angriffe-3223811.html)


I therefore decided to release a new installer for LyX 2.2.0. This 
installer also fixes an uninstaller bug and maybe 
http://www.lyx.org/trac/ticket/9961


Could you please put it on ftp.lyx.org from here?:
http://ftp.lyx.de/LyX%202.2.0/

thanks and regards
Uwe

Issue on the LyX download page

[Alessandro Di Federico]

Hi, long time no see, since the last (?) dev meeting in Milan.

A friend of mine told me about a popunder page which opens up when you
click on a download on the download page:

http://www.lyx.org/Download

Try to click on a Mac OS X link for instance. It seems related to
oswatershed, probably their domain expired and something weird is going
on.

I also want to let you know that this year we had the 4th or maybe 5th
edition of the LyX courses to take notes and write a thesis at my
university, Politecnico di Milano, with our FOSS promoting association
(POuL). For various reasons, this is probably the last year we do it.

Happy to hear LyX 2.2 has been released, great job everyone! :)

--
Alessandro Di Federico
PhD student at Politecnico di Milano

Re: #9368: Apostrophe a problem in file name

[Scott Kostyshak]

On Wed, Jun 01, 2016 at 03:04:12PM +, Michael Maltenfort wrote:
> I'm sorry to have been remiss in following up on this issue.
> By the end of this month, I will download the new version of LyX and test 
> things out.
> ---Michael Maltenfort

No problem, Michael. Thanks for getting back in touch. We'll look
forward to hearing from you.

Scott

> 
> 
>   From: LyX Ticket Tracker 
>  To: maltenf...@yahoo.com; lasgout...@lyx.org 
> Cc: for...@lyx.org; sp...@lyx.org
>  Sent: Tuesday, May 31, 2016 8:31 PM
>  Subject: Re: #9368: Apostrophe a problem in file name
>
> #9368: Apostrophe a problem in file name
> +-
>  Reporter:  maltenfort              |      Owner:  lasgouttes
>     Type:  defect                  |      Status:  new
>  Priority:  low                    |  Milestone:
> Component:  general                |    Version:  2.1.2
>  Severity:  minor                  |  Resolution:
>  Keywords:  os=windows, infoneeded  |
> +-
> 
> Comment (by skostysh):
> 
>  Maltenford do you still see this with LyX 2.2.0? There have been important
>  fixes that might have addressed this issue.
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor
> 
> 
>   


signature.asc
Description: PGP signature

Re: LyX 2.2 in the press

[Scott Kostyshak]

On Wed, Jun 01, 2016 at 10:35:48PM +0200, Uwe Stöhr wrote:
> There are currently only 3 articles about our new release:
> 
> in German:
> - 
> http://www.heise.de/newsticker/meldung/LyX-2-2-0-LaTeX-fuer-hochaufloesende-Displays-und-Qt-5-3223721.html
> - 
> http://www.pro-linux.de/news/1/23600/latex-wysiwym-editor-lyx-22-unterst%C3%BCtzt-qt-56.html
> 
> in Dutch:
> - http://tweakers.net/downloads/37527/lyx-22.html
> 
> Maybe somebody could inform journalists in their country or from local
> newspapers to report.
> 
> It is interesting to read the comments below the articles. In principle they
> are positive.
> 
> (For this release I did not have the time to contact journalists but at
> least there are 2 articles in German.)
> 
> regards Uwe

I've contacted some but have not heard back from a few that I thought
would be more or less automatic (e.g. Phoronix). One that did follow
through though is:

http://texblog.net/latex-archive/ide-editor/lyx-2-2/

Scott


signature.asc
Description: PGP signature

Re: [PATCH] microtype

[Pavel Sanda]

Georg Baum wrote:
> > I just blindly copied what was there for other on-off packages, because
> > I have little clue what tex2lyx code does and zero comments in critical
> > sections does not help. I know it's not your fault ;)
> 
> Actually the other packages are not on-off, they are off-auto-on. This is 
> needed for all packages automatically loaded by math commands. It is not 
> needed for microtype, since ther is no automatism.

Oh, I see, so "2" is actually value for tri-state variable on-off-auto, correct?

> The minimum thing you need to do is to write the format corresponding to 
> LYX_FORMAT_TEX2LYX (see attached). The actual recognition of a loaded 
> microtype package can be done later (this is the reason why you need a TODO 
> entry).

Sure, I can do that.

Pavel

Re: [PATCH] microtype

[Pavel Sanda]

PhilipPirrip wrote:
> Even Fonts section should be OK, as this makes use and/or changes features 
> of individual glyphs and whole fonts.

Yes, my life would be easier then. But no hard opinion on the issue.

> Speaking of this: why is "Use justification in LyX work area" in Text 
> Layout of Document Settings, and not in Preferences, like Look&Feel/Screen 
> Fonts and Colors are?

I guess because for some people it's really per-document issue. Say you
write some of your documents in CJK language where latin whitespaces do
not apply the way they are used in latin based scripts and justification
makes it messy on the screen.

Pavel

Re: Horizontal crolling impossible in table in float in LyX 2.2.0

[Jean-Marc Lasgouttes]

Le 01/06/16 à 18:34, Richard Heck a écrit :

I hope to do the 2.1.5 release in a week or so. Once that's been done,
and if nothing really bad has appeared in the meanwhile, then we let's
merge 2.2.2-staging and move towards a 2.2.1 release.


OK. Shall I cherry-pick c8e1c09236 to stable althouhg it is already in 
2.2.2?


JMarc

Re: [PATCH] microtype

[PhilipPirrip]

On 06/01/2016 02:12 PM, Pavel Sanda wrote:

Anyway would you like to see it in text or page layout?



Between these two, I say: Text layout definitely!
Even Fonts section should be OK, as this makes use and/or changes 
features of individual glyphs and whole fonts.

Microtype isn't ONLY about how a line of text should be long.


Speaking of this: why is "Use justification in LyX work area" in Text 
Layout of Document Settings, and not in Preferences, like 
Look&Feel/Screen Fonts and Colors are?

Re: [PATCH] microtype

[Georg Baum]

Pavel Sanda wrote:

> I just blindly copied what was there for other on-off packages, because
> I have little clue what tex2lyx code does and zero comments in critical
> sections does not help. I know it's not your fault ;)

Actually the other packages are not on-off, they are off-auto-on. This is 
needed for all packages automatically loaded by math commands. It is not 
needed for microtype, since ther is no automatism.

The minimum thing you need to do is to write the format corresponding to 
LYX_FORMAT_TEX2LYX (see attached). The actual recognition of a loaded 
microtype package can be done later (this is the reason why you need a TODO 
entry).


Georgdiff --git a/src/tex2lyx/Preamble.cpp b/src/tex2lyx/Preamble.cpp
index 24c403d..35f5c11 100644
--- a/src/tex2lyx/Preamble.cpp
+++ b/src/tex2lyx/Preamble.cpp
@@ -457,7 +457,8 @@ string remove_braces(string const & value)
 
 
 Preamble::Preamble() : one_language(true), explicit_babel(false),
-	title_layout_found(false), index_number(0), h_font_cjk_set(false)
+	title_layout_found(false), index_number(0), h_font_cjk_set(false),
+	h_use_microtype(false)
 {
 	//h_backgroundcolor;
 	//h_boxbgcolor;
@@ -487,6 +488,7 @@ Preamble::Preamble() : one_language(true), explicit_babel(false),
 	h_font_tt_scale[0]= "100";
 	h_font_tt_scale[1]= "100";
 	//h_font_cjk
+	//h_use_microtype
 	h_graphics= "default";
 	h_default_output_format   = "default";
 	h_html_be_strict  = "false";
@@ -1162,7 +1164,8 @@ bool Preamble::writeLyXHeader(ostream & os, bool subdoc, string const & outfiled
 	   << ' ' << h_font_tt_scale[1] << '\n';
 	if (!h_font_cjk.empty())
 		os << "\\font_cjk " << h_font_cjk << '\n';
-	os << "\\graphics " << h_graphics << '\n'
+	os << "\\use_microtype " << h_use_microtype << '\n'
+	   << "\\graphics " << h_graphics << '\n'
 	   << "\\default_output_format " << h_default_output_format << "\n"
 	   << "\\output_sync " << h_output_sync << "\n";
 	if (h_output_sync == "1")
diff --git a/src/tex2lyx/Preamble.h b/src/tex2lyx/Preamble.h
index f9342ef..350644d 100644
--- a/src/tex2lyx/Preamble.h
+++ b/src/tex2lyx/Preamble.h
@@ -151,6 +151,7 @@ private:
 	std::string h_font_tt_scale[2];
 	bool h_font_cjk_set;
 	std::string h_font_cjk;
+	bool h_use_microtype;
 	std::string h_graphics;
 	std::string h_default_output_format;
 	std::string h_html_be_strict;

LyX 2.2 in the press

[Uwe Stöhr]

There are currently only 3 articles about our new release:

in German:
- 
http://www.heise.de/newsticker/meldung/LyX-2-2-0-LaTeX-fuer-hochaufloesende-Displays-und-Qt-5-3223721.html
- 
http://www.pro-linux.de/news/1/23600/latex-wysiwym-editor-lyx-22-unterst%C3%BCtzt-qt-56.html


in Dutch:
- http://tweakers.net/downloads/37527/lyx-22.html

Maybe somebody could inform journalists in their country or from local 
newspapers to report.


It is interesting to read the comments below the articles. In principle 
they are positive.


(For this release I did not have the time to contact journalists but at 
least there are 2 articles in German.)


regards Uwe

Re: Horizontal crolling impossible in table in float in LyX 2.2.0

[Uwe Stöhr]

Am 01.06.2016 um 18:34 schrieb Richard Heck:


I hope to do the 2.1.5 release in a week or so.


For information: I cannot provide an installer from June 9th to 19th. So 
a release before would be fine if possible.



Once that's been done,
and if nothing really bad has appeared in the meanwhile, then we let's
merge 2.2.2-staging and move towards a 2.2.1 release.


+1 People are just beginning to test LyX 2.2 and we should wait another 
week before merging 2.2-staging.


regards Uwe

Re: [LyX/2.1.x] Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5 release.

[Richard Heck]

On 06/01/2016 03:08 PM, Georg Baum wrote:
> Richard Heck wrote:
>
>> commit 4eb3ed96e53ab0eb2af519caa6125cac79c823ad
>> Author: Richard Heck 
>> Date:   Wed Jun 1 12:31:48 2016 -0400
>>
>> Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5
>> release.
>>
>> diff --git a/lib/lyx2lyx/LyX.py b/lib/lyx2lyx/LyX.py
>> index 7e52238..1e2147d 100644
>> --- a/lib/lyx2lyx/LyX.py
>> +++ b/lib/lyx2lyx/LyX.py
>> @@ -33,7 +33,7 @@ try:
>>  import lyx2lyx_version
>>  version__ = lyx2lyx_version.version
>>  except: # we are running from build directory so assume the last version
>> -version__ = '2.1'
>> +version__ = '2.2'
> Shouldn't the default version stay at 2.1?

yes, thanks.

rh

Re: [PATCH] microtype

[Pavel Sanda]

Georg Baum wrote:
> Pavel Sanda wrote:
> 
> > Pavel Sanda wrote:
> >> @@ -813,7 +814,7 @@ void Preamble::handle_package(Parser &p, string const
> >> & name,
> >>  else if (name == "amsmath" || name == "amssymb" || name == "cancel" ||
> >>  name == "esint" || name == "mhchem" || name == "mathdots" ||
> >>  name == "mathtools" || name == "stackrel" ||
> >> -   name == "stmaryrd" || name == "undertilde")
> >> +   name == "stmaryrd" || name == "undertilde" || name == 
> "microtype")
> >>  h_use_packages[name] = "2";
> > 
> > BTW Georg, do you know what this "2" stands for?
> 
> BufferParams::package_on (blame the one who decided to write enum values as 
> numbers and not as strings to the file, might be me actually). Since you use 
> a bool for use_microtype the "2" is not correct for microtype, and you 
> should not use h_use_packages.

I just blindly copied what was there for other on-off packages, because
I have little clue what tex2lyx code does and zero comments in critical
sections does not help. I know it's not your fault ;)
Could you give me helping hand?
Pavel

Re: [PATCH] microtype

[Georg Baum]

Pavel Sanda wrote:

> Pavel Sanda wrote:
>> @@ -813,7 +814,7 @@ void Preamble::handle_package(Parser &p, string const
>> & name,
>>  else if (name == "amsmath" || name == "amssymb" || name == "cancel" ||
>>  name == "esint" || name == "mhchem" || name == "mathdots" ||
>>  name == "mathtools" || name == "stackrel" ||
>> - name == "stmaryrd" || name == "undertilde")
>> + name == "stmaryrd" || name == "undertilde" || name == 
"microtype")
>>  h_use_packages[name] = "2";
> 
> BTW Georg, do you know what this "2" stands for?

BufferParams::package_on (blame the one who decided to write enum values as 
numbers and not as strings to the file, might be me actually). Since you use 
a bool for use_microtype the "2" is not correct for microtype, and you 
should not use h_use_packages.


Georg

Re: [PATCH] microtype

[Pavel Sanda]

Pavel Sanda wrote:
> diff --git a/src/tex2lyx/Preamble.cpp b/src/tex2lyx/Preamble.cpp
> index 24c403d..95212ae 100644
> --- a/src/tex2lyx/Preamble.cpp
> +++ b/src/tex2lyx/Preamble.cpp
> @@ -554,6 +554,7 @@ Preamble::Preamble() : one_language(true), 
> explicit_babel(false),
>   h_use_packages["stackrel"]   = "0";
>   h_use_packages["stmaryrd"]   = "0";
>   h_use_packages["undertilde"] = "0";
> + h_use_packages["microtype"]  = "0";
>  }
>  
>  
> @@ -813,7 +814,7 @@ void Preamble::handle_package(Parser &p, string const & 
> name,
>   else if (name == "amsmath" || name == "amssymb" || name == "cancel" ||
>name == "esint" || name == "mhchem" || name == "mathdots" ||
>name == "mathtools" || name == "stackrel" ||
> -  name == "stmaryrd" || name == "undertilde")
> +  name == "stmaryrd" || name == "undertilde" || name == 
> "microtype")
>   h_use_packages[name] = "2";

BTW Georg, do you know what this "2" stands for?

Pavel

Re: [LyX/2.1.x] Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5 release.

[Georg Baum]

Richard Heck wrote:

> commit 4eb3ed96e53ab0eb2af519caa6125cac79c823ad
> Author: Richard Heck 
> Date:   Wed Jun 1 12:31:48 2016 -0400
> 
> Update lyx2lyx from 2.2.0. This is in preparation for the 2.1.5
> release.
> 
> diff --git a/lib/lyx2lyx/LyX.py b/lib/lyx2lyx/LyX.py
> index 7e52238..1e2147d 100644
> --- a/lib/lyx2lyx/LyX.py
> +++ b/lib/lyx2lyx/LyX.py
> @@ -33,7 +33,7 @@ try:
>  import lyx2lyx_version
>  version__ = lyx2lyx_version.version
>  except: # we are running from build directory so assume the last version
> -version__ = '2.1'
> +version__ = '2.2'

Shouldn't the default version stay at 2.1?


Georg

Re: [PATCH] microtype

[mn]

On 01.06.16 16:21, Guenter Milde wrote:
> On 2016-06-01, Jürgen Spitzmüller wrote:
> 
>> [-- Type: text/plain, Encoding: quoted-printable --]
> 
>> 2016-06-01 11:43 GMT+02:00 Jürgen Spitzmüller :
> 
>>> Do not use LateXisms in the GUI -- we just got rid of "Use longtable".
> 
>>> Instead of "Use microtype", the GUI should be something like "Enable
>>> micro-typographic extensions"
> 
>>> And the tooltip:
> 
>>> "Activates micro-typographic extensions such as character protusion and
>>> font expansion via the microtype package (requires pdftex 
> 
> or LuaTeX

No.
Although, according to the Readme, LuaTex-support is/will be improved
again in TexLive 2016.
But full support/functionality means the features kerning and spacing
are working/ can be enabled for pdf-output.
This is not the case for luatex.
(cf. p. 7 microtype.pdf in TexLive2015)
Only PDF-output via pdflatex gives full functionality.

>>> for full functionality)".


greetings
Mike

Re: [PATCH] microtype

[Pavel Sanda]

Jürgen Spitzmüller wrote:
> BTW, character protusion and font expansion are not so much a font
> property, but a page layout property.

I guess its both. Anyway would you like to see it in text or page layout?

Pavel

Re: Horizontal crolling impossible in table in float in LyX 2.2.0

[Richard Heck]

On 06/01/2016 08:02 AM, Jean-Marc Lasgouttes wrote:
> Le 31/05/2016 à 23:20, Richard Heck a écrit :
>>> Since it is a regression and the patch is simple, this could actually
>>> be candidate for branch right now, Richard.
>>
>> Sure, looks safe enough.
>
> Which leads me to the question: do we really expect that there will be
> a urgent 2.2.1 release? What about merging 2.2.2-staging right now and
> start the (somewhat long) release process?
>
> I understand that the 2.1.5 release process has begun (since the
> translators have been warned), but maybe 2.2.1 could be handled in
> parallel? We already have some interesting material in there, that
> accumulated during 2.2.0 release time.

I hope to do the 2.1.5 release in a week or so. Once that's been done,
and if nothing really bad has appeared in the meanwhile, then we let's
merge 2.2.2-staging and move towards a 2.2.1 release.

> PS: don't forget to update lyx2lyx for 2.1.5 :)

Just done.

Richard

Re: #9368: Apostrophe a problem in file name

[Michael Maltenfort]

I'm sorry to have been remiss in following up on this issue.
By the end of this month, I will download the new version of LyX and test 
things out.
---Michael Maltenfort


  From: LyX Ticket Tracker 
 To: maltenf...@yahoo.com; lasgout...@lyx.org 
Cc: for...@lyx.org; sp...@lyx.org
 Sent: Tuesday, May 31, 2016 8:31 PM
 Subject: Re: #9368: Apostrophe a problem in file name
   
#9368: Apostrophe a problem in file name
+-
 Reporter:  maltenfort              |      Owner:  lasgouttes
    Type:  defect                  |      Status:  new
 Priority:  low                    |  Milestone:
Component:  general                |    Version:  2.1.2
 Severity:  minor                  |  Resolution:
 Keywords:  os=windows, infoneeded  |
+-

Comment (by skostysh):

 Maltenford do you still see this with LyX 2.2.0? There have been important
 fixes that might have addressed this issue.

-- 
Ticket URL: 
The LyX Project 
LyX -- The Document Processor


  

Re: [PATCH] microtype

[Guenter Milde]

On 2016-06-01, Jürgen Spitzmüller wrote:

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

> 2016-06-01 11:43 GMT+02:00 Jürgen Spitzmüller :

>> Do not use LateXisms in the GUI -- we just got rid of "Use longtable".

>> Instead of "Use microtype", the GUI should be something like "Enable
>> micro-typographic extensions"

>> And the tooltip:

>> "Activates micro-typographic extensions such as character protusion and
>> font expansion via the microtype package (requires pdftex 

or LuaTeX

>> for full
>> functionality)".



> BTW, character protusion and font expansion are not so much a font
> property, but a page layout property.

> Jürgen


>> Jürgen





> [-- Skipped Type: text/html --]

Re: Horizontal crolling impossible in table in float in LyX 2.2.0

[Jean-Marc Lasgouttes]

Le 31/05/2016 à 23:20, Richard Heck a écrit :

Since it is a regression and the patch is simple, this could actually
be candidate for branch right now, Richard.


Sure, looks safe enough.


Which leads me to the question: do we really expect that there will be a 
urgent 2.2.1 release? What about merging 2.2.2-staging right now and 
start the (somewhat long) release process?


I understand that the 2.1.5 release process has begun (since the 
translators have been warned), but maybe 2.2.1 could be handled in 
parallel? We already have some interesting material in there, that 
accumulated during 2.2.0 release time.


JMarc

PS: don't forget to update lyx2lyx for 2.1.5 :)

Re: [PATCH] microtype

[Jürgen Spitzmüller]

2016-06-01 11:43 GMT+02:00 Jürgen Spitzmüller :

> Do not use LateXisms in the GUI -- we just got rid of "Use longtable".
>
> Instead of "Use microtype", the GUI should be something like "Enable
> micro-typographic extensions"
>
> And the tooltip:
>
> "Activates micro-typographic extensions such as character protusion and
> font expansion via the microtype package (requires pdftex for full
> functionality)".
>


BTW, character protusion and font expansion are not so much a font
property, but a page layout property.

Jürgen


> Jürgen
>
>
>
>

Re: [PATCH] microtype

[Jürgen Spitzmüller]

2016-06-01 11:02 GMT+02:00 Pavel Sanda :

> So updated patch for master. I decided to make fileformat change
> instead of module.
>
> Will commit unless there are some comments.
>

Do not use LateXisms in the GUI -- we just got rid of "Use longtable".

Instead of "Use microtype", the GUI should be something like "Enable
micro-typographic extensions"

And the tooltip:

"Activates micro-typographic extensions such as character protusion and
font expansion via the microtype package (requires pdftex for full
functionality)".

Jürgen

Re: [PATCH] microtype

[Pavel Sanda]

So updated patch for master. I decided to make fileformat change
instead of module. 

Will commit unless there are some comments.

Pavel Sanda wrote:
> Guenter Milde wrote:
> > I got the same impression after some tests with a *.tex file here.
> > This is also what the documentation tells: it works for all three of
> > pdflatex, xelatex, and lualatex but only pdflatex supports all features.
> > There is no error with "plain" latex (DVI, PS, PDF (ps2pdf), PDF (dvipdfm)
> > but no effect either.
> > 
> > A tooltip should hint to limited support (linking to the documentation)

Done.

> > > People who use custom parameters are on their own. But is there an

> > > advantage of letting users enter custom params via a line edit, instead
> > > of letting them write it by hand in the preamble?  It does not seem to
> > > me that the GUI helps here. Or do you have further plans for this
> > > feature?
> 
> I do not have plan, just got some (unf.) private response to this thread.
> I will ask on users list whether people tend to use some params.

Since people on users list did use params either, I killed the optional line 
edit.

Pavel
diff --git a/development/FORMAT b/development/FORMAT
index 01319df..f7bb30f 100644
--- a/development/FORMAT
+++ b/development/FORMAT
@@ -11,6 +11,11 @@ adjustments are made to tex2lyx and bugs are fixed in lyx2lyx.
 
 ---
 
+2016-06-16 Pavel Sanda 
+	* Format incremented to 509.
+	New parameter "\use_microtype bool" for including microtype LaTeX
+	package into preamble.
+
 2016-04-05 Enrico Forestieri 
 	* Format incremented to 508
 	  New kind of Separator inset (latexpar). The old parbreak separator
diff --git a/lib/lyx2lyx/LyX.py b/lib/lyx2lyx/LyX.py
index 1e2147d..fa2bbba 100644
--- a/lib/lyx2lyx/LyX.py
+++ b/lib/lyx2lyx/LyX.py
@@ -33,7 +33,7 @@ try:
 import lyx2lyx_version
 version__ = lyx2lyx_version.version
 except: # we are running from build directory so assume the last version
-version__ = '2.2'
+version__ = '2.3'
 
 default_debug__ = 2
 
@@ -86,7 +86,8 @@ format_relation = [("0_06",[200], minor_versions("0.6" , 4)),
("1_6", list(range(277,346)), minor_versions("1.6" , 10)),
("2_0", list(range(346,414)), minor_versions("2.0" , 8)),
("2_1", list(range(414,475)), minor_versions("2.1" , 5)),
-   ("2_2", list(range(475,509)), minor_versions("2.2" , 0))
+   ("2_2", list(range(475,509)), minor_versions("2.2" , 0)),
+   ("2_3", list(range(509,510)), minor_versions("2.3" , 0))
   ]
 
 
diff --git a/lib/lyx2lyx/Makefile.am b/lib/lyx2lyx/Makefile.am
index 4490cb7..89ba23b 100644
--- a/lib/lyx2lyx/Makefile.am
+++ b/lib/lyx2lyx/Makefile.am
@@ -33,6 +33,7 @@ dist_lyx2lyx_PYTHON = \
 	lyx_2_0.py \
 	lyx_2_1.py \
 	lyx_2_2.py \
+	lyx_2_3.py \
 	profiling.py \
 	test_parser_tools.py
 
diff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
index 9d121cb..bcf8d64 100644
--- a/src/BufferParams.cpp
+++ b/src/BufferParams.cpp
@@ -388,6 +388,7 @@ BufferParams::BufferParams()
 	fonts_math[1] = "auto";
 	fonts_default_family = "default";
 	useNonTeXFonts = false;
+	use_microtype = false;
 	fonts_expert_sc = false;
 	fonts_old_figures = false;
 	fonts_sans_scale[0] = 100;
@@ -771,6 +772,8 @@ string BufferParams::readToken(Lexer & lex, string const & token,
 		lex >> fonts_typewriter_scale[1];
 	} else if (token == "\\font_cjk") {
 		lex >> fonts_cjk;
+	} else if (token == "\\use_microtype") {
+		lex >> use_microtype;
 	} else if (token == "\\paragraph_separation") {
 		string parsep;
 		lex >> parsep;
@@ -1139,6 +1142,7 @@ void BufferParams::writeFile(ostream & os, Buffer const * buf) const
 	if (!fonts_cjk.empty()) {
 		os << "\\font_cjk " << fonts_cjk << '\n';
 	}
+	os << "\\use_microtype " << convert(use_microtype) << '\n';
 	os << "\\graphics " << graphics_driver << '\n';
 	os << "\\default_output_format " << default_output_format << '\n';
 	os << "\\output_sync " << output_sync << '\n';
@@ -1411,6 +1415,9 @@ void BufferParams::validate(LaTeXFeatures & features) const
 
 	if (useNonTeXFonts && fontsMath() != "auto")
 		features.require("unicode-math");
+	
+	if (use_microtype)
+		features.require("microtype");
 
 	if (!language->requires().empty())
 		features.require(language->requires());
diff --git a/src/BufferParams.h b/src/BufferParams.h
index f62911c..7314b42 100644
--- a/src/BufferParams.h
+++ b/src/BufferParams.h
@@ -278,6 +278,8 @@ public:
 	int fontsTypewriterScale() const { return fonts_typewriter_scale[useNonTeXFonts]; }
 	/// the font used by the CJK command
 	std::string fonts_cjk;
+	/// use LaTeX microtype package
+	bool use_microtype;
 	///
 	Spacing & spacing();
 	Spacing const & spacing() const;
diff --git a/src/LaTeXFeatures.cpp b/src/LaTeXFeatures.cpp
index 4fa2c82..3a2e775 100644
--- a/src/LaTeXFeatures.cpp
+++ b/src/LaTeXFeatures.cpp
@@ -1132,6 +1

Re: [LyX/master] glitch in lfundoc

[Pavel Sanda]

avel Sanda wrote:
> commit b356df7fcf8b1970a1767138d0fa287114b6cea3
> Author: Pavel Sanda 
> Date:   Wed Jun 1 00:20:50 2016 -0700
> 
> glitch in lfundoc

Hi Juergen,

I don't know whether it was your intention, but it seems that part of Hidden
lfuns is no more generated correctly and some lfuns are missing (most probably
due to the fact they don't have Syntax line).

Pavel