lyx.org emails
Hi, everyone owning @lyx.org address should have received few minuttes back an email with the subject "lyx.org email transition (hopefully) finished". If you did not receive it let me know, so we can fix it. Pavel -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: lyx.org down?
On Wed, Jan 31, 2018 at 05:29:38AM +, Joel Kulesza wrote: > Just came up for me. Thanks, seems fine here now also. Scott signature.asc Description: PGP signature
Re: lyx.org down?
Just came up for me. On Tue, Jan 30, 2018 at 10:23 PM, Scott Kostyshak wrote: > lyx.org is not responding to me. > > Scott >
lyx.org down?
lyx.org is not responding to me. Scott signature.asc Description: PGP signature
Re: missing forward to https for lyx.org
Am 24.12.2017 um 08:16 schrieb Christian Ridderström:
> IIRC, rewrites isn't done by .htaccess by the main Apache
configuration files under /etc/httpd/.
OK. I am a beginner with these things. I found the solution with
.htaccess by googling and it works.
It should work if you replace in www.lyx.org.conf
> RewriteEngine On
> RewriteLog /var/log/httpd/lyx.org_rewrite.log
> RewriteLogLevel 1
> #RewriteCond %{HTTP_POST} ^lyx\.org.*
> RewriteRule ^/(.*) http://www.lyx.org/$1 [L,R]
with
RewriteEngine On
RewriteLog /var/log/httpd/lyx.org_rewrite.log
RewriteLogLevel 1
RewriteCond %{HTTP_POST} ^lyx\.org [NC]
RewriteCond %{SERVER_PORT} 80
RewriteRule ^/(.*) https://www.lyx.org/$1 [L,R]
For a Wordpress page the solution was even simpler: in the dashboards
one simply uses https:// for the location of Wordpress.
Since lyx.org is based of PmWiki maybe the relocation to https can be
done there too by a setting within PmWiki (similar to the Wordpress
solution)?
> Maybe we should ask on the users' list if there's anyone there with
experience with Apache configuration files and rewrite?
Good idea.
thanks and regards
Uwe
missing forward to https for lyx.org
I noticed that calling http://www.lyx.org does not automatically forward/rewrite to https://www.lyx.org I did this this week for a private website by adding some code to the .htaccess file. Therefore I think that this should be possible for lyx.org as well without troubles. Christian and Richard, could you please have a look? thanks and regards Uwe
Re: linked email addresses on lyx.org
El 14.12.2017 a las 08:43, Jürgen Spitzmüller escribió: These 2 pages needs to be updated: http://www.lyx.org/Credits http://www.lyx.org/BlanketPermission Done. Thanks. I was looking how this is done and noted that they contain the full email addresses of all of us. Perfect for Spam bots. So can't we use just the text of the addresses instead of links? The inc file themselves do not contain valid addresses. They are created dynamically by php. Christian, could you please have a look if this can be avoided? thanks and regards Uwe
Re: linked email addresses on lyx.org
Am Mittwoch, den 13.12.2017, 19:32 +0100 schrieb Uwe Stöhr: > These 2 pages needs to be updated: > http://www.lyx.org/Credits > http://www.lyx.org/BlanketPermission Done. > I was looking how this is done and noted that they contain the full > email addresses of all of us. Perfect for Spam bots. So can't we use > just the text of the addresses instead of links? The inc file themselves do not contain valid addresses. They are created dynamically by php. > How can I update http://www.lyx.org/Credits It's a subversion repo: http://www.lyx.org/trac/browser/www-user Jürgen > thanks and regards > Uwe signature.asc Description: This is a digitally signed message part
linked email addresses on lyx.org
These 2 pages needs to be updated: http://www.lyx.org/Credits http://www.lyx.org/BlanketPermission I was looking how this is done and noted that they contain the full email addresses of all of us. Perfect for Spam bots. So can't we use just the text of the addresses instead of links? How can I update http://www.lyx.org/Credits thanks and regards Uwe
Re: 404 on manuals on lyx.org
Le 22/08/2017 à 19:08, Tommaso Cucinotta a écrit :
On 22/08/2017 09:08, Jean-Pierre Chrétien wrote:
-) 4 langs with complete 5 manuals on the page (Intro, Tutorial, UserGuide,
Math, Customization, EmbeddedObjects).
Additional is missing there, shouldn't it be added? It's kind of UserGuide2...
we have only 5 Additional.lyx manuals. For reference, this is the complete dump
[1]. What are the .16.lyx ones ?
I guess, manuals for lyx version 1.6 (last major release of the 1 series). I
don't think that this version is used anymore, but who knows?
The dump shows for current version:
- 7 real manuals: Intro, Tutorial, UserGuide, Math, Embedded, Customization
and Additional
- 2 help docs from automated build reflecting the local setup: Shortcuts,
LatexConfig
- 2 ancillary files: DummyDocument{1,2}
- 2 hidden documents (not appearing in the help menu): Formula-numbering,
MergedManuals
It misses:
- 1 help doc from automated build: Lyx Functions
- 14 specific help docs which are located in the examples folder
- 1 welcome file (example folder as well)
The example folder has localized subfolders.
I think that only the 7 real manuals and (possibly) the specialized ones should
appear in the wiki page. Maybe the MergedManuals would be useful also, if it can
be built in a an automated manner. The manuals are already searchable from
Edition>Search & Replace, but it would be a plus to be able to get the global plan.
--
Jean-Pierre
Re: 404 on manuals on lyx.org
On 22/08/2017 09:08, Jean-Pierre Chrétien wrote:
-) 4 langs with complete 5 manuals on the page (Intro, Tutorial, UserGuide,
Math, Customization, EmbeddedObjects).
Additional is missing there, shouldn't it be added? It's kind of UserGuide2...
we have only 5 Additional.lyx manuals. For reference, this is the complete dump
[1]. What are the .16.lyx ones ?
Thanks,
T.
[1]
$ find . -maxdepth 1 -name '*.lyx' | while read f; do echo ${f##./} $(find .
-name ${f##./} | wc -l); done | sort -k2 -nr
Intro.lyx 26
Tutorial.lyx 22
Shortcuts.lyx 8
UserGuide.lyx 5
Math.lyx 5
EmbeddedObjects.lyx 5
Customization.lyx 5
Additional.lyx 5
Formula-numbering.lyx 4
DummyDocument2.lyx 3
DummyDocument1.lyx 3
MergedManuals.lyx 2
LaTeXConfig.lyx 2
UserGuide.16.lyx 1
Tutorial.16.lyx 1
Shortcuts.16.lyx 1
MergedManuals.16.lyx 1
Math.16.lyx 1
LFUNs.lyx 1
LFUNs.16.lyx 1
LaTeXConfig.16.lyx 1
Intro.16.lyx 1
Formula-numbering.16.lyx 1
EmbeddedObjects.16.lyx 1
DummyDocument2.16.lyx 1
DummyDocument1.16.lyx 1
Development.lyx 1
Development.16.lyx 1
Customization.16.lyx 1
Additional.16.lyx 1
Re: 404 on manuals on lyx.org
Dear Tommaso, On 2017-08-21, Tommaso Cucinotta wrote: > I checked that, with the converted manuals from the > generate_manuals_for_web.sh script, we have: > -) 4 langs with complete 5 manuals on the page (Intro, Tutorial, >UserGuide, Math, Customization, EmbeddedObjects). > -) 22 langs with the Intro (18 besides the 4 complete langs) > -) 18 langs with the Tutorial (14 besides the 4 complete langs) > -) 17 langs with both Intro and Tutorial > But who knows how many of these are actually maintained and updated to > what LyX release ? > So, I was wondering whether it was worth to go for: > -) growing the current table to a maxi table (22 langs x 5 manuals) >with all possible intersections (likely different tables for >different doc types) No. > -) adding to the current table a new one, pointing only to the Intro & >Tutorial of the 22 langs having at least one of them. Yes. This would also allow to add a caveat: "these manuals may be outdated." > Thoughts ? I'd use a layout with the different formats of one document in one common cell: Manual English Français Deutsch Español IntroductionHTML HTML HTMLHTML LyX LyXLyX LyX PDF PDFPDF PDF TutorialHTML HTML HTMLHTM LyX LyXLyX LyX PDF PDFPDF PDF ... Additonal The HTML would be added once "fit for publication". Either fix major issues with the native export or use elyxer (exporting to LyX-2.0 format and then converting with elyxer should give better results, as the elyxer is quite old by now: "* eLyXer version 1.2.5 (2015-02-26)". Günter
Re: 404 on manuals on lyx.org
Le 21/08/2017 à 23:29, Tommaso Cucinotta a écrit : On 21/08/2017 23:09, Christian Ridderström wrote: - The link texts could be LyX vs PDF instead of EN/FR etc. tried also to play with the clikkable PDF/LyX icons that bring you to the file, but if we get tens of those I expect the page to become difficult to browse. I added example of how you can use an image as the "link text". Also how it can be resized. But it's better if the uploaded image has the proper size from the beginning. +1, thanks. I checked that, with the converted manuals from the generate_manuals_for_web.sh script, we have: -) 4 langs with complete 5 manuals on the page (Intro, Tutorial, UserGuide, Math, Customization, EmbeddedObjects). Additional is missing there, shouldn't it be added? It's kind of UserGuide2... -- Jean-Pierre
Re: 404 on manuals on lyx.org
On 21/08/2017 23:09, Christian Ridderström wrote: - The link texts could be LyX vs PDF instead of EN/FR etc. tried also to play with the clikkable PDF/LyX icons that bring you to the file, but if we get tens of those I expect the page to become difficult to browse. I added example of how you can use an image as the "link text". Also how it can be resized. But it's better if the uploaded image has the proper size from the beginning. +1, thanks. I checked that, with the converted manuals from the generate_manuals_for_web.sh script, we have: -) 4 langs with complete 5 manuals on the page (Intro, Tutorial, UserGuide, Math, Customization, EmbeddedObjects). -) 22 langs with the Intro (18 besides the 4 complete langs) -) 18 langs with the Tutorial (14 besides the 4 complete langs) -) 17 langs with both Intro and Tutorial But who knows how many of these are actually maintained and updated to what LyX release ? So, I was wondering whether it was worth to go for: -) growing the current table to a maxi table (22 langs x 5 manuals) with all possible intersections (likely different tables for different doc types) -) adding to the current table a new one, pointing only to the Intro & Tutorial of the 22 langs having at least one of them. Both would have to be auto-generated of course. Thoughts ? T.
Re: 404 on manuals on lyx.org
On 21/08/2017 17:02, Pavel Sanda wrote: https://wiki.lyx.org/uploads/ or from within wiki: uploads:/path/file.png solved, I was using "uploads:path/to/..." instead of "uploads:/path/to/..." A minor issue I'm seeing is that, clicking on a tutorial .lyx file in any language, Firefox proposes me to open the file with LyX, whilst clicking on any other .lyx document (not a tutorial), Firefox opens its text content in the webpage. Some misconfiguration of MIME types on the server ? Thanks, T.
Re: 404 on manuals on lyx.org
Tommaso Cucinotta writes: > On 20/08/2017 20:20, Christian Ridderström wrote: >> - Perhaps write out English, Español etc in the headings > > I made an attempt to rotate the text, to keep the table compact, via > CSS attributes, but the rotated one didn't show well, because it was > rotating the cell borders as well :(. Perhaps a hack might be to keep > the heading cell as a perfect square ;-P. I tested making the header text smaller, have a look at the playground page now. Looks ok to me, but maybe you think it's still to wide? >> - The link texts could be LyX vs PDF instead of EN/FR etc. > > tried to upload a .pdf icon from LyX, I've put it here: > Now, how can I get that image to show up in the wiki ? What is the URL > it becomes visible as ? I tried to follow pmwiki's (upload:, attach:), > but didn't work. Seems like you've solved it now. I added example of how you can use an image as the "link text". Also how it can be resized. But it's better if the uploaded image has the proper size from the beginning. /Christian
Re: 404 on manuals on lyx.org
Pavel Sanda wrote: > Tommaso Cucinotta wrote: > > Now, how can I get that image to show up in the wiki ? What is the URL it > > becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but > > didn't work. > > https://wiki.lyx.org/uploads/ or from within wiki: uploads:/path/file.png p
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > Now, how can I get that image to show up in the wiki ? What is the URL it > becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but > didn't work. https://wiki.lyx.org/uploads/ Pavel
Re: 404 on manuals on lyx.org
On 20/08/2017 20:20, Christian Ridderström wrote: - Perhaps write out English, Español etc in the headings I made an attempt to rotate the text, to keep the table compact, via CSS attributes, but the rotated one didn't show well, because it was rotating the cell borders as well :(. Perhaps a hack might be to keep the heading cell as a perfect square ;-P. - The link texts could be LyX vs PDF instead of EN/FR etc. tried to upload a .pdf icon from LyX, I've put it here: ftp wiki.lyx.org Connected to www.lyx.org. 220 Welcome to the LyX wiki FTP service. Name (wiki.lyx.org:tommaso): lyxftp 331 Please specify the password. Password: 230 Login successful. cd LyX cd Manuals put buffer-export_pdf.png dir -rw-r--r--1 ftp ftp 8170 Aug 21 12:46 buffer-export_pdf.png Now, how can I get that image to show up in the wiki ? What is the URL it becomes visible as ? I tried to follow pmwiki's (upload:, attach:), but didn't work. Do you mean how to make an image appear on a wiki page (http://www.pmwiki.org/wiki/PmWiki/Images) or how to upload an image onto the server? seemingly the upload part is ok, I just can't make it visible from a wiki page now. General tip: Test things in the group "/Test", e.g. see here http://wiki.lyx.org/Test/Images that's exactly what I was trying to follow :( Or use a playground page, e.g. http://wiki.lyx.org/Playground/AngusWikiSandbox moved Manuals2 to http://wiki.lyx.org/Playground/ManualsPG (feel free to edit, if you can let any image appear there, we're done!) Thx, T.
Re: CI job generating PDFs? Was: 404 on manuals on lyx.org
On 2017-08-20, Christian Ridderström wrote: > Guenter Milde writes: >> On 2017-08-11, Christian Ridderström wrote: >>> On 11 August 2017 at 13:03, Pavel Sanda wrote: Christian Ridderström wrote: > [*] It might make sense to have a CI job that builds PDFs etc from the > manuals as a separate test. ... > Some months ago I created a CI job that runs (some of?) the tests. ... > Due to the many tests failing it didn't seem so useful to deploy. > Here's the (presumably) relevant line from the log: > 68% tests passed, 2073 tests failed out of 6522 This warrants a look into the test setup, but may be no problem if the very small subset of tests exporting documentation to the default output format works fine. However, ... > From there I then navigated to e.g. > > https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ws/build/autotests/out-home/sv/splash_defaultF.pdf3 > I was able to download that file and view it, although my mac required > me (!!!???) to first rename the extension from .pdf3 to .pdf, even when > I tried to launch 'Preview' on the file from the command line. We would need to: * select the *.pdf2 (PDF(pdflatex) files matching the manuals and rename them to *.pdf * select required graphic files * move them into a sensible directory hierarchy All in all, it seems simpler to keep the documentation generation as a separate task. Günter
Re: 404 on manuals on lyx.org
Tommaso Cucinotta writes: > On 15/08/2017 22:11, Uwe Stöhr wrote: >> So fine with me if you change the order. > > done. Also, I gave a try to pmwiki tables, to get to a more compact form: > > http://wiki.lyx.org/LyX/Manuals2 The table looks nice to me. Some minor thoughts: - Perhaps write out English, Español etc in the headings - The link texts could be LyX vs PDF instead of EN/FR etc. - Perhaps state the LyX release before the table > (might be visually improved with some .lyx/.pdf icons, plus > country-code flags, but don't know how to attach images to the > lyx.org wiki) Do you mean how to make an image appear on a wiki page (http://www.pmwiki.org/wiki/PmWiki/Images) or how to upload an image onto the server? General tip: Test things in the group "/Test", e.g. see here http://wiki.lyx.org/Test/Images Or use a playground page, e.g. http://wiki.lyx.org/Playground/AngusWikiSandbox /Christian PS. It's a good idea to create a page like Manuals2 in the group Playground/ for others to review. Then when people like it, move improvements into LyX/Manuals. This is because we likely don't want to have two pages. This way we won't have to figure out how to delete a wiki page (which I've completely forgotten how to do). PPS. We can also consider maintaining an official page http://www.lyx.org/LyX/Manuals as the web pages are actually wiki pages, the task of creating and updating the page is the same.
CI job generating PDFs? Was: 404 on manuals on lyx.org
Guenter Milde writes: > On 2017-08-11, Christian Ridderström wrote: >> On 11 August 2017 at 13:03, Pavel Sanda wrote: >>> Christian Ridderström wrote: > >>> > [*] It might make sense to have a CI job that builds PDFs etc from the >>> > manuals as a separate test. > > This is already done by Kornel's export test suite. All manuals are > regularely exported and failures mailed to the list. > > There are known failures in additional tests for various "exotic" export > routes and configurations but AFAIK all documentation exports fine using the > set standard export format (mostly PDF(pdflatex)). Some months ago I created a CI job that runs (some of?) the tests. The CI job is currently located here https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ Due to the many tests failing it didn't seem so useful to deploy. Here's the (presumably) relevant line from the log: 68% tests passed, 2073 tests failed out of 6522 That line is from job#310, i.e. here (might require logging in): https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/310/console I also logged in to the CI node and checked the workspace to look for PDFs [2]. There's a whole bunch of PDFs in that list, so maybe we already have a CI job that generates (some) of the manuals as PDFs? The workspace of the most recent job can be accessed like this: https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ws/ >From there I then navigated to e.g. https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ws/build/autotests/out-home/sv/splash_defaultF.pdf3 I was able to download that file and view it, although my mac required me (!!!???) to first rename the extension from .pdf3 to .pdf, even when I tried to launch 'Preview' on the file from the command line. /Christian [1] This job is running regulary. Previously it checked if Git had changed every eight hours, but as it's a big job I just tweaked this to only check Git on Thursdays. [2] I logged in to the CI node and checked the workspace to look for PDFs. This is what I found ci@ubuntu1604:~/workspace/testing-Jenkins/ctest$ find . -name "*.pdf" ./lib/examples/beamer-icsi-logo.pdf ./lib/doc/de/clipart/Zusammenfassung.pdf ./lib/doc/clipart/3D-structure-distort.pdf ./lib/doc/clipart/2D-intensity-plot.pdf ./lib/doc/clipart/Abstract.pdf ./lib/doc/clipart/endnotes.pdf ./lib/doc/clipart/without_fntright.pdf ./lib/doc/clipart/Star-structure.pdf ./lib/doc/clipart/with_fntright.pdf ./lib/doc/es/clipart/Resumen.pdf ./build/lib/examples/beamer-icsi-logo.pdf ./build/autotests/out-home/aastex6_defaultF.pdf ./build/autotests/out-home/de/beamer-article_defaultF.pdf ./build/autotests/out-home/de/MultilingualCaptions_defaultF.pdf ./build/autotests/out-home/de/serienbrief1_defaultF.pdf ./build/autotests/out-home/de/Math_defaultF.pdf ./build/autotests/out-home/de/serienbrief3_defaultF.pdf ./build/autotests/out-home/de/Braille_defaultF.pdf ./build/autotests/out-home/de/Tutorial_defaultF.pdf ./build/autotests/out-home/de/ItemizeBullets_defaultF.pdf ./build/autotests/out-home/de/Formelnummerierung_defaultF.pdf ./build/autotests/out-home/de/FeynmanDiagrams_defaultF.pdf ./build/autotests/out-home/de/Intro_defaultF.pdf ./build/autotests/out-home/de/Customization_defaultF.pdf ./build/autotests/out-home/de/Shortcuts_defaultF.pdf ./build/autotests/out-home/de/Additional_defaultF.pdf ./build/autotests/out-home/de/beispiel_gelyxt_defaultF.pdf ./build/autotests/out-home/de/DummyDocument1_defaultF.pdf ./build/autotests/out-home/de/beispiel_roh_defaultF.pdf ./build/autotests/out-home/de/DummyDocument2_defaultF.pdf ./build/autotests/out-home/de/EmbeddedObjects_defaultF.pdf ./build/autotests/out-home/de/Lebenslauf_defaultF.pdf ./build/autotests/out-home/de/linguistics_defaultF.pdf ./build/autotests/out-home/de/serienbrief2_defaultF.pdf ./build/autotests/out-home/de/splash_defaultF.pdf ./build/autotests/out-home/de/Dezimal_defaultF.pdf ./build/autotests/out-home/de/UserGuide_defaultF.pdf ./build/autotests/out-home/testcases_basic_defaultF.pdf ./build/autotests/out-home/mixing_inTitle_layouts_defaultF.pdf ./build/autotests/out-home/latex/arabic_simple_defaultF.pdf ./build/autotests/out-home/latex/utf8-plain-with-tex-fonts_defaultF.pdf ./build/autotests/out-home/beamer-article_defaultF.pdf ./build/autotests/out-home/achemso_defaultF.pdf ./build/autotests/out-home/serial_letter1_defaultF.pdf ./build/autotests/out-home/Formula-numbering_defaultF.pdf ./build/autotests/out-home/MultilingualCaptions_defaultF.pdf ./build/autotests/out-home/IEEEtran-CompSoc_defaultF.pdf ./build/autotests/out-home/architecture_defaultF.pdf ./build/autotests/out-home/sr/Braille_defaultF.pdf ./build/autotests/out-home/sr/splash_defaultF.pdf ./build/autotests/out-home/revtex4-1_defaultF.pdf ./build/autotests/out-home/obsolete/g-brief-en_defaultF.pdf ./build/autotests/out-home/obsolete/g-brief-de_defaultF.pdf ./build/autotests/out-home/cs/priklad_zLyXovany_defaultF.pdf ./build/autotests/out-home/cs/Tutorial_defaultF.pdf ./build/autotests
Re: 404 on manuals on lyx.org
Pavel Sanda writes: > Yes, I will try to push our xhtml output to the web during next week or > two so more ppl can check the output with their own eyes. > I guess many of the bugs will rather easy-fix business. Where/which URL(s) and with what kind of structure did you intend to use? Also, are you planning one using two "areas" on the web? I.e. - An area (URL) for staging/testing/reviewing the pages - An area (URL) for the published/deployed/reviewed pages? I would recommend using two separate areas for robustness and convenience. And further that we'd tell bots to not index the staging/testing area. /Christian
Re: 404 on manuals on lyx.org
Uwe Stöhr writes: > El 11.08.2017 a las 08:35, Christian Ridderström escribió: > >> I can't do an anonymous login to ftp://ftp.lyx.de. Uwe wrote: > I'll try to repair it later today. I just tested and I still cannot do anonymous login to ftp://ftp.lyx.de. However, according to the message I get, I'm guessing anonymous isn't allowed => so it's probably the way it should be. >> I can do an anonymous login to http://ftp.lyx.de. Still works => good >> I am _not_ able to see the subfolder /Documentation/, so it's gone, moved >> or permissions changed. And this now also seem to work => good I also did a successful spot check and followed one of the links from the wiki page 'Manuals' => good. Thanks for fixing this Uwe. Best regards, Christian
FTP service on regular LyX server (Was: 404 on manuals on lyx.org)
Uwe Stöhr writes: >> With our release frequency, it shouldn't be a problem to manually [*] >> update PDFs and upload the official manuals. > > I only used ft.lyx.de because I could not upload files anymore to > wiki.lyx.org. Is this now again possible? Hi Uwe, Yes, there's been a working ftp server on the regular LyX server for some time. Don't remember for how long though. > if so I would switch back to wiki.lyx.org. That's kind of funny: I thought you intentionally were using a separate FTP server to reduce the load on our regular server...? > How do I upload there files? Please try and follow the instructions here: http://wiki.lyx.org/Site/AboutUploading Also please don't hesitate to remark if the page is unclear -- or simply fix it of course. Regards, Christian PS. I'll e-mail the FTP password separately.
Re: 404 on manuals on lyx.org
On Thu, Aug 17, 2017 at 01:14:14AM +0200, Pavel Sanda wrote: > Richard Heck wrote: > > Seriously, if we're really going to make the manuals available in this > > form, that will provide us with some motivation to fix the worst of the > > bugs with XHTML output. Often, this simply means making some design > > So here we go: at this moment I am not capable even to preview xhtml output > of math manual at all in firefox: > > XML Parsing Error: undefined entity Location: > file:///tmp/lyx_tmpdir.ddMdYjE28061/lyx_tmpbuf1/Math.xhtml > Line Number 7050, Column 13: > &imaginary; > ^ > > (MathML enabled in doc options.) I can reproduce that Firefox doesn't show the file. Chromium does but also shows the error. Unfortunately, xmllint does not catch an error, so our xhtml tests pass for Math. I tried different xmllint options but couldn't get one to give me an error for this. Scott signature.asc Description: PGP signature
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > Here you go, script attached, it compiles the main manuals for all Unf. this script still has quite some troubles. Mainly, because -E html instead of -E xhtml was used... My hack with copying to /tmp is not enough, because we use in manuals our toolbars icons as well and lyx will grab those stored at lyx root -- mangled filenames will have again the full path in it. To get this right, we will need to whole lyx root in tmp/ which kinda sucks... Pavel
Re: 404 on manuals on lyx.org
Richard Heck wrote: > Seriously, if we're really going to make the manuals available in this > form, that will provide us with some motivation to fix the worst of the > bugs with XHTML output. Often, this simply means making some design So here we go: at this moment I am not capable even to preview xhtml output of math manual at all in firefox: XML Parsing Error: undefined entity Location: file:///tmp/lyx_tmpdir.ddMdYjE28061/lyx_tmpbuf1/Math.xhtml Line Number 7050, Column 13: &imaginary; ^ (MathML enabled in doc options.) Pavel
Re: 404 on manuals on lyx.org
On 15/08/2017 22:11, Uwe Stöhr wrote: So fine with me if you change the order. done. Also, I gave a try to pmwiki tables, to get to a more compact form: http://wiki.lyx.org/LyX/Manuals2 (might be visually improved with some .lyx/.pdf icons, plus country-code flags, but don't know how to attach images to the lyx.org wiki) this might be a start for providing URLs for more languages (some of the) manuals are available into. Feedback welcome, thanks. T.
Re: 404 on manuals on lyx.org
El 15.08.2017 a las 11:43, Tommaso Cucinotta escribió: Great! One minor comment: probably the order of manuals might be exactly reversed, Hi Tommaso, thanks for having a look. As it is a Wiki please change it as you like. In the past I already had this sorting: Tutorial UserGuide Math Embeddedobjects Customization So fine with me if you change the order. Also, PDFs are a great help for people looking for info on the web, but HTML exports would probably be even better on the web... In principle yes, in practice no. eLyXer (http://pinchito.es/elyxer/) is no longer developed since 4 years but still produces much better results than LyX's own HTML converter. I reported the major issues: http://www.lyx.org/trac/ticket/9328 http://www.lyx.org/trac/ticket/10445 http://www.lyx.org/trac/ticket/10437 http://www.lyx.org/trac/ticket/10438 We all lack time so Richard is not to blame here. I am no real developer and therefore don't have the ability to work on the HTML converter issues. Maybe you could have a look and simply steal from eLyXer? I propose this way because the developer of eLyXer got a lot of feedback from me and LyX users and implemented almost everything people requested. ( Here are the other LyXHTML bugs: http://www.lyx.org/trac/query?status=accepted&status=assigned&status=new&status=reopened&summary=~&component=xhtml+export&description=~&reporter=~&col=id&col=summary&col=reporter&col=status&col=type&col=severity&col=keywords&desc=1&order=id ) Out of curiosity: this page links only manuals for a few languages, what about the plethora of others ? The LyX docs are only more or less complete in English, german, french, Spanish and Japanese. On Windows with MiKTeX I am not able to compile Japanese documents otherwise I would have uploaded also a Japanese version. OK, I am lazy because with TeXLive it works and I don't have the time to play around with TeXLive at the moment. regards Uwe
Re: 404 on manuals on lyx.org
On 15/08/2017 02:53, Uwe Stöhr wrote: I set it now again and updated the manuals to LyX 2.2.3: http://wiki.lyx.org/LyX/Manuals Great! One minor comment: probably the order of manuals might be exactly reversed, to have easier stuff first, and more advanced stuff last. Also, PDFs are a great help for people looking for info on the web, but HTML exports would probably be even better on the web... Out of curiosity: this page links only manuals for a few languages, what about the plethora of others ? Is that because these languages are the only ones for which we have a complete set of manuals ? my2c, T.
Re: 404 on manuals on lyx.org
El 13.08.2017 a las 15:04, Uwe Stöhr escribió: damn, I repaired this already few months ago. I also complained about this automatic permission removal at my hoster... it turned out that the Documentation folder even got lost. I set it now again and updated the manuals to LyX 2.2.3: http://wiki.lyx.org/LyX/Manuals regards Uwe
Re: 404 on manuals on lyx.org
Richard Heck wrote: > Seriously, if we're really going to make the manuals available in this > form, that will provide us with some motivation to fix the worst of the > bugs with XHTML output. Often, this simply means making some design > decisions. Implementing them is not difficult, since the output routines > are self-contained. I'm busy, as we all are, but I can do some of that > work and provide pointers if others want to do some of it. Yes, I will try to push our xhtml output to the web during next week or two so more ppl can check the output with their own eyes. I guess many of the bugs will rather easy-fix business. Pavel
Re: 404 on manuals on lyx.org
On 08/13/2017 11:49 AM, Pavel Sanda wrote: > Tommaso Cucinotta wrote: >> On 13/08/2017 17:33, Pavel Sanda wrote: >>> Maybe we are seeing different phenomena. Here EmbeddedObjects compiles >> [...] >>> Apart from that it looks sort of OK. TeXLive 2012 here :) >> yes, the difference seems that you're exporting xhtml, whilst I was >> exporting .html. > You mean you are not exporting to LyXHTML target? That's the only one we > have under control. HTML is likely going through external latex2html > package and we shouldn't aim to go primarily through that convertor... Uh, oh, here we go again Seriously, if we're really going to make the manuals available in this form, that will provide us with some motivation to fix the worst of the bugs with XHTML output. Often, this simply means making some design decisions. Implementing them is not difficult, since the output routines are self-contained. I'm busy, as we all are, but I can do some of that work and provide pointers if others want to do some of it. Richard
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > On 13/08/2017 17:33, Pavel Sanda wrote: >> Maybe we are seeing different phenomena. Here EmbeddedObjects compiles > [...] >> Apart from that it looks sort of OK. TeXLive 2012 here :) > > yes, the difference seems that you're exporting xhtml, whilst I was > exporting .html. You mean you are not exporting to LyXHTML target? That's the only one we have under control. HTML is likely going through external latex2html package and we shouldn't aim to go primarily through that convertor... Pavel
Re: 404 on manuals on lyx.org
On 13/08/2017 16:58, Tommaso Cucinotta wrote: On my system, despite having installed texlive-lang-all, not all of them succeed in compilation. I was missing xetex for the ja (and presumably he) languages. T.
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > Here you go, script attached, it compiles the main manuals for all > available languages, and auto-builds an index.html linking them all. Feel > free to add it to the LyX git (couldn't identify a suitable location in the > git tree for such a tool). > > On my system, despite having installed texlive-lang-all, not all of them > succeed in compilation. > > Result as can be seen at (file lyxdoc.tar.gz, once it's done uploading): > > https://drive.google.com/open?id=0B6A-8XYYe1nYUlg3U2YyQm0xQVU Cool! I will try to push this forward next week, to busy right now. Pavel
Re: 404 on manuals on lyx.org
On 13/08/2017 17:33, Pavel Sanda wrote: Maybe we are seeing different phenomena. Here EmbeddedObjects compiles [...] Apart from that it looks sort of OK. TeXLive 2012 here :) yes, the difference seems that you're exporting xhtml, whilst I was exporting .html. Just checked that the .xhtml out seems ok, instead the .html export is completely broken, I get on terminal a number of Empty picture! errors, and I just get a number of random PICT in the output, without anything / any text visible (see attached). T. LY X’s detailed Figure, Table, Floats, Notes, Boxes and External Material manual by the LY X Team* Version 2.2.x August 13, 2017 *If you have comments or error corrections, please send them to the LY X Documentation mailing list: lyx-d...@lists.lyx.org Contents
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > On 13/08/2017 12:48, Pavel Sanda wrote: >> You need latin,french&german to build the main (english) manuals? > > yes, latin for the "ipse lorum blah blah", french I suspect accidentally > tags a few English paragraphs in one of the manuals, whilst german is part > of the description of some of the inter-language features of LyX (umlauts, > accents, ...) can't remember more now. I checked now, it's the same with French (description of some example hack in Customization manual). > for now, EmbeddedObjects has been excluded from the auto-build in the > script I just sent. > I'm not understanding your explanation above of the problem. Maybe we are seeing different phenomena. Here EmbeddedObjects compiles into xhtml but in the middle of output it include couple of lines from some arbitraty .lyx file referenced by listings inset. That presumably works with latex, but with xhtml we (understandably) dump th whole .lyx file into the output. Apart from that it looks sort of OK. TeXLive 2012 here :) Pavel
Re: 404 on manuals on lyx.org
On 13/08/2017 12:48, Pavel Sanda wrote: You need latin,french&german to build the main (english) manuals? yes, latin for the "ipse lorum blah blah", french I suspect accidentally tags a few English paragraphs in one of the manuals, whilst german is part of the description of some of the inter-language features of LyX (umlauts, accents, ...) can't remember more now. -) Intro, UserGuide, Tutorial, Development, Math, Customization, Additional, LFUNs compile fine (pdf and html); -) major: I'm able to pdf-compile EmbeddedObjects, but HTML compilation has problems; I'd say it's 'solvable' if the .lyx file which is dumped via listings is changed to one which is much much shorter. It won't be fixed, but it wouldn't dump 30 pages of nonsense either... for now, EmbeddedObjects has been excluded from the auto-build in the script I just sent. I'm not understanding your explanation above of the problem. that has easy workaround along those lines (not supposed to be working out of the box): SVN_OUT=~/web/stabledoc/ W=/tmp/stabledoc B=~/lyx/stable/src/lyx got it, took into account into the script just sent. Thanks, T.
Re: 404 on manuals on lyx.org
Here you go, script attached, it compiles the main manuals for all available
languages, and auto-builds an index.html linking them all. Feel free to add it
to the LyX git (couldn't identify a suitable location in the git tree for such
a tool).
On my system, despite having installed texlive-lang-all, not all of them
succeed in compilation.
Result as can be seen at (file lyxdoc.tar.gz, once it's done uploading):
https://drive.google.com/open?id=0B6A-8XYYe1nYUlg3U2YyQm0xQVU
T.
On 13/08/2017 12:48, Pavel Sanda wrote:
Tommaso Cucinotta wrote:
On 11/08/2017 16:51, Pavel Sanda wrote:
I can prepare web corner for it on www.lyx.org if you decide to do it.
I quickly check the link you posted and the results seems good enough to
me to push it on the web if we can somewhat automatize it.
I gave a try to manual compilation of manuals :-), and here's the
experience:
-) minors along the way: I was missing texlive-lang-german, french, latin,
You need latin,french&german to build the main (english) manuals?
and texlive-humanities;
That's to be expected.
-) Intro, UserGuide, Tutorial, Development, Math, Customization,
Additional, LFUNs compile fine (pdf and html);
-) major: I'm able to pdf-compile EmbeddedObjects, but HTML compilation has
problems;
I'd say it's 'solvable' if the .lyx file which is dumped via listings
is changed to one which is much much shorter. It won't be fixed, but
it wouldn't dump 30 pages of nonsense either...
-) major: MergedManuals compilation complains about not being able to find
SpecialParagraphShape.tex or smth like that; that comes from
Additional.lyx, but Additional standalone compiles without problems, and
the .tex file is there, so why does it fail when embedded within
MergedManuals ?
We don't need the merged manuals at this stage, just the main manuals would be
good enough.
-) minor: converted HTML files include images with export names alike
55_home_tommaso_lyx-trunk-ws_lyx_*, which includes the absolute path I was
exporting from -- ideally, we shouldn't include any (mangled) absolute path
when exporting (but only (mangled) relative paths), is there a TT/# for
this ?
that has easy workaround along those lines (not supposed to be working out of
the box):
SVN_OUT=~/web/stabledoc/
W=/tmp/stabledoc
B=~/lyx/stable/src/lyx
#prepare
cd lyx; mkdir $W; cp -r lib/doc $W ; cd ${W}/doc
#export
for manual in tutorial.lyx userguide.lyx ... ; do
$B -E pdf $manual
$B -E xhtml $manual
done
#sum results html; similarly for pdf
for outman in tutorialdir userguidedir ... ; do
rm -r ${SVN_OUT}/$outman
cp -r $outman ${SVN_OUT}/$outman
done
It just needs someone to tune the above script for proper names,
switches and so on...
The rest is deploying to web via svn (I can take care of myself if I get
the above camera-ready).
Pavel
manuals_for_web.sh
Description: application/shellscript
Re: 404 on manuals on lyx.org
El 11.08.2017 a las 08:35, Christian Ridderström escribió: I can't do an anonymous login to ftp://ftp.lyx.de. I can do an anonymous login to http://ftp.lyx.de. I am _not_ able to see the subfolder /Documentation/, so it's gone, moved or permissions changed. Hi Christian, damn, I repaired this already few months ago. I also complained about this automatic permission removal at my hoster. They setup new software and it seems that this is the reason I lost my permission settings - AGAIN. I'll try to repair it later today. With our release frequency, it shouldn't be a problem to manually [*] update PDFs and upload the official manuals. I only used ft.lyx.de because I could not upload files anymore to wiki.lyx.org. Is this now again possible? if so I would switch back to wiki.lyx.org. How do I upload there files? thanks and regards Uwe
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote:
> On 11/08/2017 16:51, Pavel Sanda wrote:
>> I can prepare web corner for it on www.lyx.org if you decide to do it.
I quickly check the link you posted and the results seems good enough to
me to push it on the web if we can somewhat automatize it.
> I gave a try to manual compilation of manuals :-), and here's the
> experience:
> -) minors along the way: I was missing texlive-lang-german, french, latin,
You need latin,french&german to build the main (english) manuals?
> and texlive-humanities;
That's to be expected.
> -) Intro, UserGuide, Tutorial, Development, Math, Customization,
> Additional, LFUNs compile fine (pdf and html);
> -) major: I'm able to pdf-compile EmbeddedObjects, but HTML compilation has
> problems;
I'd say it's 'solvable' if the .lyx file which is dumped via listings
is changed to one which is much much shorter. It won't be fixed, but
it wouldn't dump 30 pages of nonsense either...
> -) major: MergedManuals compilation complains about not being able to find
> SpecialParagraphShape.tex or smth like that; that comes from
> Additional.lyx, but Additional standalone compiles without problems, and
> the .tex file is there, so why does it fail when embedded within
> MergedManuals ?
We don't need the merged manuals at this stage, just the main manuals would be
good enough.
> -) minor: converted HTML files include images with export names alike
> 55_home_tommaso_lyx-trunk-ws_lyx_*, which includes the absolute path I was
> exporting from -- ideally, we shouldn't include any (mangled) absolute path
> when exporting (but only (mangled) relative paths), is there a TT/# for
> this ?
that has easy workaround along those lines (not supposed to be working out of
the box):
SVN_OUT=~/web/stabledoc/
W=/tmp/stabledoc
B=~/lyx/stable/src/lyx
#prepare
cd lyx; mkdir $W; cp -r lib/doc $W ; cd ${W}/doc
#export
for manual in tutorial.lyx userguide.lyx ... ; do
$B -E pdf $manual
$B -E xhtml $manual
done
#sum results html; similarly for pdf
for outman in tutorialdir userguidedir ... ; do
rm -r ${SVN_OUT}/$outman
cp -r $outman ${SVN_OUT}/$outman
done
It just needs someone to tune the above script for proper names,
switches and so on...
The rest is deploying to web via svn (I can take care of myself if I get
the above camera-ready).
Pavel
Re: 404 on manuals on lyx.org
On 08/12/2017 10:11 AM, Tommaso Cucinotta wrote: > On 12/08/2017 15:52, Tommaso Cucinotta wrote: >> I gave a try to manual compilation of manuals :-), and here's the >> experience: >> -) minors along the way: I was missing texlive-lang-german, french, >> latin, and texlive-humanities; >> -) Intro, UserGuide, Tutorial, Development, Math, Customization, >> Additional, LFUNs compile fine (pdf and html); >> -) major: I'm able to pdf-compile EmbeddedObjects, but HTML >> compilation has problems; >> -) major: MergedManuals compilation complains about not being able to >> find SpecialParagraphShape.tex or smth like that; that comes from >> Additional.lyx, but Additional standalone compiles without problems, >> and the .tex file is there, so why does it fail when embedded within >> MergedManuals ? > > forgot: > > -) minor: converted HTML files include images with export names alike > 55_home_tommaso_lyx-trunk-ws_lyx_*, which includes the absolute path I > was exporting from -- ideally, we shouldn't include any (mangled) > absolute path when exporting (but only (mangled) relative paths), is > there a TT/# for this ? Not as far as I know. Sounds like a pretty easy fix. Richard
Re: 404 on manuals on lyx.org
On 08/12/2017 09:52 AM, Tommaso Cucinotta wrote: > > I gave a try to manual compilation of manuals :-), and here's the > experience: > -) minors along the way: I was missing texlive-lang-german, french, > latin, and texlive-humanities; > -) Intro, UserGuide, Tutorial, Development, Math, Customization, > Additional, LFUNs compile fine (pdf and html); I'd guess that there is probably some weirdness in the HTML version of the math manual, if one looks through it carefully. But it's good to know it at least works. The others I'd expect are fine, though with some glitches. > -) major: I'm able to pdf-compile EmbeddedObjects, but HTML > compilation has problems; This is not surprising. As I said in another message, Embedded Objects uses some advanced features that aren't well supported by LyXHTML. I've done some work in this, but there's a lot more to be done still. Richard
Re: 404 on manuals on lyx.org
On 12/08/2017 15:52, Tommaso Cucinotta wrote: I gave a try to manual compilation of manuals :-), and here's the experience: -) minors along the way: I was missing texlive-lang-german, french, latin, and texlive-humanities; -) Intro, UserGuide, Tutorial, Development, Math, Customization, Additional, LFUNs compile fine (pdf and html); -) major: I'm able to pdf-compile EmbeddedObjects, but HTML compilation has problems; -) major: MergedManuals compilation complains about not being able to find SpecialParagraphShape.tex or smth like that; that comes from Additional.lyx, but Additional standalone compiles without problems, and the .tex file is there, so why does it fail when embedded within MergedManuals ? forgot: -) minor: converted HTML files include images with export names alike 55_home_tommaso_lyx-trunk-ws_lyx_*, which includes the absolute path I was exporting from -- ideally, we shouldn't include any (mangled) absolute path when exporting (but only (mangled) relative paths), is there a TT/# for this ? Thx, T.
Re: 404 on manuals on lyx.org
On 11/08/2017 16:51, Pavel Sanda wrote: I can prepare web corner for it on www.lyx.org if you decide to do it. There's an autotest exporting manuals in a few formats that used to be troublesome (xhtml and lyx16x) in the past, in development/autotests/export-in.sh I gave a try to manual compilation of manuals :-), and here's the experience: -) minors along the way: I was missing texlive-lang-german, french, latin, and texlive-humanities; -) Intro, UserGuide, Tutorial, Development, Math, Customization, Additional, LFUNs compile fine (pdf and html); -) major: I'm able to pdf-compile EmbeddedObjects, but HTML compilation has problems; -) major: MergedManuals compilation complains about not being able to find SpecialParagraphShape.tex or smth like that; that comes from Additional.lyx, but Additional standalone compiles without problems, and the .tex file is there, so why does it fail when embedded within MergedManuals ? I dropped the result here: https://drive.google.com/drive/folders/0B6A-8XYYe1nYUlg3U2YyQm0xQVU?usp=sharing T.
Re: 404 on manuals on lyx.org
On 08/11/2017 07:03 AM, Pavel Sanda wrote: > Christian Ridderström wrote: >> I agree HTML pages online would be nice. >> Not sure if our manuals can (in a nice way) just be exported as HTML though. > Last time I tried (around 2009 and "merged manuals" idea) it did not came out > nicely. > IIRC I reported the issues, Richard might have fixed them since then... Some of the issues got fixed, but I haven't thad a lot of time to work on that in the last few years. Still, it would be some motivation. I think many of the manuals export fine. The Embedded Objects one, perhaps, not so well, but that uses a lot of more complex machinery. Richard
Re: 404 on manuals on lyx.org
On 2017-08-11, Christian Ridderström wrote: > On 11 August 2017 at 13:03, Pavel Sanda wrote: >> Christian Ridderström wrote: >> > [*] It might make sense to have a CI job that builds PDFs etc from the >> > manuals as a separate test. This is already done by Kornel's export test suite. All manuals are regularely exported and failures mailed to the list. There are known failures in additional tests for various "exotic" export routes and configurations but AFAIK all documentation exports fine using the set standard export format (mostly PDF(pdflatex)). >> The problem is you need to check them visually as well. Günter
Re: 404 on manuals on lyx.org
Le 11/08/2017 à 15:55, Christian Ridderström a écrit : In theory the procedure above could work on PDFs (or perhaps PS?), or possible PDFs converted to RTF or something else that's text based duh, perhaps HTML :-) What about using the command 'strings' (maybe with an appropriate option)? -- Jean-Pierre
Re: 404 on manuals on lyx.org
Tommaso Cucinotta wrote: > from my viewpoint, it would be good to have the manuals just available and > searchable on-line, i.e., when I'm looking for something on a search That was exactly the idea behind merged manuals. Fortunately some italian guy implemented advanced search through all manuals meanwhile :) > Albeit, someone pointed out previously that we purposely stop bots to avoid I don't think this would be any problem, because those pages would be static. Bots are problem with Trac, because each query launches costly backend. So it really boils down that someone (you?) is willing to sit down and write the script I envisioned. I can prepare web corner for it on www.lyx.org if you decide to do it. Pavel
Re: 404 on manuals on lyx.org
On 11/08/2017 15:55, Christian Ridderström wrote: simply to ensure that LyX doesn't fail when reading and exporting the manuals as PDFs. from my viewpoint, it would be good to have the manuals just available and searchable on-line, i.e., when I'm looking for something on a search engine, being redirected to either related topics throughout the manuals, or to related discussions throughout our mailing list archives, or related pages on the LyX wiki, would all be good things to have. Albeit, someone pointed out previously that we purposely stop bots to avoid our web server to be overloaded, which is understandable but not nice for visibility of LyX. Thanks, T.
Re: 404 on manuals on lyx.org
On 11 August 2017 at 13:03, Pavel Sanda wrote: > Christian Ridderström wrote: > > I agree HTML pages online would be nice. > > Not sure if our manuals can (in a nice way) just be exported as HTML > though. > > Last time I tried (around 2009 and "merged manuals" idea) it did not came > out nicely. > IIRC I reported the issues, Richard might have fixed them since then... > > > [*] It might make sense to have a CI job that builds PDFs etc from the > > manuals as a separate test. > > The problem is you need to check them visually as well. > I agree that checking the generated PDFs is the difficult part. However, in my mind the test's purpose is simply to ensure that LyX doesn't fail when reading and exporting the manuals as PDFs. This could catch introduced errors in HEAD, or if you let the TeX installation update itself, breakage due to that. > I guess once fixed we could just add one makefile rule to > 1. create all major manuals into pdf & html from tarball > 2. copy it to svn web tree, svn add new html figs > 3. commit it > > It just needs someone to sit and spend couple hours on it... I don't think the server autodeploys from SVN these days, but I could be wrong. Anyway, I didn't intend for such a CI job to also automatically publish the manuals/PDFs. IMHO, before publishing a new set of manuals some kind of manual review is necessary. /Christian [*] I have previously done some stuff that might be relevant/useful. E.g. in one project we got a large log file from a build that might somewhere contain a new error or warning message. Or perhaps one of thousands of values in the log output had changed although it shouldn't. Filtering for 'errror' and 'warning' is of course one way to go. Instead I introduced this approach: 1. Before one release, let two developers manually review the log file 2. Commit the reviewed log file as reference baseline (after fixing some things) 3. After each new build, automatically diff the generated log to the baseline. The diff, if any, had to be manually reviewed and if the changes were intentional and as expected we converted the newly generated log into a new reference for future builds. This worked well IMHO and it did help us catch some subtle bugs. However, the build situation was very different compared to that of LyX. I also introduced this approach for other "outputs", like big automatically generated data tables that were based on the source. Before 'diff:ing' we sometimes had to convert to another format, but it worked pretty well. In theory the procedure above could work on PDFs (or perhaps PS?), or possible PDFs converted to RTF or something else that's text based duh, perhaps HTML :-) It's a totally different question if the effort needed to setup the above is worth it though, which is why I thought of a simpler test that fails if LyX fails to export a PDF.
Re: 404 on manuals on lyx.org
Christian Ridderström wrote: > I agree HTML pages online would be nice. > Not sure if our manuals can (in a nice way) just be exported as HTML though. Last time I tried (around 2009 and "merged manuals" idea) it did not came out nicely. IIRC I reported the issues, Richard might have fixed them since then... > [*] It might make sense to have a CI job that builds PDFs etc from the > manuals as a separate test. The problem is you need to check them visually as well. I guess once fixed we could just add one makefile rule to 1. create all major manuals into pdf & html from tarball 2. copy it to svn web tree, svn add new html figs 3. commit it It just needs someone to sit and spend couple hours on it... Pavel
Re: 404 on manuals on lyx.org
On 11 August 2017 at 08:35, Christian Ridderström wrote: > On 8 August 2017 at 18:28, Tommaso Cucinotta wrote: > >> I just noticed these broken links >> >> http://wiki.lyx.org/LyX/Manuals#download >> http://ftp.lyx.de/Documentation/en/Customization.lyx >> http://ftp.lyx.de/Documentation/en/Customization.pdf >> >> guess they're all broken. >> > > I can't do an anonymous login to ftp://ftp.lyx.de. > I can do an anonymous login to http://ftp.lyx.de. > I am _not_ able to see the subfolder /Documentation/, so it's gone, moved > or permissions changed. > > IIRC, Uwe is related to this. CC:ing him. (to his @lyx.org-account, which > could be wrong) > > With our release frequency, it shouldn't be a problem to manually [*] > update PDFs and upload the official manuals. > > Scott, are the manuals and their updating perhaps related to your notes on > release procedure? > Scott wrote: > I don't currently have any notes on this, but it's possible this was > written somewhere and I missed it. Please let me know the exact steps > that I should take if I should handle it, and I will add those to my > notes. I think I remember more now and I think Uwe does it. I've now CCed his web.de-address thanks to Jean-Pierre. /Christian > > As the problem seems to be the access, perhaps what's needed is a CI job > that monitors that the FTP is working? > > There's also a seemingly outdated (from y 2009) merged manual available at: >> >> http://wiki.lyx.org/LyX/Documentation#toc2 >> https://wiki.lyx.org/uploads//LyX/Manuals/1.4.2/merged_manua >> ls/merged_manuals-1.4.2.pdf >> >> However, besides fixing the links, considering the powerful conversion >> capabilities of LyX, I'd propose to keep at least some manuals accessible >> as HTML pages on the web, rather than, or in addition to, .lyx/.pdf >> downloads. >> > > I agree HTML pages online would be nice. > Not sure if our manuals can (in a nice way) just be exported as HTML > though. > > /Christian > > [*] It might make sense to have a CI job that builds PDFs etc from the > manuals as a separate test. > >
Re: 404 on manuals on lyx.org
On Fri, Aug 11, 2017 at 08:35:04AM +0200, Christian Ridderström wrote: > Scott, are the manuals and their updating perhaps related to your notes on > release procedure? I don't currently have any notes on this, but it's possible this was written somewhere and I missed it. Please let me know the exact steps that I should take if I should handle it, and I will add those to my notes. Scott signature.asc Description: PGP signature
Re: 404 on manuals on lyx.org
Le 11/08/2017 à 08:35, Christian Ridderström a écrit : IIRC, Uwe is related to this. CC:ing him. (to his @lyx.org-account, which could be wrong) No it's right, but he prefers to get mails on his personal address uwesto...@web.de -- Jean-Pierre
Re: 404 on manuals on lyx.org
On 8 August 2017 at 18:28, Tommaso Cucinotta wrote: > I just noticed these broken links > > http://wiki.lyx.org/LyX/Manuals#download > http://ftp.lyx.de/Documentation/en/Customization.lyx > http://ftp.lyx.de/Documentation/en/Customization.pdf > > guess they're all broken. > I can't do an anonymous login to ftp://ftp.lyx.de. I can do an anonymous login to http://ftp.lyx.de. I am _not_ able to see the subfolder /Documentation/, so it's gone, moved or permissions changed. IIRC, Uwe is related to this. CC:ing him. (to his @lyx.org-account, which could be wrong) With our release frequency, it shouldn't be a problem to manually [*] update PDFs and upload the official manuals. Scott, are the manuals and their updating perhaps related to your notes on release procedure? As the problem seems to be the access, perhaps what's needed is a CI job that monitors that the FTP is working? There's also a seemingly outdated (from y 2009) merged manual available at: > > http://wiki.lyx.org/LyX/Documentation#toc2 > https://wiki.lyx.org/uploads//LyX/Manuals/1.4.2/merged_manua > ls/merged_manuals-1.4.2.pdf > > However, besides fixing the links, considering the powerful conversion > capabilities of LyX, I'd propose to keep at least some manuals accessible > as HTML pages on the web, rather than, or in addition to, .lyx/.pdf > downloads. > I agree HTML pages online would be nice. Not sure if our manuals can (in a nice way) just be exported as HTML though. /Christian [*] It might make sense to have a CI job that builds PDFs etc from the manuals as a separate test.
404 on manuals on lyx.org
Hi, I just noticed these broken links http://wiki.lyx.org/LyX/Manuals#download http://ftp.lyx.de/Documentation/en/Customization.lyx http://ftp.lyx.de/Documentation/en/Customization.pdf guess they're all broken. There's also a seemingly outdated (from y 2009) merged manual available at: http://wiki.lyx.org/LyX/Documentation#toc2 https://wiki.lyx.org/uploads//LyX/Manuals/1.4.2/merged_manuals/merged_manuals-1.4.2.pdf However, besides fixing the links, considering the powerful conversion capabilities of LyX, I'd propose to keep at least some manuals accessible as HTML pages on the web, rather than, or in addition to, .lyx/.pdf downloads. Thanks, T.
Re: About LyX web site and wiki site (Was: lyx.org is down again)
On Sun, Nov 27, 2016 at 3:54 AM, Christian Ridderström < christian.ridderst...@gmail.com> wrote: > On 3 November 2016 at 00:46, Joel Kulesza wrote: > >> On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes >> wrote: >>> >>> If you are interested in updating this part of the wiki, we can give you >>> the necessary passwords :) Indeed everything is really out of date. The >>> graphical tour shows proudly LyX 1.3.0pre2! >> >> >> I might be interested... At the risk of raising the ire of >> traditionalists, as part of reworking some of the parts of the site that >> have aged less-than-gracefully, I'd be interested to learn more about the >> infrastructure behind LyX development and distribution to see if moving to >> more-centralized and/or remotely-hosted solutions make sense. >> > > FYI, both the lyx web site and the wiki site are run by the PmWiki wiki > engine. The content of both sites can actually be edited through a browser, > it's simply not as visible for the web site. > This is good information. The wiki would certainly need to be migrated in its current "wiki" form to that, or another, wiki engine to permit continued live editing by any personnel. Given the nature of the websites design (generally static, no elements requiring dynamic interaction / database querying) and the current state of markdown languages, I'd be somewhat inclined to migrate the web presence to inter-linked markdown files. The "README" file would then be the "main page". This will 1. tightly couple the web information/documentation with the rest of the project, 2. migrate the web information to git, 3. allow developer contributions to the web presence with equal level of permission/authentication that they have to the code (direct push, pull request, post patch, etc.). I've already tried reworking the current README to a markdown-compliant format and I think it looks better and is more serviceable (i.e., has links to other appropriate URLs and files). I think this approach is reasonable and reduced the barrier to keeping the website up to date and reliance on few select administrative personnel. It will also tag/track the website along with the various releases à la documentation. If this approach is disagreeable and a more traditional website is preferred, migrating the website to a standalone git repository seems like the preferred approach to me. Because the website is static, the HTML to control it will be rather basic and should require less wiki-customization during any future migration. The only apparent advantage to the current permission-based wiki format is ease of editing --- am I missing something? > Regarding "less-than-graceful" ageing, I'm actually surprised they still > work. And I'm happy people are still editing content on the wiki. I think > I started that work over ten years ago, so my memory is a bit vague on the > details of their configuration... > Indeed, the wiki is a nice resource which I've used and contributed to. As such, I'd like to see it live on. One attractive component to me of the Github/Gitlab services is that they have wiki engines built into projects. Thus, this is something else I'd like to investigate feasibility of migrating: existing wiki to Gitlab wiki (following migration testing for existing Trac to Gitlab issues). However, if I remember correctly, at the time both the wiki and web site > where in SVN. Right now it seems only the web site files have a > .svn/-folder. > > But these days we use git, so I don't even know if there's something > corresponding to the www-user repo in git. > See point above regarding how to migrate the website to git. > At the time it was possible to checkout the web on a different host, or at > a different location, and test it there. So when I did bigger configuration > changes, I deployed and tested locally before putting in production at > lyx.org. > This is my common practice as well. If I'm working directly on a server, I work in a ./stg (staging) subdirectory that is live but unknown (this way I can see how it performs on the actual hardware). Once migration is approved to involved parties, the live site goes to ./bak (backup) and ./stg goes to ./. In this way, the old setup is preserved for some length of time in case there are issues. In this migration, because it would (ideally) be moving to a hosted service, the hosted service site will be built up with content (which is all slowly changing except the codebase itself). Then, when the hosted service is set up and ready for migration, pointers will be made from the current URLs to it with the old site held as "backup" on the server in Bonn. This will allow a revert if there are any issues. > Do you have the login passwords? > I do not. I think there may still be some internal discussion amongst the developer-admins about what, if any, level of access to grant me to the various components of the web infrastructure. > Thanks, Joel
About LyX web site and wiki site (Was: lyx.org is down again)
Hi Joel, On 3 November 2016 at 00:46, Joel Kulesza wrote: > On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes > wrote: >> >> If you are interested in updating this part of the wiki, we can give you >> the necessary passwords :) Indeed everything is really out of date. The >> graphical tour shows proudly LyX 1.3.0pre2! > > > I might be interested... At the risk of raising the ire of > traditionalists, as part of reworking some of the parts of the site that > have aged less-than-gracefully, I'd be interested to learn more about the > infrastructure behind LyX development and distribution to see if moving to > more-centralized and/or remotely-hosted solutions make sense. > FYI, both the lyx web site and the wiki site are run by the PmWiki wiki engine. The content of both sites can actually be edited through a browser, it's simply not as visible for the web site. Regarding "less-than-graceful" ageing, I'm actually surprised they still work. And I'm happy people are still editing content on the wiki. I think I started that work over ten years ago, so my memory is a bit vague on the details of their configuration... However, if I remember correctly, at the time both the wiki and web site where in SVN. Right now it seems only the web site files have a .svn/-folder. At the time it was possible to checkout the web on a different host, or at a different location, and test it there. So when I did bigger configuration changes, I deployed and tested locally before putting in production at lyx.org. But these days we use git, so I don't even know if there's something corresponding to the www-user repo in git. Anyway, updating the content of the wiki and the web site ought to primarily be a matter of using the wiki functionality (for both of them). Do you have the login passwords? Regards, Christian -- Christian Ridderström, +46-70 687 39 44
Re: lyx.org down?
On Sat, Nov 12, 2016 at 06:51:04PM +0100, Jean-Marc Lasgouttes wrote: > Le 12/11/2016 à 14:23, Scott Kostyshak a écrit : > > Hasn't been responding to me for the past 30 minutes or so. > > Seems to work right now? Yes, thanks for checking. Scott signature.asc Description: PGP signature
Re: lyx.org down?
Le 12/11/2016 à 14:23, Scott Kostyshak a écrit : Hasn't been responding to me for the past 30 minutes or so. Seems to work right now? JMarc
lyx.org down?
Hasn't been responding to me for the past 30 minutes or so. Scott signature.asc Description: PGP signature
Re: lyx.org is down again
Joel Kulesza wrote: > http://www.lyx.org/images/about/aqua.png from http://www.lyx.org/Screenshots If you send me how the mac screen looks nowadays, I can upload it. If you would like to rework the walk through we will need to give you access. Pavel
Re: lyx.org is down again
On Wed, Nov 2, 2016 at 7:25 AM, Jean-Marc Lasgouttes wrote: > > If you are interested in updating this part of the wiki, we can give you > the necessary passwords :) Indeed everything is really out of date. The > graphical tour shows proudly LyX 1.3.0pre2! I might be interested... At the risk of raising the ire of traditionalists, as part of reworking some of the parts of the site that have aged less-than-gracefully, I'd be interested to learn more about the infrastructure behind LyX development and distribution to see if moving to more-centralized and/or remotely-hosted solutions make sense. For example, hosting lyx.org from a redirected github.io (or similar) that would hopefully mitigate some of the administrative overhead and improve stability/availability. I wouldn't act without consent/consensus from this list; however, I would like to investigate other options and potentially make a staging site that could be evaluated as a demo of what I have in mind. > But how does the script find the offending IPs? > Parsing log entries to look for certain signatures (sorry for the intentional vagueness).
Re: lyx.org is down again
Le 02/11/2016 à 14:07, Joel Kulesza a écrit : If you're spending time on infrastructure this weekend, perhaps some site updates could be included in your work? http://www.lyx.org/images/about/aqua.png from http://www.lyx.org/Screenshots ;-) If you are interested in updating this part of the wiki, we can give you the necessary passwords :) Indeed everything is really out of date. The graphical tour shows proudly LyX 1.3.0pre2! On a more serious note, with respect to the IPTables work, are unauthorized access attempts an issue that is consuming undue system resources? If so, I have a script I've used before that parses logs for offending IPs and then adds them to a drop rule. But how does the script find the offending IPs? If Richard manages to limit the number of concurrent connections and it proves not to be sufficient, then we will have to resort to other tricks. JMarc
Re: lyx.org is down again
On Tue, Nov 1, 2016 at 7:29 PM, Richard Heck wrote: > > I can probably figure this out, but it will be the weekend before I can > spend the time. Richard, If you're spending time on infrastructure this weekend, perhaps some site updates could be included in your work? http://www.lyx.org/images/about/aqua.png from http://www.lyx.org/Screenshots ;-) On a more serious note, with respect to the IPTables work, are unauthorized access attempts an issue that is consuming undue system resources? If so, I have a script I've used before that parses logs for offending IPs and then adds them to a drop rule. - Joel
Re: lyx.org is down again
On 11/01/2016 05:06 PM, Jean-Marc Lasgouttes wrote: > Le 01/11/16 à 21:51, Richard Heck a écrit : >> What about rate limiting access to the trac/ subdirectory? The problem >> is that we get hit too many times too fast by these bots. Refusing to >> serve them that fast won't make them go away, but it will keep them from >> taking us down. > > Do you know how to do that? I am not sure that trac is the only > problem, BTW. > > And what is the reasonable limit? > > I had some suggestions from Máté: limit the number of connections from > the same IP. IPTables can do this: > > http://unix.stackexchange.com/questions/139285/limit-max-connections-per-ip-address-and-new-connections-per-second-with-iptable > > > Máté suggested a limit of 2 connections per IP. > > I have no idea how to do this properly, though. I can probably figure this out, but it will be the weekend before I can spend the time. Richard
Re: lyx.org is down again
Le 01/11/2016 à 21:06, Jean-Marc Lasgouttes a écrit : I had some suggestions from Máté: limit the number of connections from the same IP. IPTables can do this: http://unix.stackexchange.com/questions/139285/limit-max-connections-per-ip-address-and-new-connections-per-second-with-iptable Máté suggested a limit of 2 connections per IP. I have no idea how to do this properly, though. I have here a /etc/init.d/firewall file that I had set up from an template found somewhere, which begins with: #!/bin/sh ### BEGIN INIT INFO # Provides: custom firewall # Required-Start:$remote_fs $syslog $network # Required-Stop: $remote_fs $syslog $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: firewall initscript # Description: Custom Firewall ### END INIT INFO and then describes the iptables rules. I guess I would add the suggested rules after the HTTP rules: # HTTP iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT # HTTPS iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT iptables -t filter -A INPUT -p tcp --dport 8443 -j ACCEPT The rules are parsed frop top to bottom in this firewall, apparently. -- Jean-Pierre
Re: lyx.org is down again
Le 01/11/16 à 21:51, Richard Heck a écrit : What about rate limiting access to the trac/ subdirectory? The problem is that we get hit too many times too fast by these bots. Refusing to serve them that fast won't make them go away, but it will keep them from taking us down. Do you know how to do that? I am not sure that trac is the only problem, BTW. And what is the reasonable limit? I had some suggestions from Máté: limit the number of connections from the same IP. IPTables can do this: http://unix.stackexchange.com/questions/139285/limit-max-connections-per-ip-address-and-new-connections-per-second-with-iptable Máté suggested a limit of 2 connections per IP. I have no idea how to do this properly, though. JMarc
Re: lyx.org is down again
On 11/01/2016 03:25 PM, Jean-Marc Lasgouttes wrote: > Le 01/11/2016 à 03:52, Joel Kulesza a écrit : >> Does anyone know what the instability is stemming from (hardware, >> software, provider, etc.)? > > I would say that the problem was receiving the visit of > crawl.sogou.com (220.181.125.68), which sucked 700MiB of data (along > with some Amazon aws guy who claimed 320MiB). These are badly behaved > bots which do not respect our robots.txt file. In this file, we > request explicitly to skip indexing the /trac subdirectory. > > I can blacklist by hand these bots, but they are gone now AFAIK and > the harm is done. It seems possible to download automatically some > blacklist of bad crawlers and blacklist them, but I do not know > whether this is a good idea in real life. What about rate limiting access to the trac/ subdirectory? The problem is that we get hit too many times too fast by these bots. Refusing to serve them that fast won't make them go away, but it will keep them from taking us down. Richard
Re: lyx.org is down again
Le 01/11/2016 à 03:52, Joel Kulesza a écrit : Does anyone know what the instability is stemming from (hardware, software, provider, etc.)? I would say that the problem was receiving the visit of crawl.sogou.com (220.181.125.68), which sucked 700MiB of data (along with some Amazon aws guy who claimed 320MiB). These are badly behaved bots which do not respect our robots.txt file. In this file, we request explicitly to skip indexing the /trac subdirectory. I can blacklist by hand these bots, but they are gone now AFAIK and the harm is done. It seems possible to download automatically some blacklist of bad crawlers and blacklist them, but I do not know whether this is a good idea in real life. So we could oversize our server just for the pleasure of letting any stupid bot spend time requesting data. But the best would probably to have a proper webadmin! We do not have anybody doing this job right now. JMarc
Re: lyx.org is down again
I did not have time to look at it yet, but last time it was a rogue Chinese crawler. The solution is probably to blacklist it. JMarc Le 1 novembre 2016 03:52:56 GMT+01:00, Joel Kulesza a écrit : >Does anyone know what the instability is stemming from (hardware, >software, >provider, etc.)? > >On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote: > >> This is now the third down within 2 weeks. >> We should really start to think about switching our provider. >> >> regards Uwe >>
Re: lyx.org is down again
Paul Johnson wrote: > Want more mirrors? Not sure how this helps, if you are normal user and lyx.org does not work how do you figure out to go to freefaculty.org? > The big key is that you give me the nearly bonehead proof command to > run every day. Full mirror is not possible we run quite more services (web,wiki,trac,git,svn) web could be obtained by regular updating svn tree (svn up) if you have on your host php&wiki&subversion. But do not expect bullet proof command, you'll likely spend some time tuning things... Pavel
Re: lyx.org is down again
Want more mirrors? If you would make it "easy" to mirror your server. I could do it on freefaculty.org. How easy? In the R CRAN system, they made this very easy because all I need to do is run an rsync command. No editing at all is needed. We put it in a cron job. So far as I know, there has never been a problem. If you give me an rsync line like that, I could mirror you at some address like http://lyx.freefaculty.org, I'm stuck with "freefaculty.org" because I bought it. We could call it something more neutral, maybe http://mirrors.freefaculty.org/lyx. The big key is that you give me the nearly bonehead proof command to run every day. I never figured out the certificate magic to make https:// possible on the R mirror, but we could try if one of you smart young people helps. This https part is mysterious, but the regular http thing would be, well, no problem. If you tell me the "rsync" command to run. pj On Mon, Oct 31, 2016 at 9:52 PM, Joel Kulesza wrote: > Does anyone know what the instability is stemming from (hardware, software, > provider, etc.)? > > On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote: >> >> This is now the third down within 2 weeks. >> We should really start to think about switching our provider. >> >> regards Uwe > > -- Paul E. Johnson http://pj.freefaculty.org Director, Center for Research Methods and Data Analysis http://crmda.ku.edu To write to me directly, please address me at pauljohn at ku.edu.
Re: lyx.org is down again
Does anyone know what the instability is stemming from (hardware, software, provider, etc.)? On Mon, Oct 31, 2016 at 5:39 AM, Uwe Stöhr wrote: > This is now the third down within 2 weeks. > We should really start to think about switching our provider. > > regards Uwe >
lyx.org is down again
This is now the third down within 2 weeks. We should really start to think about switching our provider. regards Uwe
Re: lyx.org is down again
Am 15.10.2016 um 16:27 schrieb Uwe Stöhr: Am 15.10.2016 um 15:41 schrieb Jean-Marc Lasgouttes: I restarted it, but I am not sure how long it will stand. It is again down and we just released a new version. regards Uwe
Re: lyx.org is down again
Am 15.10.2016 um 15:41 schrieb Jean-Marc Lasgouttes: I restarted it, but I am not sure how long it will stand. thanks regards Uwe
Re: lyx.org is down again
I restarted it, but I am not sure how long it will stand. JMarc
lyx.org is down again
Re: lyx.org down?
On Wed, Oct 05, 2016 at 11:47:31AM -0400, Richard Heck wrote: > On 10/05/2016 10:25 AM, Paul A. Rubin wrote: > > On 10/05/2016 10:02 AM, Scott Kostyshak wrote: > >> lyx.org is not responsive for me. This comment also suggests that it's > >> down for someone else: > >> http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712 > >> > >> Scott > > Confirmed here (and also by Down for Everyone Or Just Me > > <http://www.isup.me/>). > > One of those things, yet again. Seems to work now here. Works here now also. Scott signature.asc Description: PGP signature
Re: lyx.org down?
On 10/05/2016 10:25 AM, Paul A. Rubin wrote: > On 10/05/2016 10:02 AM, Scott Kostyshak wrote: >> lyx.org is not responsive for me. This comment also suggests that it's >> down for someone else: >> http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712 >> >> Scott > Confirmed here (and also by Down for Everyone Or Just Me > <http://www.isup.me/>). One of those things, yet again. Seems to work now here. Richard
Re: lyx.org down?
On 10/05/2016 10:02 AM, Scott Kostyshak wrote: lyx.org is not responsive for me. This comment also suggests that it's down for someone else: http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712 Scott Confirmed here (and also by Down for Everyone Or Just Me <http://www.isup.me/>). Paul
lyx.org down?
lyx.org is not responsive for me. This comment also suggests that it's down for someone else: http://tex.stackexchange.com/questions/332712/getting-text-to-wrap-in-lyx-table-cells#comment815461_332712 Scott signature.asc Description: PGP signature
Re: Win Vista announcement for lyx.org
Uwe Stöhr wrote: > post is subjective and thus not fair. We should not propose an OS for the > users! People are free to use what they like. If they prefer PC-BSD, MacOS I kicked any OS related suggestions out. Pavel
Re: Win Vista announcement for lyx.org
Am 09.06.2016 um 20:15 schrieb Richard Heck: That seems like a good and clear message. OK, could you please put it then on lyx.org? Or should I do this If so how is this done? I don't have access. Pavel took care of the news items related to the release. Needs SVN access to change the RSS code, from what I understand. I can take care of it. Richard, many thanks for putting it on lyx.org. BUT this is now what I wrote. Your post is subjective and thus not fair. We should not propose an OS for the users! People are free to use what they like. If they prefer PC-BSD, MacOS or Windows 10 - it is their choice. And you also now that in the vast majority of companies around the world Windows is used and that employees cannot choose an OS. Therefore please change the news message. This was my proposed message: --- End of support for Windows Vista The Windows binaries for the new LyX versions 2.2.x will not run under Windows Vista. The reason is that LyX uses the library Qt 5.6 for the user interface which does no longer support Windows Vista. By using LyX 2.1.5 (that will be released this week) it is nevertheless possible to collaborate on Vista with persons using LyX 2.2.x. LyX 2.1.5 runs on Vista and is able to read LyX files created/saved with LyX 2.2.x. Since Microsoft's support with security fixes for Vista ends in April 2017 an update to another Windows version or another OS should be considered. --- This is in my opinion more clear because most users never heard of Qt and don't know what this is. In your post I find Qt a bit hard to understand. sorry for nagging, thanks and regards Uwe p.s. (I also don't think that even if you prefer Linux, we should propose a special distribution like Ubuntu.)
Re: lyx.org down?
This tends to happened when some robot is crawling, I think. We should take a serious look at the http log at these times if we want to understand what is going on. JMarc Le 12 décembre 2015 08:25:12 GMT+01:00, Georg Baum a écrit : >Richard Heck wrote: > >> I restarted httpd. Not sure why it was slow this time. > >It is slow again:-( > >Georg
Re: lyx.org down?
Richard Heck wrote: > I restarted httpd. Not sure why it was slow this time. It is slow again:-( Georg
Re: lyx.org down?
On 12/11/2015 06:56 PM, Scott Kostyshak wrote: > On Fri, Dec 11, 2015 at 06:54:43PM -0500, Scott Kostyshak wrote: >> It was working fine 5 minutes ago but it has not been working the last 5 >> minutes for me. I normally wait a few hours before sending this email, >> but I've learned that it's good to send it early in case someone sees it >> before signing off for the night. > Nevermind. Working fine now. I restarted httpd. Not sure why it was slow this time. rh
Re: lyx.org down?
On Fri, Dec 11, 2015 at 06:54:43PM -0500, Scott Kostyshak wrote: > It was working fine 5 minutes ago but it has not been working the last 5 > minutes for me. I normally wait a few hours before sending this email, > but I've learned that it's good to send it early in case someone sees it > before signing off for the night. Nevermind. Working fine now. Scott signature.asc Description: PGP signature
lyx.org down?
It was working fine 5 minutes ago but it has not been working the last 5 minutes for me. I normally wait a few hours before sending this email, but I've learned that it's good to send it early in case someone sees it before signing off for the night. Scott signature.asc Description: PGP signature
Re: #9873: lyx.org does not support https
On 12/06/2015 06:41 AM, Georg Baum wrote: > Christian Ridderström wrote: > >> Note: The LE client needs root access, e.g. to stop/start apache, and to >> do other stuff in order to prove to the LE servers that we (i.e. the >> server) really are the one controlling www.lyx.org and wiki.lyx.org. The >> cron job then also needs root/sudo in order to update the client. > Giving root access to the LE client is IMHO a no-go. It means you need to > trust a relatively new piece of code which is controlled from outside (even > worse). See also this (german) blog entry: http://blog.fefe.de/?ts=a89f4ed6 > > It is a rant, but as usual for Fefe it contains some substantial reasoning > as well. > > If Letsencrypt does not allow to download the certificate manually, so that > it can be installed manually in a trusted environment, some other > certificate provider should be used IMHO. This does seem to be possible, but needs some investigation. See https://community.letsencrypt.org/t/i-just-want-a-certificate/5331/10 for some of the relevant details. I intend to play around with this, as I said in a different email, on my own server. If I get it working there, I can do it also on lyx.org, with documentation about how it works. The one downside will be the need to update the certificate manually every three months. Richard
Re: #9873: lyx.org does not support https
Christian Ridderström wrote: > Note: The LE client needs root access, e.g. to stop/start apache, and to > do other stuff in order to prove to the LE servers that we (i.e. the > server) really are the one controlling www.lyx.org and wiki.lyx.org. The > cron job then also needs root/sudo in order to update the client. Giving root access to the LE client is IMHO a no-go. It means you need to trust a relatively new piece of code which is controlled from outside (even worse). See also this (german) blog entry: http://blog.fefe.de/?ts=a89f4ed6 It is a rant, but as usual for Fefe it contains some substantial reasoning as well. If Letsencrypt does not allow to download the certificate manually, so that it can be installed manually in a trusted environment, some other certificate provider should be used IMHO. Georg
Re: #9873: lyx.org does not support https
On 12/05/2015 05:44 PM, Christian Ridderström wrote: > I'm for enabling HTTPS, and have actually thought it's something we > ought to have... > So I took a look at letsencrypt tonight. It seems doable, but I'm a > little concerned it'll take more work than its worth. > Roughly: > - Ensure dependencies are met (this is probably not so bad) > - Install the Letsencrypt (LE) client > - Make LE work and get a certificate > Involves setting up a private key, and I think submitting some > e-mail address > to letsencrypt. Not sure what address that should be - is there e.g. > an ad...@lyx.org <mailto:ad...@lyx.org>? > - Make some cron job or similar renew the certificate every 90 days > - Adjust links on wiki and web pages to support working over HTTPS > (maybe links have HTTP hardcoded for instance) > > Note: The LE client needs root access, e.g. to stop/start apache, and > to do other stuff in order to prove to the LE servers that we (i.e. > the server) really are the one controlling www.lyx.org > <http://www.lyx.org> and wiki.lyx.org <http://wiki.lyx.org>. The cron > job then also needs root/sudo in order to update the client. I've been looking at this, too. I'm thinking that, once classes are over and I have a bit of time, I'll try installing an LE certificate on one of my own servers, and see how that goes. Once I have some experience with that, we can perhaps revisit this issue. Richard
Re: #9873: lyx.org does not support https
I'm for enabling HTTPS, and have actually thought it's something we ought to have... So I took a look at letsencrypt tonight. It seems doable, but I'm a little concerned it'll take more work than its worth. Roughly: - Ensure dependencies are met (this is probably not so bad) - Install the Letsencrypt (LE) client - Make LE work and get a certificate Involves setting up a private key, and I think submitting some e-mail address to letsencrypt. Not sure what address that should be - is there e.g. an ad...@lyx.org? - Make some cron job or similar renew the certificate every 90 days - Adjust links on wiki and web pages to support working over HTTPS (maybe links have HTTP hardcoded for instance) Note: The LE client needs root access, e.g. to stop/start apache, and to do other stuff in order to prove to the LE servers that we (i.e. the server) really are the one controlling www.lyx.org and wiki.lyx.org. The cron job then also needs root/sudo in order to update the client. Regards, Christian On 2 December 2015 at 06:27, LyX Ticket Tracker wrote: > #9873: lyx.org does not support https > ---+ > Reporter: uwestoehr | Owner: chr > Type: defect | Status: new > Priority: normal | Milestone: > Component: website| Version: 2.1.4 > Severity: normal | Resolution: > Keywords: | > ---+ > > Comment (by skostysh): > > Seems that now might be a good time to look into it: > > https://letsencrypt.org/2015/11/12/public-beta-timing.html?v=2 > > -- > Ticket URL: <http://www.lyx.org/trac/ticket/9873#comment:7> > The LyX Project <http://www.lyx.org/> > LyX -- The Document Processor > -- Christian Ridderström, +46-70 687 39 44
Re: lyx.org down for me
Le 18/10/15 15:31, Georg Baum a écrit : Jean-Marc Lasgouttes wrote: I just sent a message to netad...@stw-bonn.de Seems to have worked ;-) Yes, these guys are quite responsive. JMarc
Re: lyx.org down for me
Jean-Marc Lasgouttes wrote: > I just sent a message to netad...@stw-bonn.de Seems to have worked ;-) Georg
Re: lyx.org down for me
Le 18/10/15 01:29, Richard Heck a écrit : Not sure where to go from there :( I am not sure that we have a live contact with people of stw-bonn.de who host us. Lars set that up, didn't he? I just sent a message to netad...@stw-bonn.de JMarc
