Showing posts sorted by date for query latex. Sort by relevance Show all posts
Showing posts sorted by date for query latex. Sort by relevance Show all posts

March 25, 2008

Document Freedom Day


This one is going to be short, I promise.

Tomorrow is going to the the "Document Freedom Day". I intend to celebrate it in Lisbon. If you want to celebrate it in Portugal you might be interested in checking about the events in Lisbon and Oporto. If you want to know about other countries, there's a list aggregating the events happening all over the world.

Document Freedom is an important matter. I've been a fan and user of LaTeX for more than 10 years. The main reason I liked it in the first place was the easyness of creating, writting an maintaining a document. I remember having a really old 386 laptop which only use was a LaTeX compiler, the vim editor and a DVI viewer. What starting as being "wow, this is a cool new way of doing stuff, without that boring formating crap and I'm really more produtive with it!", quickly started being a lot more things, as I stumbled upon more advantadges. See, LaTeX is an Open Format. Besides being available in any Operating System I stumbled upon, the fact that it is distributed under the terms of the LPPL, thus being free software, made it suitable for a lot of uses. Heck, I earned some real money doing translators and interpreters of, or using, LaTeX. The beauty of it was that, since it was open, anybody could read, alter, interpret or otherwise manipulate a TeX document. I was happy, but the format never was really adopted but in some specific cases or scenarios, and in the academic world (specially Mathmatics, since LaTeX has the most powerful - in my oppinion at least - way of representing math formulas). On one hand, LaTeX is only suitable to produce word processing documents, formulas or presentations. Office suites give you that, and also spreadsheets and charts. On the other hand, even if fully documented, LaTeX (and TeX) aren't standards.

I heard for the first time about ODF in 2002. Of course I knew that there were concurrent formats to those of Microsoft Office, but as soon as I heard about ODF I became more happy. No, I wasn't intending to be a ODF user. I still do my documents in LaTeX, even today. But this was - finaly - a document format, open as (La)TeX, but an "office suite format", meaning that it would also cover spreadsheets and charts. The cherry on the top of the cake, those making ODF happen wanted it to be an Open Standard. Great! I was not the only one - of course - understanding the power and importance of an Open Standard for documents. Documents in an open format - specially if regulated by a standards body, warrants you long-term access to data without legal or technical barriers. In 2004 the European Union understood its importance, and demanded from the existing vendors the existence of a document standard. The ODF work was already being done, and in 2005 ODF became an OASIS standard, a step into 2006 where it became an ISO standard. In that same year I attended to XTech '06, where I met Donna that spoke about ODF, Our Document Future. It was a great presentation in many ways: The talked about the importance of digital preservation, how can we do it, and why ODF was the best choice. She then talked about the massive adoption that ODF was already having in Australia, with the Digital Preservation front efforts. That was just the beggining: Italy adopted ODF in 2007, the same year that saw ODF 1.1 as an ISO standard (1.2 should be ready in summer 2009), and nowadays ODF is being considered and already adopted, in some cames more massively than in others, in countries like Netherlands, Belgium, Finland, France, Norway, Japan, Germany and Malaysia.

But Donna also told in her 2006's presentation that the future would bring us dark clouds in our sunshining scenario: Microsoft and OOXML. She was right. See, Microsoft has no commercial interest of adopting ODF (or any standard, for the matter). Yet, with all political pressure, it is mandatory that they support a standard... So they decided to create their own, which was aprooved as an ECMA standard in December 2006 and is now in the process of trying its aprooval as an ISO standard. Microsoft doesn't really support ODF (despite their trolls saying "but we pay for the development of converters!"): if they wanted to support the ODF standard, even if not their format of choice, ODF would be integrated in a stock instalation of their Office Suite. Also, if you considered that they were never interested in contributing into making ODF a better standard (which would be the natural action of a party interested in the field) that would serve for their technical purposes, you can't really think nor expect people to believe that Microsoft was really interested in a standard. But OOXML is worse than that: it isn't open (thus, even if it turns into a standard it will never be an open standard), is encumbered with software patents, while supposedly being a XML format (like ODF) has in its specs examples that show invalid XML, and has an incomplete specification.

I could go on and on about all the process and steps that Microsoft made this last couple of years to make OOXML a standard, refering to the way they admitedly bought votes and comitees, how issues were handled and so far, but I don't think that's useful. Last October I was invited to be the chair to a debate about ODF and OOXML. Not even one of the dozens of entities that supposedly support OOXML in Portugal were available to attend. The excuse of Microsoft, for instance, was that "during the aproval process there were made personal acusations to Microsoft workers in newspapers and blogs, so we don't have conditions in participating". This same Microsoft employee writes frequently in several blogs whenever the issue arises. But what really made me stop writting much about the issue was the fact that... it's a war I can't win, and that pisses me off. Everytime someone talks about the issue, dozens of Microsoft-payed people (they admited it) go to the blogs and flood them with lies, circular references, and anti-IBM or anti-SUN messages. They have the means and the money to do that, I don't. But I still have the truth with me, and tomorrow I'll show it. Because the world doesn't need to be controled by some corporation. The world needs Document Freedom.

October 11, 2006

The Not So Short Introduction to LaTeX2e

LaTeXThe Not So Short Introduction to LaTeX2e is a freely available online GPL'd book and a big reference among the reference books on LaTeX. It's first version was written in 1995, and the first Portuguese version "Uma não tão pequena introdução ao LaTeX", was written in 2001. This year the Portuguese book saw a printed edition (the black book at the photo) which is being sold for 3€ (to pay the expenses), and - such a good book at such a low price - I got one today (yes, that picture is of my copy, the book behing it is the proceedings of YAPC::EU::2005, that I also got today).

Now, I've already read the english version a couple of times, but having this on paper is sweet, and I took a look at it (I count on reading it all, of course), but I've found some issues in several places and reported them, which lead to... a contribution from me! So, if another issue of this book comes to be printed*, my name will bne on it! ;-)

Not this is the first or the second Portuguese article/paper/book about LaTeX that has my name on it...
* a second, updated, edition on paper now exists, here.

May 18, 2006

LaTeX vs. Office's

I was talking about this over lunch with some Opera guys here on XTech, and then I attended to two presentations where people where talking about XML on your documents, and one of the presentations was in fact about ODF.

For all of those I wss just thinking .oO( damn, LaTeX does better than that for years! )

Well, now I just came across this rant that shows exactly my frustrations everytime I try to use an Office suite. Well, not all of them: the last time I has such stresses was because people tend to use .xls's for documents where you have to fill some fields... and when you must end with a printable version, it just SUCKS.

People, if you want WYSIWYG stuff, can you please at least add usabillity into it?

XTech - day 2 - part 3

Developing for the Personal InfoCloud

This presentation is actually called "Developing for The Come to Me Web"...

  • (past) I Go Get Web

    • We sought "their" information
    • Focus on content provided
    • One device
    • One use
    • Proprietary formats
    • Findability focus
    • Development metaphor was navigation
  • (now) Come To Me Web

    • "My information" is found or created
    • Focus on person using
    • Reuse
    • Attracting and keeping attracted (we want info about some stuff, but not about some other stuff)
    • Across devices
    • Open formats
    • Refindability focus
    • Development metaphor is attraction
  • Personal InfoCloud
    • This is the information one person want to have allways with him
    • As a matter of fact there isn't one person InfoCloud but four:
      • Personal InfoCloud
      • Local InfoCloud
      • Global InfoCloud
      • External InfoCloud
    • We have to make an effort to move valuable data from the external infocloud to one of the others
    • Developing to the Personal InfoCloud
      • First of all, we have to think allways about the person, he's what matters
      • Access to information
      • Organization of the information
      • Aware
        • Task (what's the data meant to be used)
        • Action (how can you use it)
        • Context (the number of disambiguities on Wikipedia shows us the importance of this)
    • Model of Attraction
      • How to attract the information to yourself?
        • The Intellectual Receptor
        • The Perceptual Receptor
        • Mechanical Receptor
        • Physical Receptor
    • Personal Information Workflow
      • Privacy...
      • People get info from local and global infoclouds and move data to the personal infocloud by:
        • Seeking
        • Recognizing
        • Retaining/Storing
        • Using/Creating
        • Following
    • Info Reuse
      • Mobility for data is really important... Thig guy should read about Ambient Networks
    • Information is needed, everywhere, with context
    • Build around people
    • Understanding Content: Assess what is provided (caution with this, have allways in mind that information is reused)
    • Assemble information for use:
      • Learn what people do with the information
      • Various use contexts
      • Usable formats for content object type
    • Rethhinking our information
    • External Structures
    • External Storage (how do we deal with data updates?)
    • Develop with Standasrds
      • Information offerings:
        • Structured
        • Flexible
        • Open Standards
        • Proprirtary or Applicvation-based Standards
        • API Friendly
      • Offer more than one option
    • InfoCloud sollutions (his contact)


Lunch time

So, I had lunch with this really cool people from Opera, who got me preety excited to attend to the presentations I had already decided to see on Opera stuff on mobile devices. Now, and before the first presentation of the afternoon, I'll try to check my e-mail...

The Intelligent Design of Microformats

So, this is the first presentation in the Foyer room I'm attending. The speaker is Ryan King, from Technorati.
The presentation can be downloaded here.


  • How to design and create formats.

  • theryanking.com

  • Technology

    • Conservative
    • add to the existing Web
    • minimum invention

  • Social

    • Promote, encourage, buid...

      • convergence
      • openness
    • not a...
      • standards body
      • proprietary project

  • Elevator Pitch - Designed for humans first
  • data format design - this isn't software development, you can't "teach" how to analyticly design a data format
  • User Centered Design
    • "web of data"
    • we need people to build the web of data
  • designing microformats
    • experiment - easy and cool, because people are open, and share thoughts, snippets,...
    • stread
    • iterate
    • watch
  • semantic markup - maintain is preery easy; converge to best practices too
  • Problem statement
    • identify the problem
    • are there any simpler problems? Can you simplify your original problem by dividing it in several easier simpler problems?
    • please please don't re-invent stuff!
    • is it really a problem?
      • ask around
      • you aren't special
      • you aren't that smart
  • Document Behaviour - use the stuff that already exists and make something based on that
    • Procedure
      • collect
      • deconstruct
      • compare

  • OK, so you really have a good idea for a microformat... what to do?


    • Proposal


      • write

      • try

      • feedback

      • iterate


    • Implementation by Scientific Method (as defined in Wikipedia), with a difference - results aren't publish only in the end, but during the whole process




In the end... MicroFormats don't convince me, at all, but the message that you shouldn't re-invent the wheel but yes extend its use is a preety good one.

BTW: graphical card crashed again on this laptop, and thins time I got to see a Kernel Oops. I really really need to do a kernel update here.

ODF: Our Document Future

So, this time it's the ODF presentation, by Donna Benjamin which I already met yesterday.

The presentation talks about three things:

  • Digital Preservation. Why does it matter?

    • Data must be preserved or it is lost. Since nowadays our data is digital, we have to digital preserve it

    • Conversion, Emulation, Migration, Encapsulation...

    • XML is free, readable, open, standard, multi-plataform, and so perfect since it won't age...


  • OpenDocument Format


    • Using an open format is REALLY IMPORTANT for so many reasons that I'll just not going to enumerate here

    • Despite what Donna says, in my oppinion is that, yes, ODF is really great, but it isn't "news"... You have stuff that has exactly the same advantages she said, like LaTeX. The only advantage of ODF to those matters is simply the massive use it has...

    • ODF _is_ the future... but has the concurrent from Micro$oft


  • Australian efforts on the Digital Preservation front

    • Australia's efforts just rulle :-P

    • vers isn't open, but do they know why?




Standardising Web Applications: Rich Web Clients at W3C

Dean Jackson from W3C and he works on Standardisation of Rich Web Clients, SVG, web on mobile phones and such.

He's looking about Standards in the Web 2.0 world. JavaScript applications are using the JS W3C's standard... There are criticisms about W3C not being concerned with the world wide web, but Dean are here to proove it wrong. Increment nowadays standards or create new ones? We don't need "one standard to rule'em all", we can support various approaches, but standards are needed.

Their focus:
* Web API's
* Web Application Formats
* Compund Document Formats

The W3C community is everyone using W3C works, and since everyone uses the web, everyone makes part of it.
* Standardise existing undocumented stuff
* Open channels of communication
* Get implementors involved

We don't have to jump from web 1.5 to 2.0, we don't need to re-invent HTML we're doing another version of it (HTML 5)...

Web API's Working Group:
* Microsoft, Mozilla, Opera, Apple, W3C
* Openness - Live specs available via CVS; all technical discussion is public
* Specs:
1 XMLHttpRequest
2 Window
3 DOM Level 3 Events
4 Selector APIs
- XPath selectors
- CSS selectors (which is going to be released this week)
5 REX
6 Future
- Client-side storage
- File upload
- Network++ (sockets?)
- <canvas> (the element and the API)
* Declarative cs. Programmatic
* Building a Web Operating System

Web Application Formats Working Group:
* HTML working group is needed?
* Web Forms 2.0
- simple extensions to HTML
- significant return for small cost
- some conflicts with XForms
- types like "range", "date", mark a field as "required" (this things are awsome!)
* XBL (they are going to try to adopt Mozilla's work on this)
* Access Control - allowing scripts to access resources from other domains (if I had this while contributing to HCL...)
* Widgets
- Packaging format and conventions
- Metadata for execution
- Media type
- discovery mechanisms
- preety cool to integrate desktop with web, a step to the "Web Operating System" (which I'm not sure I agree with)

Compound Document Formats Working Group - Framework and compounds