Re: Update to the release notes
On Thursday 19 July 2007 06:33:31 Angus Leeming wrote: Attached is my take on it. A. Thanks Angus, I have included it in my changes. -- José Abílio
Re: Update to the release notes
On Thursday 19 July 2007 06:33:31 Angus Leeming wrote: > Attached is my take on it. > > A. Thanks Angus, I have included it in my changes. -- José Abílio
Re: Update to the release notes
José Matos wrote: Hello, I propose to warn users of 1.5.0 regarding the downgrade to 1.4 and 1.3 documents. I intend to commit the following patch and I would appreciate suggestion to change the spelling, grammar and content of the note. Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19114) +++ RELEASE-NOTES (working copy) @@ -19,13 +19,13 @@ using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +is to use iconv. Using bash, the script below should work: + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l The diff above doesn't show anything different AFAICT. +- Reverting 1.5 LyX documents to previous versions +Since unicode is supported in version 1.5 the dowgrade option to 1.4 *U*nicode dow*n*grade +and 1.3 lyx documents may be lossy. In those cases where no meaningful +convertion conversion + was possible the characters will be replaced by a +placeholder ???. + +We have done our best effort to make the transition the smoothest as smooth as +possible, if problems remain please report them to the users mailing +list. developers list?
Re: Update to the release notes
José Matos wrote: --- RELEASE-NOTES (revision 19114) +++ RELEASE-NOTES (working copy) @@ -19,13 +19,13 @@ using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed but they nust be valid UTF-8 strings. One way of doing the conversion nust? -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +is to use iconv. Using bash, the script below should work: + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l done rm tmp.txt @@ -35,7 +35,17 @@ same document, the cursor position is sometimes not correctly restored when you switch from one view to the other. +- Reverting 1.5 LyX documents to previous versions +Since unicode is supported in version 1.5 the dowgrade option to 1.4 downgrade +and 1.3 lyx documents may be lossy. In those cases where no meaningful +convertion was possible the characters will be replaced by a +placeholder ???. + +We have done our best effort to make the transition the smoothest +possible, if problems remain please report them to the users mailing +list. + Note: There may later be an updated list of known issues online at http://wiki.lyx.org/LyX/ReleaseNotes -- Peter Kümmel
Re: Update to the release notes
On Wednesday 18 July 2007 13:45:27 Abdelrazak Younes wrote: The diff above doesn't show anything different AFAICT. The text has ^M at the end of lines. -- José Abílio
Re: Update to the release notes
José Matos wrote: Hello, I propose to warn users of 1.5.0 regarding the downgrade to 1.4 and 1.3 documents. I intend to commit the following patch and I would appreciate suggestion to change the spelling, grammar and content of the note. Regards, Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19114) +++ RELEASE-NOTES (working copy) @@ -19,13 +19,13 @@ using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +is to use iconv. Using bash, the script below should work: + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l done rm tmp.txt Attached is my take on it. A. Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19124) +++ RELEASE-NOTES (working copy) @@ -15,19 +15,21 @@ - User layout files must be converted to UTF-8 -In previous version, layout styles were allowed to use non-ASCII names +In previous versions, layout styles were allowed to use non-ASCII names using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed -but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +but they must be valid UTF-8 strings. One way of doing the conversion +is to use iconv. Using bash, the script below should work: + +#! /bin/sh + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l done -rm tmp.txt +rm -f tmp.txt - Cursor restoration problems with Multiple-View
Re: Update to the release notes
José Matos wrote: Hello, I propose to warn users of 1.5.0 regarding the downgrade to 1.4 and 1.3 documents. I intend to commit the following patch and I would appreciate suggestion to change the spelling, grammar and content of the note. Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19114) +++ RELEASE-NOTES (working copy) @@ -19,13 +19,13 @@ using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +is to use iconv. Using bash, the script below should work: + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l The diff above doesn't show anything different AFAICT. +- Reverting 1.5 LyX documents to previous versions +Since unicode is supported in version 1.5 the dowgrade option to 1.4 *U*nicode dow*n*grade +and 1.3 lyx documents may be lossy. In those cases where no meaningful +convertion conversion + was possible the characters will be replaced by a +placeholder ???. + +We have done our best effort to make the transition the smoothest as smooth as +possible, if problems remain please report them to the users mailing +list. developers list?
Re: Update to the release notes
José Matos wrote: > --- RELEASE-NOTES (revision 19114) > +++ RELEASE-NOTES (working copy) > @@ -19,13 +19,13 @@ > using the local encodings. LyX-1.5 now assumes that all layout files are > UTF-8 encoded. This means that non-ASCII style names are still allowed > but they nust be valid UTF-8 strings. One way of doing the conversion nust? > -is to use iconv. Using bash, the script below should work: > - > -cd /path/to/layouts > -for l in * > -do > - cp $l tmp.txt > - iconv -f latin1 -t utf8 tmp.txt -o $l > +is to use iconv. Using bash, the script below should work: > + > +cd /path/to/layouts > +for l in * > +do > + cp $l tmp.txt > + iconv -f latin1 -t utf8 tmp.txt -o $l > done > rm tmp.txt > > @@ -35,7 +35,17 @@ > same document, the cursor position is sometimes not correctly restored > when you switch from one view to the other. > > +- Reverting 1.5 LyX documents to previous versions > > +Since unicode is supported in version 1.5 the dowgrade option to 1.4 downgrade > +and 1.3 lyx documents may be lossy. In those cases where no meaningful > +convertion was possible the characters will be replaced by a > +placeholder ???. > + > +We have done our best effort to make the transition the smoothest > +possible, if problems remain please report them to the users mailing > +list. > + > Note: There may later be an updated list of known issues online at > http://wiki.lyx.org/LyX/ReleaseNotes > -- Peter Kümmel
Re: Update to the release notes
On Wednesday 18 July 2007 13:45:27 Abdelrazak Younes wrote: > The diff above doesn't show anything different AFAICT. The text has ^M at the end of lines. -- José Abílio
Re: Update to the release notes
José Matos wrote: Hello, I propose to warn users of 1.5.0 regarding the downgrade to 1.4 and 1.3 documents. I intend to commit the following patch and I would appreciate suggestion to change the spelling, grammar and content of the note. Regards, Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19114) +++ RELEASE-NOTES (working copy) @@ -19,13 +19,13 @@ using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +is to use iconv. Using bash, the script below should work: + +cd /path/to/layouts +for l in * +do + cp $l tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o $l done rm tmp.txt Attached is my take on it. A. Index: RELEASE-NOTES === --- RELEASE-NOTES (revision 19124) +++ RELEASE-NOTES (working copy) @@ -15,19 +15,21 @@ - User layout files must be converted to UTF-8 -In previous version, layout styles were allowed to use non-ASCII names +In previous versions, layout styles were allowed to use non-ASCII names using the local encodings. LyX-1.5 now assumes that all layout files are UTF-8 encoded. This means that non-ASCII style names are still allowed -but they nust be valid UTF-8 strings. One way of doing the conversion -is to use iconv. Using bash, the script below should work: - -cd /path/to/layouts -for l in * -do - cp $l tmp.txt - iconv -f latin1 -t utf8 tmp.txt -o $l +but they must be valid UTF-8 strings. One way of doing the conversion +is to use iconv. Using bash, the script below should work: + +#! /bin/sh + +cd /path/to/layouts +for l in * +do + cp "$l" tmp.txt + iconv -f latin1 -t utf8 tmp.txt -o "$l" done -rm tmp.txt +rm -f tmp.txt - Cursor restoration problems with Multiple-View
