Coquelicot August 2013

coquelicot@potager.org

2 participants
2 discussions

Installation
by Garreau Alexandre 01 Sep '13

01 Sep '13

Hi, I've some problems with coquelicot installation on my Debian GNU/Linux Wheezy server: root@server-713:/var/www# git clone https://coquelicot.potager.org/coquelicot.git Cloning into 'coquelicot'... root@server-713:/var/www# cd coquelicot root@server-713:/var/www/coquelicot# git tag -v coquelicot-0.9.2 object 069a8c16bb82b9daebd9918b34c582a9b3d346af type commit tag coquelicot-0.9.2 tagger Lunar <lunar(a)anargeek.net> 1365437455 +0200 coquelicot 0.9.2 gpg: Signature made Mon Apr 8 18:10:55 2013 CEST using RSA key ID A8D1112A gpg: Can't check signature: public key not found error: could not verify the tag 'coquelicot-0.9.2' root@server-713:/var/www/coquelicot# git checkout -b production coquelicot-0.9.2 Switched to a new branch 'production' root@server-713:/var/www/coquelicot# less INSTALL root@server-713:/var/www/coquelicot# apt-get install rubygems Reading package lists... Done Building dependency tree Reading state information... Done rubygems is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@server-713:/var/www/coquelicot# less INSTALL root@server-713:/var/www/coquelicot# gem install bundler Successfully installed bundler-1.3.5 1 gem installed Installing ri documentation for bundler-1.3.5... Installing RDoc documentation for bundler-1.3.5... root@server-713:/var/www/coquelicot# bundle install --deployment Fetching gem metadata from https://rubygems.org/......... Fetching gem metadata from https://rubygems.org/.. Installing rake (10.0.3) Installing activesupport (3.0.0) Installing active_support (3.0.0) Installing backports (3.1.0) Installing mime-types (1.17.2) Installing nokogiri (1.5.0) Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/bin/ruby1.9.1 extconf.rb /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- mkmf (LoadError) from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from extconf.rb:5:in `<main>' Gem files will remain installed in /srv/www/coquelicot/vendor/bundle/ruby/1.9.1/gems/nokogiri-1.5.0 for inspection. Results logged to /srv/www/coquelicot/vendor/bundle/ruby/1.9.1/gems/nokogiri-1.5.0/ext/nokogiri/gem_make.out An error occurred while installing nokogiri (1.5.0), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.5.0'` succeeds before bundling. root@server-713:/var/www/coquelicot# What does this error mean? PS : Is this mailing-list english or french?

3 6

</div>: let's make Coquelicot more semantic with HTML5
by Garreau Alexandre 31 Aug '13

31 Aug '13

Hello, I’ve noticed that the HTML code produced by Coquelicot is very nice made (except maybe that the code isn’t wrapped at 72th column so it looks better, like HTML-tidy do), but there’s one thing that could be improved: the HTML version. Although XHTML is very good, I think (X)HTML5 (yes it has an XML-complient version) is better: it’s really more semantic, and more simple on some points. For example, that could take away all these ugly “</div>” which have no sense. The “<div id="header">” would become “<header>”, the “<div id="footer">” would become “<footer>”, the “<code>git clone https://[…]/coquelicot.git</code>” would become more semantic with the “<kbd>” element, the “<em>Coquelicot</em>” that would become *really* semantically correct with “<cite>” element, the sections would be marked more explicitly with the “<section>” elements around and of course the “<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">” would become simpler with “<!DOCTYPE html>”. Notice that today most of web browser support HTML5 (even *IE*, yes *Microsoft Internet Explorer now supports new HTML5 semantic elements*), and are very urged to implement a lot of new HTML5 standards by great evolution of some new great CSS features (which often make the code cleaner) implemented in more popular browsers and the two most used Web layout engines (seems to be the lasts, after the great death of IE and the abandonment of Presto) are WebKit (Safari, Chrome, GNOME, etc.) and Gecko (Firefox, Greasemonkey, Thunderbird, Iceweasel, Icedove, etc.), which are both interoperable and free! Let’s take that opportunity!

3 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Coquelicot August 2013