Support Open Document Format


Let us promote Open Document Format (ODF). The only reason I write this article is because the confusions of Microsoft Document Format (OOXML) brought by Microsoft Office against Open Document Format (ODF) brought by LibreOffice (and companions). The another reasonable reason for me is no exact match in search engine I found for “support open document format” keywords even until today. So I need to explain shortly why it is important to support ODF (and another open formats) followed by mentioning many important link resources for that. So please use ODF, use LibreOffice (or its companions), use them as far as we can. Then promote them. Propagate them so another one will use them either. I hope this article will be widely useful.


This article is a short collection of the reasons why ODF is important and why we need to avoid OOXML usages. Why we need to use LibreOffice (or its companions) and why we need to avoid Microsoft Office usage. I’m talking in Free Software (and Open Source) scope. So keep inside this scope if you want to comment please.

1. What is Open Document Format?

Open Document Format (ODF, OpenDocument) is an open format for digital documents. It consists of ODT for word processor, ODS for spreadsheet, ODP for presentation, and some more. It is popular to be LibreOffice’s default document format. It is open format comparable to Microsoft Document OOXML (DOCX/XLSX/PPTX). This is non-technical description.

Open Document Format for Office Applications (ODF) is an OASIS Consortium‘s standard format based on XML for word processor, spreadsheet, and presentation applications which has been accepted as ISO standard ISO/IEC 26300. ODF is based on Sun Microsystem’s document format for Technical documentation of Open Document Format is can be downloaded below. Technical specification of ODF can be downloaded below. This is technical description.

For more detailed explanation about ODF, refer here:

2. Why Open Document Format is Important?

Because ODF is the most vendor-neutral open format for digital documents[TDF, OOXML]. It means no one patented the format specification, it is royalty-free format, no single vendor can lock the format of the document files, it means anyone permitted to create any software without patent risk forever, and it means it is readable/writable in any application worldwide.

  • For governments: it is important to use ODF[Swapnil, OOXML][Wikibooks, Benefit][OpenDocument Fellowship, Government] because if the governments use patent-encumbered format (and as the consequence is also using proprietary software) to manipulate state document, there is no guarantee for the state confidential documents not to be leaked to the vendor. There is no guarantee if format/software vendor can not read or can not lock the software applications and furthermore lock the document files. There is no guarantee that vendor can not modify remotely any confidential document created using those document formats and proprietary software. Also, it is very important for governments to ensure no state resident can be discriminated[OASIS, Benefit] in data access because of a document format or forced to buy certain product from certain vendor[OpenForumEurope, Government].
  • For end users: it is important to use ODF (and one of the consequence is using Free Software/Open Source) because its compatibility towards other software. ODF is not patented, furthermore i.e. LibreOffice is Free Software so no algorithm to read/write ODF is patented. By using ODF, somebody helps FOSS community and also helps ODF to be recognized widely.

3. What Applications To Support Open Document Format?

LibreOffice and its companions. They are Free Software, such as:

  1. Apache OpenOffice (formerly free office suite from Sun Microsystem which LibreOffice created from. Now Apache Foundation handles its development. Licensed in Apache License 2.0.
  2. Calligra Office: free office suite from KDE. Licensed in GNU GPL and LGPL.
  3. NeoOffice: free office suite from Planamesa Software for Apple Mac OS X. Licensed in GNU GPL.
  4. Abiword: free word processor from Abisource. Licensed in GNU GPL v2.
  5. Gnumeric: free spreadsheet from GNOME Project. Licensed in GNU GPL.
  6. WebODF: free web based office suite. Licensed in GNU AGPL.

They are safe to use. And their native document formats are safe also.

4. What is OOXML?

Office Open XML (OOXML) is digital document format from Microsoft for word processors, spreadsheets, and presentations. It consists of mainly three formats: DOCX, XLSX, and PPTX. They are popular for being default document format in Microsoft Office 2007 and later. This is non-technical description.

Office Open XML (OOXML) is a XML-based document file format from Microsoft for mainly word processors, spreadsheets, and presentations applications. This format standardized by ECMA (ECMA-376) then by ISO & IEC (ISO/IEC 29500). Technical specification of Office Open XML can be downloaded in This is technical description.

For more detailed explanation, see below or see section 1 above.

5. Why Microsoft OOXML Format is Need To Be Avoided?

  • OOXML is not widely compatible with another software applications, it is best to read/modify perfectly only in Microsoft products (i.e. Microsoft Office). Even different version of Microsoft Office can not or difficult to read same OOXML format from earlier version[Wikipedia, OOXML][Swardley, OOXML][OIDBD, OOXML][ICTS, OOXML][Robweir, OOXML][Office, OOXML].
  • OOXML is encumbered in software patents[NOOOXML, Ambush]. That is dangerous for Free Software and Open Source community. Why is patent dangerous? Read below.
  • OOXML is covered by not-forever-covering[Arstechnica, Patent] Microsoft Promises[Wikipedia, Promise]. Microsoft promised “not to sue” only for “current” format of OOXML, so there is no guarantee Microsoft will keep their promises for newer version of patent-encumbered OOXML format.
  • OOXML consists of 6000 pages long[ECMA, 376] document (to compare it, POSIX/SUSv3[Wikipedia, SUS] is only 3700 pages) so it is really difficult for any Free Software developer to create perfect filter to read/write into OOXML.
  • this page explains why it is even better to deny Microsoft Office.
  • OOXML is second standard approved by ISO after ODF. We need only one standard.
  • Read this Linux Foundation Wiki article mentioning many GNU/Linux software arcitect expert statements about OOXML. Those (Free Software users) who are looking for experts’ statements should read this.

6. Why Software Patent is Dangerous?

Please read more appropriate links stated below explaining how dangerous patent is. I suggest you to read sequentially number by number below.

  1. good start to know software patent problems and its impact to any Free Software/Open Source community.
  2. describing detailed software patent problems, which is bigger than proprietary software problems.
  3. (section 4): the best summary of two mentioned articles above, suitable for newbie.
  4. (NO)OOXML is dedicated wiki explaining OOXML format in case of so users can avoid it. Those (Free Software users) who need complete OOXML references should refer to this.

7. Am I Alone With This Patent Problem?

No. Every big community and company in GNU/Linux scope aware about this problem. Please read their defense policies against software patents.

Outside them, there are also organizations to dealing with patent problems against Free Software/Open Source. These are not all, but just what I can collect for now.

8. Am I Alone to Promote ODF?

No. There are many special organizations formed to face these problems. Whether they are developing software to support ODF, or they do fundamental things about ODF, or they do educational purposes to promote ODF. They are:

  1. official site of Open Document Format.
  2. Free Software Foundation’s official statement in supporting ODF.
  3. one of the most important software project which has developed free libraries for ODF, SVG, and another document formats available in the world.
  4. The Document Foundation, organization which forked and created LibreOffice. One of the biggest supporter for ODF.
  5. OASIS Consortium, the creator of ODF.
  6. LibreOffice official site.
  7. End Software Patents project’s wiki.
  8. (NO)OOXML, dedicated wiki explaining OOXML for Free Software users.
  9. personal blog explaining many aspects of OOXML including detailed benchmarks from Free Software users’ prespective.
  10. Open Document Format in ISO official list of standards. See section ISO/IEC 26300:2006.
  11. a volunteer organization with members around the world to promote ODF.
  12. official community gathering for Open Document Format in
  13. free web based ODF editor.
  14. already explained.

9. So Practically What Can I Do?

End Users:

  • Use LibreOffice in every operating system (including Windows, Mac OS X, BSD, or any further operating system). Or, use any other of its companions mentioned earlier.
  • Save as in ODF formats (.odt, .ods, .odp).
  • Send email attachments as ODF format. Not in Microsoft OOXML format. Microsoft Office 2010 and later can save and edit ODF.
  • Deny politely any .docx (OOXML) email attachment sent by another.
  • Encourage people to install LibreOffice in every operating system possible. Or, install any other of its companions.
  • Encourage people to use ODF too.
  • Educate people like (or more than) this article tells you about importance of the ODF.


  • If you are big company, you can consider to support ODF by officially using ODF as your company document format or donate to LibreOffice development project. Of course you can donate to another of its companions too.
  • If you provide software service, you can consider to support ODF as your service document format. For example, if you have web based (server based) service, please add read/modify ODF document support.


  • Translate this article into your language and spread it.
  • Create better article than this and spread it.
  • Put ODF banners (or edit it first) created by me in your blogs.
  • Create better banners than mine.

Important Links


  1. [TDF, OOXML]
  2. [Swapnil, OOXML]
  3. [Wikibooks, Benefit]
  4. [OpenDocument Fellowship, Government]
  5. [OASIS, Benefit]
  6. [OpenForumEurope, Government]
  7. [Wikipedia, OOXML]
  8. [Swardley, OOXML]
  10. [ICTS, OOXML]
  11. [Robweir, OOXML]
  12. [Office, OOXML]
  13. [NOOOXML, Ambush]
  14. [Arstechnica, Patent]
  15. [Wikipedia, Promise]
  16. [ECMA, 376]
  17. [Wikipedia, SUS]

List of LibreOffice Related Websites


This post is a collection of links about LibreOffice. I collect both topic LibreOffice and Open Document Format. I admit that the proper diction is “links” not “websites” for the title. But for the sake of consistency with earlier posts, I keep the “websites” one. This post is my tetralogy, the fourth post after Inkscape, GIMP, and Scribus posts.

  1. downloadable official documentation for LibreOffice. The most comple in the world.
  2. official main help pages. Refers to all LibreOffice helps.
  3. list of all official supports available for LibreOffice.
  4. official LibreOffice question & answer site.
  5. project to collect FOSS people interests to contribute to LibreOffice development and to support ODF. One of the most important Free Software project.
  6. list of libraries created by the community including import/export libraries for odf, svg, cdr, visio, etc.
  7. unofficial LibreOffice forum.
  8. unofficial LibreOffice forum in Deutsch.
  9. LibreOffice forum in Dansk.
  10. LibreOffice community in Brazil.
  11. LibreOffice forum in Turkey.
  12. LIbreOffice forum in Czech.
  13. LibreOffice branding guidelines.
  14. official LibreOffice logos gallery.
  15. LibreOffice design artworks for 5.0 version.
  16. LibreOffice official marketing materials such as banner, flyer, brochures, templates, etc.
  17. a page for possible templates by the community that will be included in LibreOffice 4.4.
  18. how to contribute in LibreOffice and how to join the mailing lists.
  19. official planet from The Document Foundation members.
  20. official planet from Open Document Format organization members.
  21. official blog from The Document Foundation.
  22. official blog from Apache OpenOffice.
  23. LibreOffice 4.4 release notes, what’s new in that version.
  24. one of the most comprehensive unofficial sites about LibreOffice by an Australian professional editor and writer Jean Holis Weber.
  25. LibreOffice Documentation Team blog.
  26. personal blog of a LibreOffice hacker, Miklos.
  27. personal blog of a The Document Foundation founder and LibreOffice hacker, Thorsten.
  28. LibreOffice on Reddit.
  29. personal blog of The Document Foundation founder and a Deutsch LibreOffice hacker, Florian Effenberger.
  30. personal blog of the and LibreOffice hacker, Michael Meeks.
  31. Nabble for LibreOffice mailing lists. Nabble is a way to read mailing list in web forum form.
  32. LibreOffice community in Denmark.
  33. technical & programming blog of LibreOffice from LDCS India.
  34. mailing list archive for LibreOffice user support by
  35. list of all LibreOffice support mailing lists, excluding development mailing lists.
  36. not enough data, but he is at least LibreOffice enthusiast.
  37. personal blog of a and LibreOffice hacker, Lionel Dricot.
  38. a LibreOffice dedicated blog of Russian Dmitry Bowie.
  39. a dedicated blog for LibreOffice in Italian.
  40. a dedicated blog for LibreOffice in Indonesian.
  41. successor blog of Italian openofficelibreoffice.
  42. personal blog of a Red Hat employee and LibreOffice hacker, Caolan McNamara.
  43. community blog from Brazilian LibreOffice users and hackers.
  44. a LibreOffice contributors for Full Circle Magazine.
  45. a serious page at Hacker Public Radio providing complete links of LibreOffice tutorials to Ahuka.
  46. Kevin O’Brians blog, providing serious and comprehensive LibreOffice tutorials.
  47. providing hundreds of LibreOffice tutorials in videos.
  48. providing LibreOffice and video tutorials on Youtube.
  49. providing dozens of LibreOffice and video tutorials.
  50. providing some LibreOffice video tutorials in Portuguese.
  51. official channel from The Document Foundation for LibreOffice, contains many tutorials.
  52. providing about 7 videos about LibreOffice calc in Portuguese in Portuguese (Brazil).
  53. providing about 11 videos about LibreOffice Calc in Portuguese (Brazil).
  54. providing about 41 videos about LibreOffice Writer and 8 videos about LibreOffice Calc in Spanish.
  55. providing dozens videos about LibreOffice in English, Hindi, Tamil, Telugu, and some other languages.
  56. providing about 80+ high quality video tutorials about LibreOffice in Deutsch.
  57. providing high quality tutorials for LibreOffice, all series.
  58. popular site (similar to omgubuntu) providing many tutorials about LibreOffice.
  59. a professional software development company, contributes to LibreOffice.
  60. a mirror for Dirgita Devina’s ebooks. The most complete tutorials for LibreOffice (because of their compatibility) in Indonesian.
  61. a mirror for Rustan & Kamariah’s LibreOffice Writer ebook in Indonesian.
  62. a mirror for Yahya Nursidik’s LibreOffice Writer ebook in Indonesian.

Bleeding Edge Style Posting


I maintain about a dozen of blogs, both in Indonesian and English, and all of them talk about GNU/Linux. As a real newbie, I have written probably more than 500 articles (including ebooks) about GNU/Linux within them and outside of them. Recently I found many of my GNU/Linux friends in Indonesia excited about using Archlinux. They love Archlinux bleeding edge style of distributing software packages, they said it is rolling release. Apparently I was excited too in the way of AUR, where my friends can get newest version of same program I use directly. Archlinux gave them more advantages than Ubuntu (official or PPA) in this case. Archlinux’s bleeding edge style, I describe it personally as forever LTS, not waiting (not freezing) for stable package to release a new package. I take that concept into my new writing style. I call it bleeding edge posting. This article is also a bleeding edge post.


After seeing bleeding edge way of Archlinux, recently I thought I must take that way to write. So I fire up my old blog (restava) to bear my new style of writing. I call this style bleeding edge posting. I don’t wait my writing for long-time editing. I post my posts directly. A bleeding edge post of me is an article which is containing at least a title and a sentence. But every post contains exactly one single idea, any new idea I find, so I don’t need to be frustrated when I find an idea and I must post it quickly. A bleeding edge post is usually finished in one time sitting duration. The main advantage of bleeding edge posting is I don’t need to wait to post any new idea where waiting is a very frustrating thing for a writer like me. It is a big win, where I can provide myself ideas collection in one place so I can make more long-editing posts in another blogs based on bleeding edge posts in bleeding edge blog. It is just similar thing between Fedora (bleeding edge*) and Red Hat Enterprise Linux (conservative edge**). My restava blog is “Fedora”, and my another blogs are “Red Hat Enterprise Linux”. Another advantage is I will never forget any of new ideas anymore. Another advantage of doing bleeding edge posting is I can fill my blog with more posts every month. If you are a writer, especially in GNU/Linux scope, bleeding edge posting saves your time so much.


  • If I find something important about apt, I can write it directly. I don’t need to compose a complete writing draft, do a little research first, experience errors, fixing errors, making conclusion, etc. I write what I find, although it is just a title. Example.
  • If I find something important about Scribus and Inkscape, I can write it directly. Example and example.
  • If I find something important about Slackware and Archlinux, I do it. Example.
  • Every time I try a new GNU/Linux distribution in a live session, I always take many screenshots of it. If I have many screenshots of gNewSense, Trisquel, openSUSE, new version of Ubuntu, I can be frustrated if I don’t post them. So bleeding edge posting saves my frustration. Examples.
  • Then outside of this scope, I can write more polished post based on bleeding edge blog on another blogs. I can spend time writing long posts there, after I collect enough bleeding edge posts here. For example, after posting a post about screenshots collection of recent Ubuntu, I can write a proper Ubuntu review based on screenshots collected. Example.

It Spreads

Well, I coined my own style bleeding edge posting about one year ago. It starts with my restava. I proofed I like this style so much. It gives me more convenient way of writing. I felt comfortable so much with this style. So, I began to spread this style into my another blog. Not just restava. I did it on desaininkscape, I did it here and inside this article too.

How About Tutorial Articles?

Yes, I admit that tutorial needs more times to write. So basically I can’t write tutorial in bleeding edge style. I must write tutorials in a very careful way, very comprehensive way. Every tutorial should be correct, should be free from errors. Yes, I place my tutorials in my conservative edge blogs especially my main blog. My main blog is just one. But because I have already accustomed with bleeding edge style, I can write long articles as technical GNU/Linux tutorials. Actually they are intended to be personal notes only but anyone can consider them as tutorials. I have few examples here and here. Yes, bleeding edge style can be used as a way to write comprehensive tutorials. Surprise.

I Know It’s Funny

If you are a distribution developer, you probably will laugh at me. I know it’s funny, though. But truly Archlinux bleeding edge style is the source of this style. Probably you have more proper terms than bleeding edge posting and have using it before me. Please, you can let me know.


*) I describe Fedora as bleeding edge to compare quickly, to make sense quicker. I know Fedora prefer to be credited as leading edge. To sum it up, bleeding edge = risky while leading edge = not risky. Thanks for alunux @ #ubuntu-indonesia to point me.

**) I describe Red Hat Enterprise Linux as conservative edge just because I don’t know the antonym of bleeding edge. I don’t find it anywhere. If you know, please let me know.

Have A Closer Look to Telegram


For those using WhatsApp, LINE, and BlackBerry® Messenger™, have a closer look to Telegram. For those looking for alternative, look at Telegram. For those concerning Free Software a lot, have a same look. We will find that Telegram is a real communication system. In Free Software matter, Telegram is better than 3 mentioned above.

1. GNU GPL Licenses

Have a closer look at GPL v2 and v3 stated there for various version of Telegram clients. Telegram is Free Software.

2. Source Code

Have a closer look at at least. We can see the source code. Grab it. Study it. Modify it. Of course under Free Software license GNU GPL. So any competent person can measure how secure Telegram is.

3. Desktop Clients for GNU/Linux

Have a closer look at It is the official client directly from Telegram developer. We can install Telegram client in GNU/Linux desktop. Does WhatsApp, LINE, or BlackBerry® Messenger™ give it? No. They abandon GNU/Linux desktop.

4. Security

Have a closer look at section. Have a look at the new secure protocol named MTProto Have a look at its security hacking contest

5. Privacy

Have a closer look at Telegram cares about our privacy. No ads in Telegram. No user data collection. Easy removal for our previously saved data.

6. API

Have a closer look at Telegram API is open to everyone. So we knew CuteGram desktop client exists. So do Telegram-FOSS, Jollagram, and Sailorgram exist. They can use the API freely. They extend Telegram in much broader way in many platforms.

7. Donation

Have a closer look at Telegram doesn’t open a donation yet. They are supported by a company named Digital Fortress to run it all.


Telegram is a really free cloud-based communication system to replace WhatsApp, LINE, or BlackBerry® Messenger™. Anyone concerns about Free Software can use it.

List of Scribus Related Websites


Yesterday I posted about serious links for Inkscape and then GIMP. Now it is the time for Scribus. I admit it, there are less dedicated websites for Scribus compared to Inkscape or GIMP. But these are dedicated websites providing Scribus tutorials. If you are learning Scribus, bookmark them.

  1. official wiki for Scribus. The most complete tutorials ever made.
  2. Scribus wiki tutorials index.
  3. the must read page for newbie.
  4. list of Scribus videos.
  5. list of works created with Scribus including magazines.
  6. official Scribus monthly newsletter in web format.
  7. complete Scribus manual from FLOSS Manuals.
  8. official Scribus forum. Including high quality tutorials and showcases.
  9. Scribus forum in Deutsch.
  10. official Scribus planet.
  11. collection of serious tutorials for Scribus.
  12. serious Scribus tutorials in video from Steve Czajka.
  13. Scribus tutorials in video from Kevin Pugh.
  14. serious Scribus tutorials in video by Dai.
  15. collection of assets for Scribus.
  16. serious Scribus online course.
  17. serious videos for Scribus.
  18. Scribus tutorial in Italian.
  19. the only dedicated website today for getting started in Free Software graphic design. Including Scribus tutorials. Maintained by Staffan Melin.
  20. Full Circle Magazine created with Scribus.
  21. PCLinuxOS Magazine created with Scribus.
  22. BlenderArt magazine once ever created with Scribus.
  23. the author of Jurus Scribus! ebook in Indonesian.
  24. the creator of [dot]BlendMagz (later OMAGZ), a Blender Magazine in Indonesian.

List of GIMP Related Websites


Yesterday I posted about serious Inkscape links. Now it’s the time to post a list of serious GIMP related websites. They are dedicated websites providing tutorials about GIMP.

  1. GIMP official tutorials.
  2. GIMP official documentations.
  3. GIMP plugins.
  4. GIMP user interface design.
  5. community tutorials for GIMP.
  6. community tutorials for GIMP.
  7. community tutorials for GIMP.
  8. SitePoint tutorials for GIMP.
  9. one of the most serious tutorials website for GIMP. Provides videos.
  10. serious tutorials and paid books for GIMP.
  11. official forum for GIMP.
  12. international community forum for GIMP. Very big. Contains tutorials and gallery.
  13. international community forum for GIMP. Very big too. Contains tutorials and gallery.
  14. international community forum for GIMP. Very big too. Contains tutorials and gallery.
  15. tidy tutorials collection for GIMP.
  16. tutorials for GIMP. Provides videos.
  17. dedicated tutorial website for GIMP.
  18. Alex Standiford’s dedicated website for GIMP.
  19. complete GIMP book from Wikimedia community.
  20. GIMP dedicated blog.
  21. online GIMP courses.
  22. complete book about GIMP.
  23. serious GIMP tutorials in Photoshop community website. Written in Deutsch.
  24. GIMP tutorials in Paint Shop Pro community website.
  25. some GIMP tutorials.
  26. dedicated blog for GIMP, with topic focused on text effect.
  27. complete book about GIMP by Kat.
  28. serious video tutorials for GIMP from Showmedo.
  29. dedicated GIMP website focused on photography.
  30. dedicated tutorial website for Free Software including GIMP.
  31. basic GIMP tutorials.
  32. GIMP photo retouching tutorials.
  33. tutorial for GIMP.
  34. basic GIMP tutorials in old-school style.
  35. GIMP tutorials by Hafidz Starlight86 from Malaysia.
  36. GIMP tutorials on DeviantArt. 150,842 Pageviews
  37. GIMP tutorials on DeviantArt. 142,366 Pageviews.
  38. GIMP tutorials and showcase on DeviantArt. 138,749 Pageviews.
  39. GIMP showcase on DeviantArt. 54,594 Pageviews.
  40. serious GIMP tutorials divided in beginner, intermediate, expert classes.
  41. serious GIMP tutorials.
  42. GIMP tutorial from professional graphic designer Abduzeedo.
  43. high quality and serious GIMP tutorials in Indonesia language.
  44. GIMP tutorials from IlmuGrafis in Indonesia languange.
  45. Kaskus GIMP Thread: GIMP dedicated thread in largest Indonesian forum Kaskus.
  46. GIMP & Inkscape dedicated blog in Indonesia language.
  47. dedicated GIMP tutorials in Indonesia language.
  48. growing GIMP tutorials in Indonesia language.

List of Inkscape Related Websites


I’ve found some serious websites dedicated to Inkscape. If you are learning Inkscape, bookmark them. It is simply the same with the list of Photoshop or CorelDRAW or Blender related websites respectively but for Inkscape. I list them here.

  1. official Inkscape forum.
  2. official Inkscape planet.
  3. showing all aspects of Inkscape officially from its developer.
  4. an Inkscape blog by Tavmjong Bah.
  5. a big gallery showing both high quality tutorials and art showcases.
  6. list of Inkscape add-ons.
  7. complete quick guide for Inkscape beginner in one single page.
  8. a tutorial website dedicated to Inkscape.
  9. a very complete beginner guide to Inkscape in one single page.
  10. tutorials dedicated to Inkscape.
  11. a tutorial website dedicated to Inkscape.
  12. video tutorial collections dedicated to Inkscape.
  13. tutorials dedicated to Inkscape.
  14. complete Inkscape manual including examples in Indonesia language by Sokhibi Imgos.
  15. extensive tutorials and videos in Indonesia language dedicated to Inkscape (including GIMP and Blender) by Irfan Prastyanto.
  16. dedicated Inkscape website for game development.
  17. dedicated tutorial website for Inkscape (and GIMP).
  18. the most complete and the best video website for Inkscape ever made.
  19. a Fedoran notes about Inkscape in Deutsch.
  20. extensive Inkscape tutorials or courses in Dutch.
  21. the most complete repository of Inkscape-created artworks. It is collaborative (you can upload artworks) and free.
  22. Inkscape community on DeviantArt.
  23. Inkscape community on DeviantArt.
  24. Inkscape community on DeviantArt.
  25. similar list to this but more extensive.

I Create No Community


Indeed, I never created any community before. Moreover, I dislike to create new community. But once I ever created a community, I see it again. Again and again. What’s wrong with name “Ubuntu”? If you dislike “Ubuntu”, create your own community. Don’t enter any community to change its name. Don’t take me and my works after you change my community name. Probably I’m just a little man, but I’m not as lowly as that. I won’t create any community anymore. I am incompatible with photographs and highly more incompatible with bad manner folks. I’m not compatible with anyone. You dislike my style, let me alone. Don’t command me. This is one reason why I dislike to create community: tata krama.

LaTeX Package bundledoc in Ubuntu 12.04


I need a technique to do collect output in my LaTeX document. So, my LaTeX document will be exactly same with any LibreOffice document in which a single file contains all resource files. In LaTeX terms, collect output is called bundle. The tools to do that is bundledoc. bundledoc main purpose is to collect all resource files (LaTeX calls them dependencies) and package them into a single tarball file. Exactly same with what I need. In Ubuntu, bundledoc tool contained inside texlive-extra-utils package. It is an official package and my Precise already has this package. But the problem is texlive-extra-utils in Precise didn’t contain bundledoc package. texlive-extra-utils in Vivid has. So how to resolve this problem?

Automatic Package Management System

  1. Diagnose first. Compare them. Precise hereVivid here.
  2. Found the problem. Precise has no bundledoc.
  3. Search for texlive-extra-utils for Vivid. Found it in Launchpad.
  4. Open the package download page for that package in Launchpad.
  5. Download that package.
  6. Install with –simulate argument. See the output.
  7. Apparently, texlive-extra-utils for Vivid is no way compatible with Precise. It breaks texlive-base package in Precise.
  8. I failed with automatic package management system. These steps are deprecated.


Manual Package Management System

Special for LaTeX, actually we can install any new package by downloading the package files from CTAN. It is a big example we knew for years happened in LaTeX (CTAN) and Perl (CPAN). Big example for manual package management system.

  1. Open CTAN.
  2. Search for bundledoc.
  3. Download the package.
  4. Unzip the package.
  5. Copy the binary package to binary executable search path. I copy bundledoc package to /usr/bin directory.
  6. Copy the manual package to manpage executable search path. I copy bundledoc.1 package to /usr/local/man/man1 directory.
  7. Finish.



bundledoc command in Precise