So i had planned to do blogging each day but at the end there's too many interesting things going on at the same time to get time to write something down.
GCDS has already ended and i'm waiting at the Fataga hotel hacking area with other barcelona fellows until late as our plane leaves at 00:05 of tomorrow.
Let's try to summarize a whole week of GCDS :-D
I have some new gear now: Kubuntu, GCDS and KDAB tshirts and a Qt towel
Keynotes where rather interesting, RMS speech had as expected some Mono bashing, Sugar shown us a different way of having a Desktop Environment, Quim Gil told us that Maemo was switching to Qt as GUI toolkit and Robert Lefkowitz told us we use Free Software not because it's better, but because we are gentleman and he convinced me :D
Then we had the cross-desktop lighting talks that started with Frank Karlistech announcing Open-Pc project and followed with lots of other fast talks not really cross-desktop but one of each
Next day i attended some more so-called cross-desktop talks and sadly most of the focused only on one of the two projects, i think i managed to be quite equidistant in my poppler talk but maybe i wasn't :D
After day Akademy started with a nice keynote telling us that Free Software will save the world, we rock! Then we had the IDE battle with KDevelop and Qt Creator, Qt Creator requiring you to grant Nokia a commercial license so that they accept your code makes it the loser in my book. Then GAmaral talked us about KDE in Mexico and Knut introduced some students that had been working on Qt.
Nokia payed us a nice party that night in the harbour
Next day we had Akademy too, i attended talks about Qt graphic things, improving productivity, improving design and improving git for Qt and KDE.
After lunch, Sebastian did a keynote on our own future followed by dfaure telling us how to fix bugs faster and Olivier doing the same talk i had prepared for Akademy-es :D After that i switched to the Business track with Till, Nikolaj, Bart and Frank telling us how to win money with KDE.
And finally Akademy almost ended with the Akademy Award ceremony, with three of the key people in our community awarded.
The real Akademy ending was at the basysKom party
From there all turned even more crazy, with KDE eV assembly, ereslibre and antlarr saving Behdad from dead (well just leading him to the hospital), KDE España assembly, bofhs, Akademy-es (more on that on the dot shortly) a trip to the beach with a bug in the transportation system, having Behdad explaining me how font rendering works, discussing about poppler with lost of people and yet another party this time sponsored by Collabora.
All in all i think the GCDS was ok, though as always with this kind of events there were several things i did not like much like people being spread on lots of hotels, having one auditorium room outside the main building with too much time travel to the other, having the travel agency (Viajes El Corte Inglés sucks!) kind of scamming me, the University being too far away from the hotel and Akademy-es being eaten by a too much bigger event, on the other hand having the possibility to meet some gnome people i needed to talk to was a pleasant experience even if it made it a bit more difficult to start talking with people at parties because maybe you spoke with someone that did not have much in common with you.
Saturday, July 11, 2009
Monday, June 01, 2009
Okular, PDF and file permissions
There seems to be some controversy about how Okular handles file permissions (sometimes called DRM) in PDF files. I will put here my personal opinions (weird i have to say this since this is *my* blog so when i write here it's always *my* personal opinion).
As a note for those that don't know me much, i was KPDF maintainer from 2004 or so till it's death, mentored the SoC project that created Okular, a regular Okular developer and i'm also the maintainer of poppler since a few time ago, so well, i think we'll agree i know what i'm talking about ;-)
Let's analize the bug-reporter sentence:
"So what I want to know is: why are people putting code into Debian
that limits our freedom? Why are people putting such code into KDE?"
So he wants to KNOW why *we* did this, yet he mails Debian bug tracker. First weird thing man, we have the okular irc channel, the okular mailing list and the kde bug tracker, all this are MUCH BETTER places for knowing.
First question:
"why are people putting code into Debian that limits our freedom?"
is very similar to
"why is people coding in GPL that that limits our freedom?" from the BSD fanboys. It all boils down to your freedom ends where other people freedom starts. And someone freely decided he doesn't want you to copy his PDF, you may hate him for that, but it is his freedom, *his* license, and we all like people respecting our license (GPL) so we should respect others, or are we just going to respect licenses we like?
Second question:
"Why are people putting such code into KDE?"
because it's what the PDF specification says and we want to have a PDF reader, don't we?
Now, there's even a LWN article talking about it (sorry folks, you have to pay them to read that unresearched article), but i'll quote here a small part (under the fair quotation law i hope)
he means evince has it disabled by default and okular enabled by default? I don't see a "tend to" here
KPDF had the exact very same behaviour since 2005. And well, if Okular is not called KPDF in KDE 4 it's just because we decided to support more formats but for the rest it's the same program.
Repeat with me Okular is not Linux, Okular is KDE, Okular runs in Linux, Okular runs in Solaris, Okular runs in FreeBSD, Okular runs in Windows, Okular runs in Mac OS X.
And now my final words. I hate DRM, i don't buy DRM enabled things (or try as hard as i can not to) BUT KDE is not the place to protest about that. The place to protest against that is with your wallet (don't buy DRM'ed things), with your vote (don't vote politicians that pass pro-DRM laws) or even in the streets in demonstrations.
As a note for those that don't know me much, i was KPDF maintainer from 2004 or so till it's death, mentored the SoC project that created Okular, a regular Okular developer and i'm also the maintainer of poppler since a few time ago, so well, i think we'll agree i know what i'm talking about ;-)
Let's analize the bug-reporter sentence:
"So what I want to know is: why are people putting code into Debian
that limits our freedom? Why are people putting such code into KDE?"
So he wants to KNOW why *we* did this, yet he mails Debian bug tracker. First weird thing man, we have the okular irc channel, the okular mailing list and the kde bug tracker, all this are MUCH BETTER places for knowing.
First question:
"why are people putting code into Debian that limits our freedom?"
is very similar to
"why is people coding in GPL that that limits our freedom?" from the BSD fanboys. It all boils down to your freedom ends where other people freedom starts. And someone freely decided he doesn't want you to copy his PDF, you may hate him for that, but it is his freedom, *his* license, and we all like people respecting our license (GPL) so we should respect others, or are we just going to respect licenses we like?
Second question:
"Why are people putting such code into KDE?"
because it's what the PDF specification says and we want to have a PDF reader, don't we?
Now, there's even a LWN article talking about it (sorry folks, you have to pay them to read that unresearched article), but i'll quote here a small part (under the fair quotation law i hope)
Applications which do implement this "feature" tend to disable it by default.
he means evince has it disabled by default and okular enabled by default? I don't see a "tend to" here
Perhaps this behavior is result of the relative newness of this application; as it accumulates more users, the pressure for more user-friendly behavior is likely to grow.
KPDF had the exact very same behaviour since 2005. And well, if Okular is not called KPDF in KDE 4 it's just because we decided to support more formats but for the rest it's the same program.
Linux, at all levels, has felt free to ignore standards when following them makes no sense.
Repeat with me Okular is not Linux, Okular is KDE, Okular runs in Linux, Okular runs in Solaris, Okular runs in FreeBSD, Okular runs in Windows, Okular runs in Mac OS X.
And now my final words. I hate DRM, i don't buy DRM enabled things (or try as hard as i can not to) BUT KDE is not the place to protest about that. The place to protest against that is with your wallet (don't buy DRM'ed things), with your vote (don't vote politicians that pass pro-DRM laws) or even in the streets in demonstrations.
Friday, May 29, 2009
A day in scam land
So i'm looking for two tickets for FIB now that tickets are sold out.
One goes to google and finds three announcements on craigslist, price is okaish so you contact the posters ... and all you get are scammers.
The first one says "please provide me this details asap so i can start this transaction asap through craigslist they will contact you", a mention to craigslist itself, this must be safe for sure, but then you go to craigslist and see a page that explicitly says that they don't handle transactions at all. The announcer does not answer back once i point her to this page.
The second and third announcements end up being from the same mail address, interesting as one announcement is from Barcelona and the other from London, one asks 400€ and other 380£. The poster says he is not able to meet me and Barcelona and neither an hypothetic friend of mine in London because "he works all day" (though answers my mails in 5 minutes). I ask him to post pictures of the tickets with a newspaper of today or the very same mail i just send and he just sends pictures of the tickets themselves. More over he says we'll do the transaction via "Ebay and Square Trade". If you look at Square Trade, they are not a transaction company at all either, seems someone is using their name to scam gullible people.
So basically it seems that yeah, the prices they were selling the tickets were "too low" and are just a honey pot to scam people.
I hate how the world is full of people that don't any respect for others at all. Meh :-/
One goes to google and finds three announcements on craigslist, price is okaish so you contact the posters ... and all you get are scammers.
The first one says "please provide me this details asap so i can start this transaction asap through craigslist they will contact you", a mention to craigslist itself, this must be safe for sure, but then you go to craigslist and see a page that explicitly says that they don't handle transactions at all. The announcer does not answer back once i point her to this page.
The second and third announcements end up being from the same mail address, interesting as one announcement is from Barcelona and the other from London, one asks 400€ and other 380£. The poster says he is not able to meet me and Barcelona and neither an hypothetic friend of mine in London because "he works all day" (though answers my mails in 5 minutes). I ask him to post pictures of the tickets with a newspaper of today or the very same mail i just send and he just sends pictures of the tickets themselves. More over he says we'll do the transaction via "Ebay and Square Trade". If you look at Square Trade, they are not a transaction company at all either, seems someone is using their name to scam gullible people.
So basically it seems that yeah, the prices they were selling the tickets were "too low" and are just a honey pot to scam people.
I hate how the world is full of people that don't any respect for others at all. Meh :-/
Thursday, May 28, 2009
Your talk in Akademy-es 2009
You may that we are celebrating Akademy-es 2009 inside GCDS. If you did not know you do now ;-)
So if you think you have something to say to the Spanish community that will gather there do not hesitate to read the call for activities and submit one before the 8 of June!
We are waiting for them ;-)
So if you think you have something to say to the Spanish community that will gather there do not hesitate to read the call for activities and submit one before the 8 of June!
We are waiting for them ;-)
Tuesday, May 19, 2009
Buenos Presagios (Good Omens)
So yesterday i finished reading Buenos Presagios the translation of Good Omens by Terry Pratchett and Neil Gaiman, a book written in 1990 and that has the Spanish first edition on ... April 2009 ... it's intriguing how some editorials decide to translate not so great books asap and better ones are left on the dust for almost 20 years.
And now onto the book, it's my first Gaiman book, but my n-th Pratchett one and i have to say it lives to the expectation.
It's a novel about the end of the world because of the Armageddon, the coming of the Antichrist, with the Four Horsemen of the Apocalypse, a witch that did 300 years of exact predictions and an earth-living Angel and Demon that prefer to work together instead of for their far away bosses. All that mixed with the great humour that Pratchett gives to all his books, will have to read some Gaiman to see if it's good too (Just saw he's the writter of Stardust, i haven't read the book but the movie was entertaining). The only thing i did not like much is that book ending is a bit weak in my opinion, but otherwise a very recommended book.
And now onto the book, it's my first Gaiman book, but my n-th Pratchett one and i have to say it lives to the expectation.
It's a novel about the end of the world because of the Armageddon, the coming of the Antichrist, with the Four Horsemen of the Apocalypse, a witch that did 300 years of exact predictions and an earth-living Angel and Demon that prefer to work together instead of for their far away bosses. All that mixed with the great humour that Pratchett gives to all his books, will have to read some Gaiman to see if it's good too (Just saw he's the writter of Stardust, i haven't read the book but the movie was entertaining). The only thing i did not like much is that book ending is a bit weak in my opinion, but otherwise a very recommended book.
Labels:
book,
buenos presagios,
good omens,
neil gaiman,
terry pratchett
Monday, May 11, 2009
Poppler 0.11.0 (0.12 Alpha 1) released
Available from
http://poppler.freedesktop.org/poppler-0.11.0.tar.gz
WARNING: This is a unstable release, it is actually 0.12 Alpha 1 release, it should work like any release from the 0.10 branch, but do not blame us if it turns the sea into Coke.
Changes against the 0.10 branch:
core:
* Add initial support for color management
* Remove case-insensitive matching of filenames in PDFDoc constructor
* Fix extraction of some ActualText content
* More work on Annotations support
* Improve font rendering in Cairo output device
* Fix bug in cairo backend with nested masks
* Fix cairo luminosity smask rendering
* Add optionally text support to Cairo output device
* Add the possibility of setting the datadir on runtime
* Return an error code instead of a boolean when saving
* Make the font scanner more versatile
* Small opimization in documents that use PostScriptFunction
* Minor optimization to Stream handling
* Fix some compile warnings
glib:
* Optional content support
* More work on Annotations support
* Improvements to the demo
* Documentation improvements
* Fix build when compiling with GTK_DISABLE_SINGLE_INCLUDES
Qt4:
* Support URI actions for Table Of Contents items
* Documentation improvements
* Improvements to the demo
* Add a FontIterator for iterating through the fonts of the document
utils:
* Allow the use of cropbox in pdftoppm
* Make pdftohtml output png images when the image is not a jpeg
* Make pdftotext accept cropping options like pdftoppm
* Support rendering non-square pixels in pdftoppm
build system:
* Require Cairo 1.8.4 for the Cairo output device
* Require CMake 2.6 when using the CMake build system
* Optionally require libpng for pdftohtml
* Optionally require libcms for color management
Testing, patches and bug reports welcome.
http://poppler.freedesktop.org/poppler-0.11.0.tar.gz
WARNING: This is a unstable release, it is actually 0.12 Alpha 1 release, it should work like any release from the 0.10 branch, but do not blame us if it turns the sea into Coke.
Changes against the 0.10 branch:
core:
* Add initial support for color management
* Remove case-insensitive matching of filenames in PDFDoc constructor
* Fix extraction of some ActualText content
* More work on Annotations support
* Improve font rendering in Cairo output device
* Fix bug in cairo backend with nested masks
* Fix cairo luminosity smask rendering
* Add optionally text support to Cairo output device
* Add the possibility of setting the datadir on runtime
* Return an error code instead of a boolean when saving
* Make the font scanner more versatile
* Small opimization in documents that use PostScriptFunction
* Minor optimization to Stream handling
* Fix some compile warnings
glib:
* Optional content support
* More work on Annotations support
* Improvements to the demo
* Documentation improvements
* Fix build when compiling with GTK_DISABLE_SINGLE_INCLUDES
Qt4:
* Support URI actions for Table Of Contents items
* Documentation improvements
* Improvements to the demo
* Add a FontIterator for iterating through the fonts of the document
utils:
* Allow the use of cropbox in pdftoppm
* Make pdftohtml output png images when the image is not a jpeg
* Make pdftotext accept cropping options like pdftoppm
* Support rendering non-square pixels in pdftoppm
build system:
* Require Cairo 1.8.4 for the Cairo output device
* Require CMake 2.6 when using the CMake build system
* Optionally require libpng for pdftohtml
* Optionally require libcms for color management
Testing, patches and bug reports welcome.
Thursday, April 30, 2009
i18n as second citizen in KDE
Sadly it seems that i18n (short for internationalization), that is, making your program available for non english speakers is a second citizen between KDE developers.
Programmers are treating bugs reported against i18n as non critical when effectively they are making their program unavailable for lots of users.
You may think this is a personal perception, but let's mention some examples:
* Plasma: Category names ("Application Launchers", "Astronomy") in the drop down box of the "Add Widget" dialog are untranslatable. Plasma developers excuse themselves saying i18n is not their best aptitude
* Places names are set after first use and don't follow the user locale https://bugs.kde.org/show_bug.cgi?id=177536
* KMail view names have a similar problem, can't find the bug number right now
* Places names for devices are not translatable http://lists.kde.org/?t=123937583500004&r=1&w=2
* Amarok: Items in the playlist layout editor are not translated https://bugs.kde.org/show_bug.cgi?id=189750
* Amarok: Default layout names are not translatable https://bugs.kde.org/show_bug.cgi?id=189751
These are just some examples, don't feel finger pointed if your app is here.
You'll notice that some of this bugs/reports have patches or suggestions on how to fix it, yet nothing has been done to fix them.
So please, don't treat i18n as second citizen, you *really* don't want to alienate so much users from your program.
Programmers are treating bugs reported against i18n as non critical when effectively they are making their program unavailable for lots of users.
You may think this is a personal perception, but let's mention some examples:
* Plasma: Category names ("Application Launchers", "Astronomy") in the drop down box of the "Add Widget" dialog are untranslatable. Plasma developers excuse themselves saying i18n is not their best aptitude
* Places names are set after first use and don't follow the user locale https://bugs.kde.org/show_bug.cgi?id=177536
* KMail view names have a similar problem, can't find the bug number right now
* Places names for devices are not translatable http://lists.kde.org/?t=123937583500004&r=1&w=2
* Amarok: Items in the playlist layout editor are not translated https://bugs.kde.org/show_bug.cgi?id=189750
* Amarok: Default layout names are not translatable https://bugs.kde.org/show_bug.cgi?id=189751
These are just some examples, don't feel finger pointed if your app is here.
You'll notice that some of this bugs/reports have patches or suggestions on how to fix it, yet nothing has been done to fix them.
So please, don't treat i18n as second citizen, you *really* don't want to alienate so much users from your program.
Subscribe to:
Posts (Atom)
