date:20160402

On 3/04/2016 2:44 a.m., Peter Kümmel wrote:

Am 2. April 2016 11:26:06 MESZ, schrieb Andrew Parsloe :

Hullo Peter,
I've tried twice now to get a working bleeding-edge LyX (on a windows 7

machine), since there have been occasions recently when it would have
been helpful to have someone testing latest commits on a windows
machine. Everything seems to function until I launch LyX. A console
window opens, and then LyX is launched, but as you can see from the
attachment, the console window displays three error messages, and
remains open. Closing the console window closes LyX. With these errors
present, I'm reluctant to do anything serious with the resulting LyX.

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Lyx gives a lot of warnings. I don't think these are critical.

The console is enabled for bleeding edge build, maybe not a good idea. In a
release the console is just disabled, so there is no differrence in the lyx
functionality.
I will disable the console for bleeding edge, too.

Thanks for testing bleeding edge, I already was thinking about killing it.

Peter
I've downloaded a more recent version, and the console window is absent,
which is good. However, there is a problem with \lyxformat numbers. I
see that a new document in bleeding-edge LyX is format 507. Documents in
beta2 are 506 and are not converted. Looking at the messages pane
(newfile1.lyx is a 506 document),

Opening document D:\Documents\newfile1.lyx...Error: Document format failure

C:/Users/Andrew/AppData/Local/Temp/lyx_tmpdir.ZzYoSAnf4440/Buffer_convertLyXFormatiA4440.lyx
is not a readable LyX document.

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: Proposal for a guide on updating layouts

On 04/02/2016 03:55 PM, Andrew Parsloe wrote:
>
>
> On 3/04/2016 5:11 a.m., Guenter Milde wrote:
>> On 2016-04-02, Andrew Parsloe wrote:
>>> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
 On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
> "Add a template and/or example file to lib/templates/ respectively
> lib/examples/."
>> ...
>>
>>> As the son of a teacher of English and someone who spent a number of
>>> years indexing, editing and proofreading books, I question whether the
>>> "and/or" construction is needed at all. Just "or" suffices, the
>>> "respectively" making it clear which destination is appropriate. So:
>>> "Add a template or example file to lib/templates/ or lib/examples/,
>>> respectively."
>> Thank you for the clarification.
>>
>> As I am no native speaker, I am not sure whether this makes clear the
>> point,
>> that you are free to do one of the following three:
>>
>> a) add a template file to lib/templates/
>>
>> b) add an example file to lib/examples/
>>
>> c) add both, a template and an example file.
>>
>> Just "or" means for non-programmers typically an exclusive or (at
>> least in
>> German).
>>
>> Maybe we should be just explicit, as many readers ar non-natives, too.
>>
>> Günter
>>
> Good point. (Generally, if you want to emphasize an exclusive "or" in
> English you add "either": "either A or B". But in everyday English I
> suspect that "A or B" means something halfway between the logician's
> inclusive and exclusive "or"s.)

This is an issue that is much discussed by philosophers and linguists.
It is clear that "or" is used to convey both inclusive and exclusive
propositions. What's not clear is whether this is because the *word*
"or" is ambiguous between these two or whether it has one fixed meaning
and the other sense is a feature of (not entirely literal) usage. See
this article:
http://plato.stanford.edu/entries/implicature/
for more. The case of "or" is mentioned in section 4.

On a more substantive note: Do we really mean to require that a template
or example file be provided? I don't myself see any reason for that.

Richard

Re: Proposal for a guide on updating layouts




On 3/04/2016 5:11 a.m., Guenter Milde wrote:

On 2016-04-02, Andrew Parsloe wrote:

On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:

On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:

"Add a template and/or example file to lib/templates/ respectively
lib/examples/."

...


As the son of a teacher of English and someone who spent a number of
years indexing, editing and proofreading books, I question whether the
"and/or" construction is needed at all. Just "or" suffices, the
"respectively" making it clear which destination is appropriate. So:
"Add a template or example file to lib/templates/ or lib/examples/,
respectively."

Thank you for the clarification.

As I am no native speaker, I am not sure whether this makes clear the point,
that you are free to do one of the following three:

a) add a template file to lib/templates/

b) add an example file to lib/examples/

c) add both, a template and an example file.

Just "or" means for non-programmers typically an exclusive or (at least in
German).

Maybe we should be just explicit, as many readers ar non-natives, too.

Günter
Good point. (Generally, if you want to emphasize an exclusive "or" in 
English you add "either": "either A or B". But in everyday English I 
suspect that "A or B" means something halfway between the logician's 
inclusive and exclusive "or"s.)


Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: Proposal for a guide on updating layouts

2016-04-02 Thread Guillaume Munch


Le 02/04/2016 09:17, Scott Kostyshak a écrit :

On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:

Patch below, OK to commit?


Regarding "Summary... by GM.", note that we have two GM's.



Yes, sorry about this. I did not realise it when I chose this login. I
am always careful now not to introduce ambiguities.

Re: Proposal for a guide on updating layouts

2016-04-02 Thread Guenter Milde

On 2016-04-01, Richard Heck wrote:
> On 03/31/2016 05:35 PM, Scott Kostyshak wrote:
>> On Tue, Mar 29, 2016 at 12:53:15PM -0400, Richard Heck wrote:

>> Regarding version detection, do you have an idea for the
>> implementation? (if you want, you can make a trac ticket regarding
>> versioning and we can move the discussion there)

> I do not know how to do the LaTeX part, but I am assuming someone else
> will. Once we have that, the idea would be to have a layout tag like:

> IfVersion whatever.cls >= 0.9
> 
> EndIfVersion

> possibly with some "else" stuff in there, too. On the other hand, Georg
> has suggested some reservations about how extensively we'd want to use
> this, and those need to be thought through.

My idea was different: instead of introducing new "magic" for the layouts, I
would like to expand the existing mechanism for detection of available LaTeX
packages and classes, similar to waht LaTeX itself does:

  The  option of the package-author command

\RequirePackage [⟨options-list⟩] {⟨package-name⟩} [⟨release-info⟩]

  (as well as the author command \usepackage) tells a minimal required
  version/date.

Examples: \RequirePackage{ifthen}[1994/06/01]

Using a similar syntax in layout files, we could specify a version
requirement.

LyX could then announce if this version is provided or not, just like
currently done for versions with different file names.

Considering, that we may also want to exclude uncompatible newer versions
(when keeping an old layout so that old documents can still be opened), we
may also have to conceive a more powerful syntax.

Günter

Re: Issues to discuss for 2.2.0rc1

Am 2. April 2016 18:48:12 MESZ, schrieb Scott Kostyshak :
>On Sat, Apr 02, 2016 at 11:11:33AM +0200, Peter Kümmel wrote:
>> 
>> I've found a solution for the strange crashes, strfwd.h must always
>included first, if not the compiler makes assumption which are wrong.
>> Now config.h for msvc2015 includes strfwd.h, not very nice but it
>solves the issue.
>
>Thank you for the fix.
>
>> So I think we could risk a msvc2015/Qt 5.6.0 release.
>
>I want to make sure I understand this statement. I interpret this to
>mean that it might not be crazy of us to do a MSVC2015/Qt 5.6.0
>release.
>
>Or should I interpret it to mean that you now recommend a
>MSVC2015/Qt 5.6.0 release over a MSVC2010/Qt 5.5.1 release?
>
>Scott

I recomment now the msvc2015/Qt5.6.0 build. I think the risk is minimal, sure 
we drop the beta feedback, but I have the impression there was not much 
feedback. And 5.6 has features which users will miss, especially on Win 10.

And when we get horror feedback from the rc1 we could still go back.

Btw, why are the betas and rcs not announced on the webpage?

Peter

Re: Proposal for a guide on updating layouts

2016-04-02 Thread Guenter Milde

On 2016-04-02, Andrew Parsloe wrote:
> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
>> On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
>>> "Add a template and/or example file to lib/templates/ respectively
>>> lib/examples/."
...

> As the son of a teacher of English and someone who spent a number of 
> years indexing, editing and proofreading books, I question whether the 
> "and/or" construction is needed at all. Just "or" suffices, the 
> "respectively" making it clear which destination is appropriate. So:
> "Add a template or example file to lib/templates/ or lib/examples/, 
> respectively."

Thank you for the clarification.

As I am no native speaker, I am not sure whether this makes clear the point,
that you are free to do one of the following three:

a) add a template file to lib/templates/ 

b) add an example file to lib/examples/

c) add both, a template and an example file.

Just "or" means for non-programmers typically an exclusive or (at least in
German).

Maybe we should be just explicit, as many readers ar non-natives, too.

Günter

Re: Insert LyX Separator

2016-04-02 Thread Guillaume Munch


Le 02/04/2016 18:58, Scott Kostyshak a écrit :

On Sat, Apr 02, 2016 at 06:53:49PM +0200, Guillaume Munch wrote:

Le 02/04/2016 17:12, Richard Heck a écrit :


Is there a menu entry for inserting LyX separators and paragraph breaks?
I would have thought I'd find it under Insert> Formatting.





Edit > Start new environment (Alt+P Enter)

Seems convenient enough for me (also preserves the old shortcut).

Parbreak can be converted into from the contextual menu; there is no element
in the menu because, as I understand, they are only really useful when
converting 2.1 files into 2.2 files (tell me if I'm wrong).


Note also the following item from RELEASE-NOTES:

* The --Separator-- layout has been removed in favor of an environment
   separator inset. There is no provision for inserting this inset from
   the GUI (though some menu entries use it) as it is automatically inserted
   when needed. See Section 3.4.6 of the User Guide for details.

So I think Guillaume is right that in theory the separator should be
inserted automatically when necessary via the "Start new environment"
and "Start new (paragraph) environment".




There is also pressing Enter in an empty standard paragraph following a 
non-standard one (again, mimicking older behaviour).

Re: Insert LyX Separator

On Sat, Apr 02, 2016 at 06:53:49PM +0200, Guillaume Munch wrote:
> Le 02/04/2016 17:12, Richard Heck a écrit :
> >
> >Is there a menu entry for inserting LyX separators and paragraph breaks?
> >I would have thought I'd find it under Insert> Formatting.
> >
> 
> 
> 
> Edit > Start new environment (Alt+P Enter)
> 
> Seems convenient enough for me (also preserves the old shortcut).
> 
> Parbreak can be converted into from the contextual menu; there is no element
> in the menu because, as I understand, they are only really useful when
> converting 2.1 files into 2.2 files (tell me if I'm wrong).

Note also the following item from RELEASE-NOTES:

* The --Separator-- layout has been removed in favor of an environment
  separator inset. There is no provision for inserting this inset from
  the GUI (though some menu entries use it) as it is automatically inserted
  when needed. See Section 3.4.6 of the User Guide for details.

So I think Guillaume is right that in theory the separator should be
inserted automatically when necessary via the "Start new environment"
and "Start new (paragraph) environment".

Scott

signature.asc
Description: PGP signature

Re: Insert LyX Separator

2016-04-02 Thread Guillaume Munch


Le 02/04/2016 17:12, Richard Heck a écrit :


Is there a menu entry for inserting LyX separators and paragraph breaks?
I would have thought I'd find it under Insert> Formatting.





Edit > Start new environment (Alt+P Enter)

Seems convenient enough for me (also preserves the old shortcut).

Parbreak can be converted into from the contextual menu; there is no 
element in the menu because, as I understand, they are only really 
useful when converting 2.1 files into 2.2 files (tell me if I'm wrong).


Guillaume

Re: Bleeding-edge LyX

On Sat, Apr 02, 2016 at 10:42:55AM -0400, Richard Heck wrote:

> They are probably in customized bind files, possibly in
> user.bind. I'm not sure where these files are on Windows.

I think Help > About will say.

Scott


signature.asc
Description: PGP signature

Re: Issues to discuss for 2.2.0rc1

On Sat, Apr 02, 2016 at 11:11:33AM +0200, Peter Kümmel wrote:
> 
> I've found a solution for the strange crashes, strfwd.h must always included 
> first, if not the compiler makes assumption which are wrong.
> Now config.h for msvc2015 includes strfwd.h, not very nice but it solves the 
> issue.

Thank you for the fix.

> So I think we could risk a msvc2015/Qt 5.6.0 release.

I want to make sure I understand this statement. I interpret this to
mean that it might not be crazy of us to do a MSVC2015/Qt 5.6.0 release.

Or should I interpret it to mean that you now recommend a
MSVC2015/Qt 5.6.0 release over a MSVC2010/Qt 5.5.1 release?

Scott

signature.asc
Description: PGP signature

Re: Proposal for a guide on updating layouts

On 04/02/2016 04:33 AM, Georg Baum wrote:
> Guenter Milde wrote:
>
>> I tried to start a chapter about new and updated layouts in
>> Development.lyx. Of course, this is a biased view based on my experiences
>> and ideas, so please correct and amend before this can be the base for a
>> consensus.
>>
>> Patch below, OK to commit?
> I like it, but I think it can be improved (see attached):
>
> - I moved the discussion summary out of the file format section and into the 
> layout section. IMHO, the file format section should just list the changes 
> that do require a file format change.
> - I added modules to the layout section, since almost everything applies to 
> them as well
> - I mentioned removing of styles in the file format section. This was 
> missing previously, but it would be strange to require a file format change 
> for adding styles, but not for removing.
> - I took the comments by Scott into account, except the one about "Add a 
> template and/or example file to lib/templates/ respectively
> lib/examples/.", since I did not want to decide on this one.
>
> If you are fine with this one please commit.

I made some more changes and committed it. Others should obviously feel
free to keep updating it. One important thing I added was a note about
including the name of the |*.cls| file as an optional argument in the
|\DeclareLaTeXClass| line.

I think this will be a very good solution.

Richard

LyX Document

Insert LyX Separator


Is there a menu entry for inserting LyX separators and paragraph breaks?
I would have thought I'd find it under Insert> Formatting.

Richard

Re: Bleeding-edge LyX

Am 2. April 2016 11:26:06 MESZ, schrieb Andrew Parsloe :
>Hullo Peter,
>I've tried twice now to get a working bleeding-edge LyX (on a windows 7
>
>machine), since there have been occasions recently when it would have 
>been helpful to have someone testing latest commits on a windows 
>machine. Everything seems to function until I launch LyX. A console 
>window opens, and then LyX is launched, but as you can see from the 
>attachment, the console window displays three error messages, and 
>remains open. Closing the console window closes LyX. With these errors 
>present, I'm reluctant to do anything serious with the resulting LyX.
>
>Andrew
>
>
>---
>This email has been checked for viruses by Avast antivirus software.
>https://www.avast.com/antivirus

Lyx gives a lot of warnings. I don't think these are critical.

The console is enabled for bleeding edge build, maybe not a good idea. In a 
release the console is just disabled, so there is no differrence in the lyx 
functionality.
I will disable the console for bleeding edge, too.

Thanks for testing bleeding edge, I already was thinking about killing it.

Peter

Re: Bleeding-edge LyX

On 04/02/2016 05:26 AM, Andrew Parsloe wrote:
> Hullo Peter,
> I've tried twice now to get a working bleeding-edge LyX (on a windows
> 7 machine), since there have been occasions recently when it would
> have been helpful to have someone testing latest commits on a windows
> machine. Everything seems to function until I launch LyX. A console
> window opens, and then LyX is launched, but as you can see from the
> attachment, the console window displays three error messages, and
> remains open. Closing the console window closes LyX. With these errors
> present, I'm reluctant to do anything serious with the resulting LyX.

You probably have been getting these same errors for a very long time,
but you just never saw them. The LyX functions mentioned were removed in
LyX 2.0! They are probably in customized bind files, possibly in
user.bind. I'm not sure where these files are on Windows.

It should be safe to proceed.

Richard

Re: Proposal for a guide on updating layouts

On 04/02/2016 05:16 AM, Andrew Parsloe wrote:
>
>
> On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:
>> On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:
>>> "Add a template and/or example file to lib/templates/ respectively
>>> lib/examples/."
>>> -->
>>> (just a suggestion that sounds more natural to me, although it looks
>>> weird with "and/or" in-between directory paths. Your call.)
>>> "Add a template and/or example file to lib/templates/ and/or
>>> lib/examples/, respectively."
>>>
>>>
>>>
>>> Scott
> As the son of a teacher of English and someone who spent a number of
> years indexing, editing and proofreading books, I question whether the
> "and/or" construction is needed at all. Just "or" suffices, the
> "respectively" making it clear which destination is appropriate. So:
> "Add a template or example file to lib/templates/ or lib/examples/,
> respectively."

And it would actually be unusual, because usually unnecessary, to add both.

Richard

Bleeding-edge LyX


Hullo Peter,
I've tried twice now to get a working bleeding-edge LyX (on a windows 7 
machine), since there have been occasions recently when it would have 
been helpful to have someone testing latest commits on a windows 
machine. Everything seems to function until I launch LyX. A console 
window opens, and then LyX is launched, but as you can see from the 
attachment, the console window displays three error messages, and 
remains open. Closing the console window closes LyX. With these errors 
present, I'm reluctant to do anything serious with the resulting LyX.


Andrew


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: Proposal for a guide on updating layouts




On 2/04/2016 8:17 p.m., Scott Kostyshak wrote:

On Fri, Apr 01, 2016 at 09:23:05PM +, Guenter Milde wrote:

"Add a template and/or example file to lib/templates/ respectively
lib/examples/."
-->
(just a suggestion that sounds more natural to me, although it looks
weird with "and/or" in-between directory paths. Your call.)
"Add a template and/or example file to lib/templates/ and/or
lib/examples/, respectively."



Scott
As the son of a teacher of English and someone who spent a number of 
years indexing, editing and proofreading books, I question whether the 
"and/or" construction is needed at all. Just "or" suffices, the 
"respectively" making it clear which destination is appropriate. So:
"Add a template or example file to lib/templates/ or lib/examples/, 
respectively."


Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: Issues to discuss for 2.2.0rc1




Am 27.03.2016 um 21:38 schrieb Uwe Stöhr:

Am 20.03.2016 um 21:48 schrieb Scott Kostyshak:


Peter stated [1] that the patch is not necessary for compilation with
MSVC 2010.


But it doesn't harm then, see my today's post in the plans thread.


It seems the majority opinion is to release rc1 (and final
2.2.0) with Qt 5.5.1 compiled with MSVC 2010. Uwe, are you OK with that?


As I just wrote in the other thread I prefer Qt 5.6.
I can nevertheless release RC1 with Qt5.5.1/MSVC2010 and also a Qt 5.6 version. 
However, for the final release I won't maintain/offer support for a Qt 5.5.1 
build. Due to lack of time I will have to focus on one version and Qt 5.6 
offers a long term support, meaning I can assume that this version will be 
supported by the Qt people for the full life time of LyX 2.2.

I hope you can understand my decision.

regards Uwe



I've found a solution for the strange crashes, strfwd.h must always included 
first, if not the compiler makes assumption which are wrong.
Now config.h for msvc2015 includes strfwd.h, not very nice but it solves the 
issue.

So I think we could risk a msvc2015/Qt 5.6.0 release.

Peter

Re: Plan for 2.2.0rc1




Am 27.03.2016 um 21:33 schrieb Uwe Stöhr:

Am 19.03.2016 um 08:18 schrieb Scott Kostyshak:


Uwe, are you OK with shipping the official RC1 with 5.5.1 and MSVC 2010?
 From what I understand, that's the recommendation of Georg and Peter and
it seems like the safest approach.


This is not fine with me. My spare time is limited and I need to minimize the 
time to support LyX. With Qt 5.6 I can rely on a long term support. I already 
benefited from this with Qt 4.8.

I have been busy the last days but meanwhile used LyX 2.2git intensively for 2 
documentation projects with success. I used the Qt 5.6/MSVC2015 build and it is 
is faster than the Qt 5.5.1/MSVC 2010 build. I did not experience any 
regressions between both builds.

So all I need is the patch from Peter in master and then I am ready for LyX 
2.2RC1. Please note that the patch does not destroy anything, I applied it for 
all builds and I cannot see a problem.


I've commited the change.



So once again, please release RC1. I don't see why we should wait any longer.

regards Uwe

Re: Proposal for a guide on updating layouts

2016-04-02 Thread Georg Baum

Guenter Milde wrote:

> I tried to start a chapter about new and updated layouts in
> Development.lyx. Of course, this is a biased view based on my experiences
> and ideas, so please correct and amend before this can be the base for a
> consensus.
> 
> Patch below, OK to commit?

I like it, but I think it can be improved (see attached):

- I moved the discussion summary out of the file format section and into the 
layout section. IMHO, the file format section should just list the changes 
that do require a file format change.
- I added modules to the layout section, since almost everything applies to 
them as well
- I mentioned removing of styles in the file format section. This was 
missing previously, but it would be strange to require a file format change 
for adding styles, but not for removing.
- I took the comments by Scott into account, except the one about "Add a 
template and/or example file to lib/templates/ respectively
lib/examples/.", since I did not want to decide on this one.

If you are fine with this one please commit.


Georgdiff --git a/lib/doc/Development.lyx b/lib/doc/Development.lyx
index 6775a19..f705bae 100644
--- a/lib/doc/Development.lyx
+++ b/lib/doc/Development.lyx
@@ -265,10 +265,24 @@ New
 \end_inset
 
 style in any layout file or module shipped with \SpecialChar LyX
-, or new shipped layout
- file or module.
- These requirements are currently under discussion and might change in the
- future.
+.
+ See 
+\begin_inset CommandInset ref
+LatexCommand ref
+reference "subsec:Backporting-new-styles"
+
+\end_inset
+
+ for backporting new styles to the stable version without file format change.
+\end_layout
+
+\begin_layout Description
+Removed
+\begin_inset space ~
+\end_inset
+
+style in any layout file or module shipped with \SpecialChar LyX
+.
 \end_layout
 
 \begin_layout Description
@@ -891,6 +905,13 @@ lib/lyx2lyx/lyx2lyx_tools.py
 
 \begin_layout Subsection
 Backporting new styles to the stable version
+\begin_inset CommandInset label
+LatexCommand label
+name "subsec:Backporting-new-styles"
+
+\end_inset
+
+
 \end_layout
 
 \begin_layout Standard
@@ -978,6 +999,463 @@ lyx2lyx
  version.
 \end_layout
 
+\begin_layout Section
+New layouts and modules
+\end_layout
+
+\begin_layout Standard
+\begin_inset Note Greyedout
+status open
+
+\begin_layout Description
+Note: This section is currently only a proposal under discussion.
+ Please correct/amend as suited.
+ Remove this note once a consensus is found.
+\end_layout
+
+\begin_layout Plain Layout
+Summary of a recent discussion in lyx-devel by GM.
+\end_layout
+
+\begin_layout Plain Layout
+See the thread 
+\begin_inset Quotes eld
+\end_inset
+
+Proposal for a guide on updating layouts
+\begin_inset Quotes erd
+\end_inset
+
+ for details and background
+\end_layout
+
+\begin_layout Plain Layout
+http://permalink.gmane.org/gmane.editors.lyx.devel/161126 
+\end_layout
+
+\end_inset
+
+
+\end_layout
+
+\begin_layout Subsection
+New layouts
+\end_layout
+
+\begin_layout Standard
+Adding a new layout to the LyX library makes this an 
+\begin_inset Quotes eld
+\end_inset
+
+officially supported
+\begin_inset Quotes erd
+\end_inset
+
+ layout.
+\end_layout
+
+\begin_layout Itemize
+You should be committed to update and fix the layout if necessary.
+\end_layout
+
+\begin_layout Itemize
+Experimental and rarely used layouts should rather stay in the LyX wiki
+ (as user-contributed).
+\end_layout
+
+\begin_layout Itemize
+It may be good to propose the new layout on lyx-devel and ask for opinions
+ before actually comitting.
+\end_layout
+
+\begin_layout Itemize
+In older versions of this document it was stated that new layouts require
+ a file format change.
+ After some discussion it was decided that this is not needed.
+ For reference, here are the arguments from http://permalink.gmane.org/gmane.editor
+s.lyx.devel/161202
+\end_layout
+
+\begin_deeper
+\begin_layout Description
+Pro "new layout files are a file format change": 
+\end_layout
+
+\begin_layout Itemize
+All documents produced by 2.2.x can always be edited and exported even if
+ x is different.
+ This is important for people using different machines, or exchanging work
+ with colleagues.
+\end_layout
+
+\begin_layout Description
+Con "new layout files are a file format change": 
+\end_layout
+
+\begin_layout Itemize
+No new LaTeX classes can be supported in a stable version.
+\end_layout
+
+\begin_layout Itemize
+We have the same situation already with custom layout files: If a document
+ using a custom layout file is interchanged, the layout file needs to be
+ interchanged as well.
+ If that is not done, then we have a fallback implemented so that such documents
+ can still be edited, but not exported, and the user gets a warning.
+ 
+\end_layout
+
+\begin_layout Itemize
+lyx2lyx cannot do anything useful on backward conversion, and the forward
+ conversion would be a noop 
+\end_layout
+
+\end_deeper
+\begin_layout Standard
+Steps:
+\end_layout
+
+\begin_layout Itemize

Re: Issues to discuss for 2.2.0rc1

2016-04-02 Thread Kornel Benko

Am Freitag, 1. April 2016 um 19:18:11, schrieb Scott Kostyshak 

> On Fri, Apr 01, 2016 at 04:00:20PM -0700, Pavel Sanda wrote:
> > Georg Baum wrote:
> > > Where can I get a 
> > > current list of the email addresses of the translators?
> > 
> > Headers of .po files usually contains the last translator,
> 
> This is what Kornel's script takes care of automatically.

+ comparing with information at this side: http://www.lyx.org/I18n
The entries are not always identical.

> Scott
> 
> > git log should help in case the mail is missing.
> > I would CC lyx doc list as well.

Kornel

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

Re: Proposal for a guide on updating layouts