The Web Open Font Format (short WOFF; here using Aladin font) is several years old. Still it took some time to get to a point, where WOFF is almost painless to use on the linux desktop. WOFF is based on OpenType style fonts and is in some way similar to the more known True Type Font (.ttf). TTF fonts are widely known and used on the Windows platform. Those feature rich kind of fonts are used for high quality font displaying for the system and local office-and design documents. WOFF aims at closing the gap towards making those features available on the web. With these fonts it becomes possible to show nice looking fonts on paper and web presentations in almost the same way. In order to make WOFF a success, several open source projects joined forces, among them Pango and Qt, and contributed to harfbuzz, a OpenType text shaping engine. Firefox and other web engines can handle WOFF inside SVG web graphics and HTML web documents using harfbuzz. Inkscape uses at least since version 0.91.1 harfbuzz too for text inside SVG web graphics. As Inkscape is able to produce PDF’s, designing for both the web and print world at the same time becomes easier on Linux.

Where to find and get WOFF fonts?
Open Font Library and Google host huge font collections . And there are more out on the web.

How to install WOFF?
For using inside inkscape one needs to install the fonts locally. Just copy the fonts to your personal ~/.fonts/ path and run

fc-cache -f -v

After that procedure the fonts are visible inside a newly started Inkscape.

How to deploy SVG and WOFF on the Web?
Thankfully WOFF in SVG documents is similar to HTML documents. However simply uploading a Inkscape SVG to the web as is will not be enough to show WOFF fonts. While viewing the document locally is fine, Firefox and friends need to find those fonts independent of the localy installed fonts. Right now you need to manually edit your Inkscape SVG to point to the online location of your fonts . For that open the SVG file in a text editor and place a CSS font-face reference right after the <svg> element like:

</svg>
<style type=”text/css”>
@font-face {
font-family: “Aladin”;
src: url(“fonts/Aladin-Regular.woff”) format(“woff”);
}
</style>
…

How to print a Inkscape SVG document containing WOFF?
Just convert to PDF from Inkscape’s file menue. Inkscape takes care for embedding the needed fonts and creates a portable PDF.

In case your prefered software is not yet WOFF ready, try the woff2otf python script for converting to the old TTF format.

Hope this small post gets some of you on the font fun path.

Avec de profondes modifications en son cœur, SUSE Linux Entreprise donne la voie à suivre pour le projet openSUSE.

Les changements sont tellement importants que l’objectif est de construire une nouvelle version standard d’openSUSE, malgré le succès d’openSUSE Tumbleweed.

Cette version pourrait s’appeler openSUSE 42. (C’est actuellement le nom du projet sur l’openSUSE Build Service) . Sa sortie est prévue autour de la SUSECon d’Amsterdam du 2 au 6 novembre 2015.

Contrairement aux anciennes versions standards, openSUSE 42 s’alignera sur les sorties et les “service packs” de SUSE Linux Enterprise.

Il y a déjà 2000 paquets dans openSUSE 42. Ce sera une version avec un support à long terme assuré par la communauté et par SUSE.

Une première milestone (version en développement) est prévue pour bientôt. Toute fois aucun live CD n’est envisagé pour le moment.

—

Syvolc

Source : https://news.opensuse.org/2015/06/26/work-begins-on-totally-new-opensuse-release/

After more than two years of development, 15 pre-releases and more than 2000 commits we proudly present release 2.0 of the DocBook Authoring and Publishing Suite, in short DAPS 2.0.

DAPS lets you publish your DocBook 4 or Docbook 5 XML sources in various output formats such as HTML, PDF, ePUB, man pages or ASCII with a single command. It is perfectly suited for large documentation projects by providing profiling support and packaging tools. DAPS supports authors by providing linkchecker, validator, spellchecker, and editor macros. DAPS exclusively runs on Linux.

Download & Installation

For download and installation instructions refer to https://github.com/openSUSE/daps/blob/master/INSTALL.adoc
Highlights of the DAPS 2.0 release include:

• fully supports DocBook 5 (production ready)
• daps_autobuild for automatically building and releasing books from different sources
• support for EPUB 3 and Amazon .mobi format
• default HTML output is XHTML, also supports HTML5
• now supports XSLT processor saxon6 (in addition to xsltproc)
• improved “scriptability”
• properly handles CSS, JavaScript and images for HTML and EPUB builds (via a “static/” directory in the respective stylesheet folder)
• added support for JPG images
• supports all DocBook profiling attributes
• improved performance by only loading makefiles that are needed for the given subcommand
• added a comprehensive test suite to ensure better code quality when releasing
• tested on Debian Wheezy, Fedora 20/21 openSUSE 13.x, SLE 12, and Ubuntu 14.10.

Please note that this DAPS release does not support webhelp. It is planned to re-add webhelp support with DAPS 2.1.

For a complete Changelog refer to https://github.com/openSUSE/daps/blob/master/ChangeLog

Support

If you have got questions regarding DAPS, please use the discussion forum at https://sourceforge.net/p/daps/discussion/General/. We will do our best to help.

Bug Reports

To report bugs or file enhancement issues, use the issue Tracker at https://github.com/openSUSE/daps/issues.

The DAPS Project

DAPS is developed by the SUSE Linux documentation team and used to generate the product documentation for all SUSE Linux products. However, it is not exclusively tailored for SUSE documentation, but supports every documentation written in DocBook.
DAPS has been tested on Debian Wheezy, Fedora 20/21 openSUSE 13.x, SLE 12, and Ubuntu 14.10.

The DAPS project moved from SourceForge to GitHub and is now available at https://opensuse.github.io/daps/.

Recently Thomas and me met in person and thought about an alternative approach to bring our big file chunking to the next level. “Big file chunking” is ownClouds algorithm to upload huge files to ownCloud with clients.

This is the first of three little blog posts in which we want to present the idea and get your feedback. This is for open discussion, nothing is set in stone so far.

What is the downside of the current approach? Well, the current algorithm needs a lot of distributed knowledge between server and client to work: The naming scheme of the part files, semi secret headers, implicit knowledge. In addition to that, due to the character of the algorithm the server code is too much spread over the whole code base which makes maintaining difficult.

This situation could be improved with the following approach.

To handle chunked uploads, there will be a new WebDAV route, called remote.php/uploads. All uploads of files larger than the chunk size will go through this route.

In a nutshell, an upload of a big file will happen as parts to a directory under that new route. The client creates it through the new route. This initiates a new upload. If the directory could be created successfully, the client starts to upload chunks of the original file into that directory. The sequence of the chunks is set by the names of the chunk files created in the directory. Once all chunks are uploaded, the client submits a MOVE request the renames the chunk upload directory to the target file.

Here is a pseudo code description of the sequence:

1. Client creates an upload directory with a self choosen name (ideally a numeric upload id):

MKCOL remote.php/uploads/upload-id

2. Client sends a chunk:

PUT remote.php/uploads/upload-id/chunk-id

3. Client repeats 2. until all chunks have successfully been uploaded 4. Client finalizes the upload:

MOVE remote.php/uploads/upload-id /path/to/target-file

5. The MOVE sends the ETag that is supposed to be overwritten in the request header to server. Server returns new ETag and FileID as reply headers of the MOVE.

During the upload, client can retrieve the current state of the upload by a PROPFIND request on the upload directory. The result will be a listing of all chunks that are already available on the server with metadata such as mtime, checksum and size.

If the server decides to remove an upload, ie. because it hasn’t been active for a time, it is free to remove the entire upload directory and return status 404 if a client tries to upload to. Also, a client is allowed to remove the entire upload directory to cancel an upload.

An upload is finalized by the MOVE request. Note that it’s a MOVE of a directory on a single file. This operation is not supported in normal file systems, but we think in this case, it has a nice well descriptive meaning. A MOVE is known as an atomic and fast operation, and that way it should be implemented by the server.

Also note that only with the final MOVE the upload operation is associated with the final destination file. We think that this approach already is a great improvement, because there is always a clear state of the upload with no secret knowledge hidden in the process.

In the next blog I will discuss an extension to this that adds more features to the process.

What do you think so far? Your feedback is appreciated, best on the ownCloud devel mailinglist!

I did a huge cleanup of my firefox profile today, which resulted in me removing tons of stuff (from dead bookmarks to useless addons to many other subtle or not that subtle stuff).
The whole process helped to return firefox in a rather working/healthy state, but also served as a good reminder of something i had in mind for quite a while now.
I wanted to document my firefox setup once i decided that it is stable or has reached a state that pleases me usability wise (hard if you consider all the changes that happened to it throughout the years).

This post serves as a good linkable source too for all those that ask me how i configure my firefox and a list of addons i practically recommend (through my own usage of them). So without further ado:
For simplicity and to give their usage in a glance i have separated them in 4 distinct categories. The list is of the form “Addon - reasoning”, i didn’t include links since all of them are readily available on addons.mozilla.org

Safe Browsing

NoScript - Blocks many stuff (js, flash, java etc) can allow whitelisting of sites that you deem safe enough to allow their code to run.
RequestPolicy - Similar in spirit to NoScript but for any cross site requests.
Certificate Patrol - Monitors and shows changes in certificates (suspicious or not)
HTTPS-Everywhere - Defaults to HTTPS by default for those sites that provide it but not offer it as the default redirect
Privacy Badger - Pretty much covered by the others but there to catch anything the others might actually miss
RefControl - To see and track what the Ref header sends to the site i visit.
Priv3 - Blocks tracking by social buttons (like, +1, etc)
Self-Destructing Cookies - Self-Explanatory addon. once i leave the site, the cookies go BOOM!

Quality of Life

GreaseMonkey - Allows me to overwrite or extend site behaviour through js
Stylish - overwrite the site CSS (really a must for more sites than i can count)
Session Manager - I always had issues with tabs management with the default manager, this solves it
uBlock Origin - Ads! many of them are so distracting and intrusive i just don’t like them.
Reddit Enchancement Suite - I browse Reddit A LOT, this makes it a tad more bearable.
Cleanest Addon Manager - with that many addons…
Google Search by Image - To make finding the source of an image quicker …

User Interface/User Experience

Pentadactyl - I am a vim and a very keyboard/keybinding heavy user, this adds better kb based control.
Socialite - Shows the current vote rating on reddit for the link i browse or allows me to quick submit it there.
The AddonBar (restored) - Firefox removed the addonbar recently, this brings it back.
Config Descriptions - I fiddle a lot with about:config sometimes, this adds explanations.
Tree Style Tab - a must, a way better visualization of the tabs i open and their relationship.

Misc

Rikaichan - This allows me to get an explanation of an unknown japanese word by just hovering it with my mouse.

Just to see how things evolve (or hopefully progress) i’ll also be keeping track of this and updating/making a listing yearly, seeing how my browsing environment will have changed by next June!