xet7 blog

If Email attachment does not open

2009-01-12T23:54:00.001+02:00

1) Wrong file extension
Rename file and try again

Text: doc, docx, rtf, odt, html, txt, xml, pdf
Spreadsheet: xls, xlsx, ods
Presentation: ppt, pptx, odp
Image: jpg / jpeg, gif, png, bmp, tif / tiff, targa
Audio: wav, mp3, ogg, flac
Video: avi, mp4, flv

Why

Save as Word document
Filename: __________.doc
File format: Word document (*.docx)

How correct file extension

Save as Word 97-2003 document
Filename: __________.doc
File format: Word 97-2003 document (*.doc)

Software

OpenOffice: odt, ods, odp
Microsoft Office 2007: docx, xlsx, pptx
Notepad or WordPad: html, txt, xml
More file extensions: http://filext.com
More software: http://www.theopendisc.com/education/

other language: http://translate.google.com

2) Corrupted file
Download and open file.

http://www.openoffice.org
Finnish language: http://fi.openoffice.org

3) Don't know what it is
Download and open file.

Windows: xvi32 hex editor http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
Linux: ghex . After install it goes to menu Applications / Programming

Latest Updates

2009-01-11T19:58:00.009+02:00

Hi,
welcome everybody from around the world, enjoy your stay! :)

Web address of this blog:
http://blog.xet7.org

I have begun to write to this blog again, because it's faster to update than my old websitehome. I'm currently adding more links to here.

About my previous blog entries of year 2006:

2006-07-09 OpenOffice for Ruby: I don't have plans to do it.
2006-02-07 Shed Skin: I tried it a little, but didn't continue to use it.

Some replies etc...

2006-07-09T11:33:00.001+03:00

From: James Britt

Date: 9.7.2006 3:12

Xet7 wrote:
> Hi,
> it would be nice, if you could try to reach Daniel and get permission to change
> license. I'd like to at least try to do something with it, because getting report
> in OpenOffice format would be cool, I need it for my app. I hope you don't mind,
> that I posted your reply at my blog, I can remove it if you want:
> http://blog.xet7.org

No, that's fine. It might answer questions for others, too,
I just sent E-mail to Daniel at what I believe is his address at
openoffice.org.

I'll let you know what he says, and if I can change the OOo4R license. If you can use OOo4R I expect you'll still need to do some additional work. Do you think you'll be adding on to OOo4R? If the library is released under Ruby's license, would you care to take over or share in
project ownership of OOo4R?

I would probably *use* such a tool if it existed, ad perhaps look at bugs and such if need be; I just don't have the wherewithal to go fix it up and make it work right myself. :)

> I'm also at #ruport channel with nick xet7 as much as I can. It would be
> much easier if license could be changed or dual lisenced to Ruby license.
> Well, I could of course take just ideas from that, but getting permission
> to that code could simplify things.
> I could have some ideas from PyOpenOffice project too:
> http://www.bezirksreiter.de/PyOpenOffice.htm
>
> Thanks for replying me so fast,

Sure. I'll let you know what I hear.
-----
And then my reply:
Hi,
I will try to figure it out and make changes, and if I get any changes done,
then I will be interested in taking over or share in project ownership of OOo4R.
I'll let you know if I get anywhere, and if I have additional questions.
-Xet7

2006-07-09T00:20:00.001+03:00

Here's what I'm trying to do now: get Ruport to have report output as OpenOffice Writer documents with OpenOffice for Ruby. Problem is the license, that is GPL, and here's the answer from author:

Sender: James Britt
Date: 8.7.2006 23:19
Subject: Re: OpenOffice for Ruby?

Xet7 wrote:
> Hi,
> are you still developing OpenOffice for Ruby?
> http://rubyforge.org/projects/ooo4r/

No. I've pretty much pushed that aside. I haven't had the time to really look after it, and with the release of OOo 2, the file formats are now different.

> Are there any plans to continue development, or have you moved to other
> projects?

The last time someone inquired about OOo4R, they wanted to know if a gem version was available. I did some work to do that, but I don't think I ever publicly released it. In the meantime I've been too busy with work (Ruby work!) and don't have the same need for an OOo tool.

> How can this code be used in commercial projects? Because it is
> GPL, does it mean that applications that uses it, must be GPL too?

If you use GPL'ed code, then the results must be GPL as well. My code was based on Daniel Carrera's OOoExtract lib, which was under the GPL. So I don't know if I have much choice in changing the license.

> How much features it has, can I make with it a Writer document that
> includes graphs? Or should I look at other packages for OpenOffice support?

I started off with Daniel's code, which allowed for easy searching and data extraction for OOo docs. I wanted a way to create Writer documents from scratch, and started on OOo4R. I had hopes that it would lead to a pure-Ruby tool for the creation and manipulation of OOo files, including Writer, Presenter, and whatever the spreadsheet thing is called.

This turned out to be a massive task. The XML specs for OOo documents are amazingly complex. So I lowered my sites to being able to at least create or edit Writer docs. I then got stuck on some zlib bugs that kept corrupting my files.

As time went on my interest faded. I had hoped that making the code a RubyForge project would attract other developer who might want to help push things along, but that never happened. And now, with OOo2, the XML formats have changed, so my code is outdated.

There are some useful features in the code, but it is not strikingly robust. I had trouble understanding some REXML behavior, so adding or manipulating arbitrary elements in a document was buggy. The released code includes some tests and samples, so that should give you a general idea of what it does. But there is nothing there for graphics or anything fancy; I never got around to understanding that markup.

I saw your other E-mail, with the irc log. My suggestion is to take the OOo4R code and steal whatever ideas you think are useful, and write your own version that targets the current OOo document XML.

If you really prefer to make a go of things with the existing code, let me know and I'll see if I can reach Daniel and get permission to change my license.

Thanks, and I hope you can get some use from OOo4R.

James Britt

Trying out Shed Skin...

2006-02-07T13:43:00.001+02:00

I'm trying out Shed Skin Python to C++ converter, with small text file processing code at first, and maybe later something more advanced later.