Re: alpha beta lyx-formats and devel versions of the docs

2017-08-01 Thread Scott Kostyshak
On Sun, Jul 30, 2017 at 07:55:55PM +0200, Uwe Stöhr wrote:

> My personal policy is to stop working on the stable branch docs with the
> release of the first beta of a new version. This is just to save manpower.
> We have not released a beta yet, but I already started the doc updating for
> 2.3. So unless there is a compilation failure I would not backport info to
> the 2.2 branch anymore.

That makes sense to me. After beta, we hopefully won't have file format
changes so anyone who installs a beta or later can edit the newest
documentation. Even if we do have a file format change, we could
probably keep the documentation in beta format.

Scott


signature.asc
Description: PGP signature


Re: alpha beta lyx-formats and devel versions of the docs

2017-07-30 Thread Uwe Stöhr

El 26.07.2017 a las 21:41, Richard Heck escribió:


Mike makes a good point. He wants to help with testing and improving the
documentation but cannot because of the file format. What is our policy
on updating the file format? I believe we only do that when we have to
update the format because we are using a new feature. Is that right?


Yes, as best we can. But in practice, the people updating the docs are
using the latest version, and the version number gets updated. (I think
this is why it's often suggested that updates be made in stable first,
not in master.)


Yes, that is why I write so often to put all changes to the 
documentation that don't require a fileformat change to the stable 
branch. This way everybody can have a look and review it.


I try to look at these changes soon and distribute the changes to the 
different language files and port the changes to master. In the past I 
got this way feedback from our translators so that I could correct it 
for the next stable release. if it would have been only in master the 
stable branch and thus the majority of users would not benefit from doc 
corrections/updates.


My personal policy is to stop working on the stable branch docs with the 
release of the first beta of a new version. This is just to save 
manpower. We have not released a beta yet, but I already started the doc 
updating for 2.3. So unless there is a compilation failure I would not 
backport info to the 2.2 branch anymore.


regards Uwe


Re: alpha beta lyx-formats and devel versions of the docs

2017-07-26 Thread Richard Heck
On 07/26/2017 02:18 PM, Scott Kostyshak wrote:
> On Tue, Jul 25, 2017 at 08:29:50PM +0200, mn wrote:
>> The latest publicly available binaries are for alpha1-1.
>> The latest changes to the docs are format 544, and none of the versions
>> I have installed can read or convert them.
>>
>> Now, say I have spotted errors or improvements in or for them, like
>> latest UserGuide.de.lyx:
>>
>> 26812 selbst) Formate für alle verfügbarren Typen von Verweisen
>> vordefiniert.
>>
>> How to proceed?
>>
>> Proposal:
>> – more intermediate alphas, betas, at least in sync with the current
>> file-format.
> Mike makes a good point. He wants to help with testing and improving the
> documentation but cannot because of the file format. What is our policy
> on updating the file format? I believe we only do that when we have to
> update the format because we are using a new feature. Is that right?

Yes, as best we can. But in practice, the people updating the docs are
using the latest version, and the version number gets updated. (I think
this is why it's often suggested that updates be made in stable first,
not in master.)

Should we ask people changing these documents EITHER to use the latest
'official' release (alpha1, in this case) or else to convert to the
relevant format before committing, UNLESS they have used a new feature?

Another way to proceed here would be to undo the damange via lyx2lyx and
check to make sure that's not actually changing anything of substance.
I've attached a patch that would do that. I've looked through it, and it
seems fine. Feel free to commit it.

Richard

PS

for F in $(find -name '*.lyx'); do if [[ $F =~ /attic/ ]]; then
continue; fi; head -n2 "$F" | tail -n1| if ! grep -q 541; then mv $F
$F.old; ../lyx2lyx/lyx2lyx -t 541 <$F.old >$F; fi;  done

from lib/doc/.

diff --git a/lib/doc/Additional.lyx b/lib/doc/Additional.lyx
index 105a9f8..60e8feb 100644
--- a/lib/doc/Additional.lyx
+++ b/lib/doc/Additional.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 544
+\lyxformat 541
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -97,7 +97,6 @@ shapepar
 \suppress_date false
 \justification true
 \use_refstyle 0
-\use_minted 0
 \notefontcolor #ff
 \index Index
 \shortcut idx
@@ -109,7 +108,6 @@ shapepar
 \paragraph_indentation default
 \is_math_indent 1
 \math_indentation default
-\math_numbering_side default
 \quotes_style english
 \dynamic_quotes 0
 \papercolumns 1
diff --git a/lib/doc/EmbeddedObjects.lyx b/lib/doc/EmbeddedObjects.lyx
index 57deaaa..72d979e 100644
--- a/lib/doc/EmbeddedObjects.lyx
+++ b/lib/doc/EmbeddedObjects.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 544
+\lyxformat 541
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -216,7 +216,6 @@ graphicboxes
 \suppress_date false
 \justification true
 \use_refstyle 0
-\use_minted 0
 \notefontcolor #ff
 \index Index
 \shortcut idx
@@ -227,7 +226,6 @@ graphicboxes
 \paragraph_separation skip
 \defskip medskip
 \is_math_indent 0
-\math_numbering_side default
 \quotes_style english
 \dynamic_quotes 0
 \papercolumns 1
diff --git a/lib/doc/Intro.lyx b/lib/doc/Intro.lyx
index aea4db7..9d145b3 100644
--- a/lib/doc/Intro.lyx
+++ b/lib/doc/Intro.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 543
+\lyxformat 541
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -95,7 +95,6 @@
 \paragraph_separation indent
 \paragraph_indentation default
 \is_math_indent 0
-\math_numbering_side default
 \quotes_style english
 \dynamic_quotes 0
 \papercolumns 1
diff --git a/lib/doc/LaTeXConfig.lyx b/lib/doc/LaTeXConfig.lyx
index abc991c..f5893fd 100644
--- a/lib/doc/LaTeXConfig.lyx
+++ b/lib/doc/LaTeXConfig.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 542
+\lyxformat 541
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -61,7 +61,6 @@
 \paragraph_separation indent
 \paragraph_indentation default
 \is_math_indent 0
-\math_number_before 0
 \quotes_style english
 \dynamic_quotes 0
 \papercolumns 1
diff --git a/lib/doc/Math.lyx b/lib/doc/Math.lyx
index ecf876f..e499938 100644
--- a/lib/doc/Math.lyx
+++ b/lib/doc/Math.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 543
+\lyxformat 541
 \begin_document
 \begin_header
 \save_transient_properties true
@@ -204,7 +204,6 @@
 \paragraph_separation skip
 \defskip medskip
 \is_math_indent 0
-\math_numbering_side default
 \quotes_style english
 \dynamic_quotes 0
 \papercolumns 1
diff --git a/lib/doc/UserGuide.lyx b/lib/doc/UserGuide.lyx
index 67db459..7c0465d 100644
--- a/lib/doc/UserGuide.lyx
+++ b/lib/doc/UserGuide.lyx
@@ -1,5 +1,5 @@
 #LyX 2.3 created this file. For more info see http://www.lyx.org/
-\lyxformat 544
+\lyxformat 541
 \begin_document
 \begin_header
 

Re: alpha beta lyx-formats and devel versions of the docs

2017-07-26 Thread Scott Kostyshak
On Tue, Jul 25, 2017 at 08:29:50PM +0200, mn wrote:
> The latest publicly available binaries are for alpha1-1.
> The latest changes to the docs are format 544, and none of the versions
> I have installed can read or convert them.
> 
> Now, say I have spotted errors or improvements in or for them, like
> latest UserGuide.de.lyx:
> 
> 26812  selbst) Formate für alle verfügbarren Typen von Verweisen
> vordefiniert.
> 
> How to proceed?
> 
> Proposal:
> – more intermediate alphas, betas, at least in sync with the current
> file-format.

Mike makes a good point. He wants to help with testing and improving the
documentation but cannot because of the file format. What is our policy
on updating the file format? I believe we only do that when we have to
update the format because we are using a new feature. Is that right?

Mike, we could tell you how to (without needing to compile) use lyx2lyx
to convert the new documentation back to e.g. alpha1-1 format so you
could read it. I'm not sure if that would help or not.

By the way, thanks for your interest in testing, Mike!

Scott


signature.asc
Description: PGP signature


alpha beta lyx-formats and devel versions of the docs

2017-07-25 Thread mn
The latest publicly available binaries are for alpha1-1.
The latest changes to the docs are format 544, and none of the versions
I have installed can read or convert them.

Now, say I have spotted errors or improvements in or for them, like
latest UserGuide.de.lyx:

26812selbst) Formate für alle verfügbarren Typen von Verweisen
vordefiniert.

How to proceed?

Proposal:
– more intermediate alphas, betas, at least in sync with the current
file-format.

greetings
Mike