Forum: itex2MML – Topic: Bugs

From what I’ve seen, many of these issues come from the differences between how LaTeX interprets expressions and how MathML parsers implement them. Even when the generated MathML is technically valid, browser rendering can still produce inconsistent results depending on the engine.

Wrapping expressions explicitly or adding grouping often seems to be the safest workaround when parser precedence is ambiguous. It’s not always ideal, but it does make the output more predictable across different environments.

If anyone is looking for additional resources or related web tools, you can find more information here.

Forum: Instiki – Topic: bundling error Linux Mint 22.3

This worked, thank you. It was not clear for me which yaml package was needed

Forum: Instiki – Topic: bundling error Linux Mint 22.3

Maybe

sudo apt install libyaml-dev

?

Forum: Instiki – Topic: bundling error Linux Mint 22.3

I’m trying to install Instiki 0.40.0 on Linux Mint 22.3 (based on Ubuntu 24.04). This is the farthest I got. In case the cause of the error can be easily spotted by anyone better versed than me, I’d welcome any help. Thank you!

xabier@atenea:~/instiki-0.40.4$bundle config set --local path 'vendor/bundle' xabier@atenea:~/instiki-0.40.4$ bundle install Bundler 2.4.20 is running, but your lockfile was generated with 4.0.11. Installing Bundler 4.0.11 and restarting using that version. Fetching gem metadata from https://rubygems.org/. Fetching bundler 4.0.11 Installing bundler 4.0.11 Fetching https://github.com/distler/maruku.git Fetching gem metadata from https://rubygems.org/……… Fetching rake 13.4.2 Installing rake 13.4.2 Fetching RedCloth 4.3.4 Fetching bigdecimal 4.1.2 Fetching connection_pool 3.0.2 Fetching json 2.19.5 Fetching prism 1.9.0 Fetching activesupport 8.1.3 Fetching drb 2.2.3 Fetching logger 1.7.0 Fetching minitest 6.0.6 Fetching rails-dom-testing 2.3.0 Fetching securerandom 0.4.1 Fetching erubi 1.13.1 Fetching racc 1.8.1 Fetching nokogiri 1.19.3 (x86_64-linux-gnu) Fetching base64 0.3.0 Fetching concurrent-ruby 1.3.6 Fetching i18n 1.14.8 Fetching tzinfo 2.0.6 Fetching uri 1.1.1 Fetching builder 3.3.0 Fetching crass 1.0.6 Installing RedCloth 4.3.4 with native extensions Installing bigdecimal 4.1.2 with native extensions Fetching loofah 2.25.1 Installing json 2.19.5 with native extensions Fetching rails-html-sanitizer 1.7.0 Fetching actionview 8.1.3 Fetching rack 3.2.6 Fetching rack-session 2.1.2 Installing prism 1.9.0 with native extensions Fetching rack-test 2.2.0 Fetching useragent 0.16.11 Fetching actionpack 8.1.3 Fetching prettyprint 0.2.0 Installing racc 1.8.1 with native extensions Fetching pp 0.6.3 Fetching erb 6.0.4 Fetching date 3.5.1 Fetching stringio 3.2.0 Fetching psych 5.3.1 Fetching tsort 0.2.0 Fetching rdoc 7.2.0 Fetching io-console 0.8.2 Fetching reline 0.6.3 Fetching irb 1.18.0 Fetching rackup 2.3.1 Fetching thor 1.5.0 Fetching zeitwerk 2.7.5 Fetching railties 8.1.3 Fetching action_text-trix 2.1.19 Fetching nio4r 2.7.5 Fetching websocket-extensions 0.1.5 Fetching websocket-driver 0.8.0 Fetching actioncable 8.1.3 Installing erb 6.0.4 with native extensions Installing date 3.5.1 with native extensions Installing stringio 3.2.0 with native extensions Fetching globalid 1.3.0 Fetching activejob 8.1.3 Fetching activemodel 8.1.3 Installing io-console 0.8.2 with native extensions Fetching timeout 0.6.1 Fetching activerecord 8.1.3 Fetching marcel 1.1.0 Fetching activestorage 8.1.3 Fetching mini_mime 1.1.5 Fetching net-protocol 0.2.2 Fetching net-imap 0.6.4 Fetching net-pop 0.1.2 Fetching net-smtp 0.5.1 Installing nio4r 2.7.5 with native extensions Fetching mail 2.9.0 Fetching actionmailbox 8.1.3 Fetching actionmailer 8.1.3 Fetching actionpack-action_caching 1.2.2 Fetching actionpack-page_caching 1.2.4 Fetching actiontext 8.1.3 Fetching csv 3.3.5 Fetching daemons 1.4.1 Fetching eventmachine 1.2.7 Fetching file_signature 1.2.0 Fetching multi_xml 0.9.1 Fetching httparty 0.24.2 Fetching iconv 1.1.1 Fetching itextomml 1.6.2 Fetching syntax 1.1.0 Fetching power_assert 3.0.1 Fetching pstore 0.2.1 Fetching rails 8.1.3 Fetching rails-controller-testing 1.0.5 Fetching rails-observers 0.1.5 Fetching rexml 3.4.4 Fetching rubyzip 2.3.2 Fetching sqlite3 2.9.4 (x86_64-linux-gnu) Fetching strscan 3.1.8 Fetching test-unit 3.7.7 Installing eventmachine 1.2.7 with native extensions Fetching thin 2.0.1 Fetching webrick 1.9.2 Fetching zip-zip 0.3 Installing connection_pool 3.0.2 Installing iconv 1.1.1 with native extensions Installing activesupport 8.1.3 Installing itextomml 1.6.2 with native extensions Installing rails-dom-testing 2.3.0 Installing drb 2.2.3 Installing logger 1.7.0 Installing minitest 6.0.6 Installing securerandom 0.4.1 Installing erubi 1.13.1 Installing base64 0.3.0 Installing nokogiri 1.19.3 (x86_64-linux-gnu) Installing concurrent-ruby 1.3.6 Installing i18n 1.14.8 Installing uri 1.1.1 Installing tzinfo 2.0.6 Installing builder 3.3.0 Installing crass 1.0.6 Installing loofah 2.25.1 Installing rails-html-sanitizer 1.7.0 Installing actionview 8.1.3 Installing rack 3.2.6 Installing rack-session 2.1.2 Installing rack-test 2.2.0 Installing useragent 0.16.11 Installing actionpack 8.1.3 Installing prettyprint 0.2.0 Installing pp 0.6.3 Installing tsort 0.2.0 Installing rdoc 7.2.0 Installing reline 0.6.3 Installing irb 1.18.0 Installing rackup 2.3.1 Installing thor 1.5.0 Installing zeitwerk 2.7.5 Installing railties 8.1.3 Installing action_text-trix 2.1.19 Installing websocket-extensions 0.1.5 Installing actioncable 8.1.3 Installing globalid 1.3.0 Installing activejob 8.1.3 Installing activemodel 8.1.3 Installing timeout 0.6.1 Installing activerecord 8.1.3 Installing marcel 1.1.0 Installing activestorage 8.1.3 Installing mini_mime 1.1.5 Installing net-protocol 0.2.2 Installing net-imap 0.6.4 Installing net-pop 0.1.2 Installing net-smtp 0.5.1 Installing mail 2.9.0 Installing actionmailbox 8.1.3 Installing actionmailer 8.1.3 Installing actionpack-action_caching 1.2.2 Installing actionpack-page_caching 1.2.4 Installing actiontext 8.1.3 Installing csv 3.3.5 Installing daemons 1.4.1 Installing file_signature 1.2.0 Installing multi_xml 0.9.1 Installing httparty 0.24.2 Installing syntax 1.1.0 Installing power_assert 3.0.1 Installing pstore 0.2.1 Installing rails 8.1.3 Installing rails-controller-testing 1.0.5 Installing rails-observers 0.1.5 Installing rexml 3.4.4 Installing rubyzip 2.3.2 Installing websocket-driver 0.8.0 with native extensions Installing strscan 3.1.8 with native extensions Installing sqlite3 2.9.4 (x86_64-linux-gnu) Installing test-unit 3.7.7 Installing webrick 1.9.2 Installing zip-zip 0.3 Installing psych 5.3.1 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory: /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/psych-5.3.1/ext/psych /usr/bin/ruby3.2 -I/usr/lib/ruby/vendor_ruby extconf.rb checking for yaml.h… no yaml.h not found *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.

Provided configuration options:

--with-opt-dir

--without-opt-dir

--with-opt-include

--without-opt-include=${opt-dir}/include

--with-opt-lib

--without-opt-lib=${opt-dir}/lib

--with-make-prog

--without-make-prog

--srcdir=.

--curdir

--ruby=/usr/bin/$(RUBY_BASE_NAME)3.2

--with-libyaml-source-dir

--without-libyaml-source-dir

--with-yaml-0.1-dir

--without-yaml-0.1-dir

--with-yaml-0.1-include

--without-yaml-0.1-include=${yaml-0.1-dir}/include

--with-yaml-0.1-lib

--without-yaml-0.1-lib=${yaml-0.1-dir}/lib

--with-yaml-0.1-config

--without-yaml-0.1-config

--with-pkg-config

--without-pkg-config

--with-libyaml-dir

--without-libyaml-dir

--with-libyaml-include

--without-libyaml-include=${libyaml-dir}/include

--with-libyaml-lib

--without-libyaml-lib=${libyaml-dir}/lib

To see why this extension failed to compile, please check the mkmf.log which can be found here:

/home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux-gnu/3.2.0/psych-5.3.1/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/psych-5.3.1 for inspection. Results logged to /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux-gnu/3.2.0/psych-5.3.1/gem_make.out

/usr/lib/ruby/vendor_ruby/rubygems/ext/builder.rb:119:in run' /usr/lib/ruby/vendor_ruby/rubygems/ext/ext_conf_builder.rb:28:in build’ /usr/lib/ruby/vendor_ruby/rubygems/ext/builder.rb:187:in build_extension' /usr/lib/ruby/vendor_ruby/rubygems/ext/builder.rb:221:in block in build_extensions’ /usr/lib/ruby/vendor_ruby/rubygems/ext/builder.rb:218:in each' /usr/lib/ruby/vendor_ruby/rubygems/ext/builder.rb:218:in build_extensions’ /usr/lib/ruby/vendor_ruby/rubygems/installer.rb:844:in build_extensions' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/rubygems_gem_installer.rb:112:in build_extensions’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/rubygems_gem_installer.rb:30:in install' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/source/rubygems.rb:211:in block in install’ /usr/lib/ruby/vendor_ruby/rubygems.rb:962:in time' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/source/rubygems.rb:210:in install’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/installer/gem_installer.rb:68:in install' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/installer/gem_installer.rb:17:in install_from_spec’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/installer/parallel_installer.rb:164:in do_install' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/installer/parallel_installer.rb:134:in block in worker_pool’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/worker.rb:70:in apply_func' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/worker.rb:65:in block in process_queue’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/worker.rb:56:in loop' /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/worker.rb:56:in process_queue’ /home/xabier/instiki-0.40.4/vendor/bundle/ruby/3.2.0/gems/bundler-4.0.11/lib/bundler/worker.rb:98:in `block (2 levels) in create_threads'

An error occurred while installing psych (5.3.1), and Bundler cannot continue.

In Gemfile: rails was resolved to 8.1.3, which depends on actiontext was resolved to 8.1.3, which depends on action_text-trix was resolved to 2.1.19, which depends on railties was resolved to 8.1.3, which depends on irb was resolved to 1.18.0, which depends on rdoc was resolved to 7.2.0, which depends on psych

Forum: Heterotic Beast – Topic: New version of Heterotic Beast

Heterotic Beast (the forum software that runs this forum) has been updated from Rails 3.2 to Rails 8.1. Many bugs were squashed along the way.

As a part of the upgrade, we switched authentication mechanisms. As a consequence, all users will have to reset their passwords, by clicking on the link on the login page.

Sorry ‘bout that.

Forum: Heterotic Beast – Topic: A Test

This is just a test of our patch.

Forum: Instiki – Topic: Debian installation

Indeed it worked. Thank you!

Forum: Instiki – Topic: Debian installation

I think there’s an issue with Rack 3.0. See if this change to your Gemfile helps

--- a/Gemfile
+++ b/Gemfile
@@ -1,7 +1,7 @@
 source "https://rubygems.org"
 gem "sqlite3", "1.4.2"
 gem "itextomml", ">=1.6.0"
-gem "rack", ">=2.0"
+gem "rack", "~>2.0"
 gem "thin"
 gem "after_commit"
 gem "rubyzip", '~>2.3.0'

Forum: Instiki – Topic: Debian installation

Here we are again… I have just installed Instiki on a machine running Linux Mint Debian Edition 5. Bundling seems OK but when I try to run the program I get this:

Traceback (most recent call last):

6: from ./instiki:6:in `<main>'

5: from ./instiki:6:in `load'

4: from /home/xabier/instiki-0.30.3/script/server:56:in `<top (required)>'

3: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'

2: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in `new_constants_in'

1: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `block in require'

/home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require': cannot load such file -- rack/handler (LoadError)

7: from ./instiki:6:in `<main>'

6: from ./instiki:6:in `load'

5: from /home/xabier/instiki-0.30.3/script/server:55:in `<top (required)>'

4: from /home/xabier/instiki-0.30.3/script/server:58:in `rescue in <top (required)>'

3: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require'

2: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in `new_constants_in'

1: from /home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `block in require'

/home/xabier/instiki-0.30.3/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in `require': cannot load such file -- rack/handler (LoadError)

Any help in making some sense of this output? Thanks!

Forum: Instiki – Topic: noob backup question

If you’re using the (default) sqlite3 database, that’s a plain file in the db/ directory. Just copy it over to the new installation. If you’ve uploaded files to your wiki, they’re in the webs/ directory. Again, just copy them over to the new installation.

Forum: Instiki – Topic: noob backup question

How do I back up and restore a wiki to a new computer? Looking though the instiki site I could not find this …

This may be obvious but I can’t understand how to do it … (I’m an embedded engineer, I can barely spell HTML much less use it)

thx

Forum: Instiki – Topic: Instiki 0.30.3

While there are a few new features, this is primarily a security release, to deal with an issue uncovered by Christian Sattler.

You will need to do a

ruby bundle install

to update some of the dependencies.

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

Just a tip: you don’t really need to wrap your SVG in a MathML equation. If all you need is to center the figure,

+--{: style='margin: auto; text-align: center'}
<svg> ...</svg>
=--

will suffice (and won’t generate the superfluous MathML wrapper).

(Even better, edit the CSS tweaks for your Web, to add a .centered class:

.centered {margin: auto; text-align: center}

Then this could be abbreviated to

+--{.centered}
<svg> ...</svg>
=--

)

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

Ohh. That was a stupid miss on my part. I never thought to look at ids! I changed them and it all works fine now. Thanks a lot

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

Just so we’re clear, Instiki takes care to uniquify the #ids of the SVG fragments generated from Tikz source. If you want to generate the SVG yourself, then that responsibility falls on you.

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

Sorry. I guess I misunderstood what you are doing. Instiki allows the inclusion of Tikz source (either inline or via [!include ...]). But that’s not what you are doing.

You’ve created two SVG fragments by some means or other. It doesn’t matter whether you put them inline or via [!include...]. The source of your trouble is that #ids need to be unique on a page, and your two SVG fragments have duplicate #ids. Individually, they work fine; but put them on the same page and all hell breaks loose.

Fix your #ids and you’ll fix your display problems.

This again, has nothing to do with Instiki, its support for Tikz or for SVG. It’s basic X(HT)ML.

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

Please find here the link to the page. And the link to the two individual figures: fig1, fig2

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

I have pages with multiple Tikz-generated images. So I don’t know what your problem is. Perhaps if you porvided a link …

Forum: Instiki – Topic: Page with multiple SVGs doesn't render properly

I have a page which includes two SVG images that were generated by tikz and then converted to SVG online. Both of them render perfectly if they are the only images on the page. But when both of them are included, the second image does not render correctly at all. All the math in the image is wrong and includes weird symbols. Is there a fix for this?

Forum: Instiki – Topic: tex2svg on Heroku

Thanks a lot! This works for now. I will ask in Heroku forums in case the timeouts grow inconvenient.

Forum: Instiki – Topic: tex2svg on Heroku

If you’re using the “free” level of service at Heroku, then timeouts can be a problem. It takes a while for Heroku to spin up a Dyno. Just try editing the page again. Once tex2svg is up and running, it should respond very quickly.

As to setup, there are many ways to do it. The simplest is simply to have two Heroku apps that talk to each other over http(s). So, e.g., in Instiki’s config/environments/production.rb, you could have

ENV['tikz_server'] = 'https://some-name-for-tex2svg.herokuapp.com'

This configuration can suffer from the timeout issue just mentioned.

Better would be to have them both running in the same Heroku instance. But that’s a Heroku question, not an Instiki question and you’ll get better advice on one of the Heroku forums.

Forum: Instiki – Topic: tex2svg on Heroku

I deployed the tex2svg server on Heroku as per the instruction given here by creating a separate app. What exactly do I now need to put in the config/environments/production.rb file? When I gave the path to the tex2svg Heroku app with port number 9292, it timed out during testing. How do I start the tex2svg server on Heroku? Please guide.

Forum: Instiki – Topic: Heroku hosting fails

It works now! Thanks!

Forum: Instiki – Topic: SVG editor doesn't work

The problem isn’t on the browser end, but rather on the server end. Instiki is misinterpreting your browsers request for that file (which resides under public/svg-edit/editor/jgraduate/css/jGraduate.css) with a request for a wiki page (in a web named svg-edit). That’s not a problem I’m seeing on any of my Instiki installations. So I’m trying to figure out what’s “different” about yours.

Forum: Instiki – Topic: Heroku hosting fails

Hmm. Looking more closely at your error message, I think this commit might fix your problem. Dunno what the source of the extra space is, but that seems to be the cause of Heroku’s complaints.

Forum: Instiki – Topic: Heroku hosting fails

I followed the exact instructions on the site. The Gemfile.lock that I can see on my machine also doesn’t have the “BUNDLED WITH” line. The code seems to be running BUNDLED_WITHOUT :

remote: Running: BUNDLE_WITHOUT=‘development:test’ BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4

But I do not know what BUNDLED_WITH version it is removing in a previous line. None of the files (Gemfile or Gemfile.lock) seem to have either BUNDLED_WITH or the BUNDLED_WITHOUT line. I found a dicussion on stackoverflow but the accepted answer says the same thing the log file says. I did not run bundle install at any point.

Forum: Instiki – Topic: SVG editor doesn't work

No I do not have any wiki (web) of that name. Or even a page. I got the same error when I tried it with different browsers also (with and without any extensions/addons).

Forum: Instiki – Topic: SVG editor doesn't work

Do you have a Web named “svg-edit”?

Forum: Instiki – Topic: Heroku hosting fails

Clearly you are trying to use the wrong Gemfile.lock. The correct one (which you are supposed to rename from Gemfile.lock.heroku) doesn’t have a “BUNDLED WITH” line in it.

Try following these instructions.

Forum: Instiki – Topic: Heroku hosting fails

I tried it again and got this error:

—–> Building on the Heroku-20 stack

—–> Determining which buildpack to use for this app

—–> Ruby app detected

—–> Installing bundler 1.17.3

—–> Removing BUNDLED WITH version in the Gemfile.lock

—–> Compiling Ruby/Rack

—–> Using Ruby version: ruby-2.7.1

—–> Installing dependencies using bundler 1.17.3

   Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 BUNDLE_GLOBAL_PATH_APPENDS_RUBY_SCOPE=1 bundle install -j4

   You are trying to install in deployment mode after changing

   your Gemfile. Run `bundle install` elsewhere and add the

   updated Gemfile.lock to version control.

   

   If this is a development machine, remove the /tmp/build_34292e11/Gemfile freeze 

   by running `bundle install --no-deployment`.

   

   Bundler is unlocking ruby

   

   You have added to the Gemfile:

   * rubyzip (~> 2.3.0)

   

   You have deleted from the Gemfile:

   * rubyzip  (~> 2.3.0)

   Bundler Output: You are trying to install in deployment mode after changing

   your Gemfile. Run `bundle install` elsewhere and add the

   updated Gemfile.lock to version control.

   

   If this is a development machine, remove the /tmp/build_34292e11/Gemfile freeze 

   by running `bundle install --no-deployment`.

   

   Bundler is unlocking ruby

   

   You have added to the Gemfile:

   * rubyzip (~> 2.3.0)

   

   You have deleted from the Gemfile:

   * rubyzip  (~> 2.3.0)

!

! Failed to install gems via Bundler.

!

! Push rejected, failed to compile Ruby app.

! Push failed

I am not sure now if this was a problem from my side.