Basically, a translator does exactly what you described in your original email. ;) Your example of gif is also the perfect example of a translator. A third party (was it Daniel Switkin?) originally wrote the gif translator. BeOS cannot read gif out of the box... but you add the gif translator (available on BeBits), and all your applications (browser, image processing apps, office apps, etc) can now read and write gif format. You can do this with about any data type you wish, including office formats. To answer 3a - yes, it can handle word processor files. 3b - addons would convert, translators allow apps to read/write that format. So you could use an office app and access a doc format via translator, load it into memory, and then "Save As" via another translator to write it into OpenDoc format. I wish we had an online BeOS Bible we could reference you to a page to read. ;) I recently talked with PeachPit press, and they have no interest in publishing an electronic version of the book. :( Deej On 4/3/07, Ar18@xxxxxxxxxxx <Ar18@xxxxxxxxxxx> wrote:
BTW, I am looking at future Haiku (as noted in the Working Groups doc) and not R1 development... if that explains where I'm coming from. -------------- Original message ---------------------- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx> > Ar18@xxxxxxxxxxx wrote: > [...] > > This is, of couse, a very simplistic approach to the issue. There > > are > > actually many issues to consider in the process: > > Something like this would be out of the scope for R1, but luckily, it > already exists in BeOS and Haiku :-) > The Translation Kit handles various file types in an independent way > (unfortunately, it lacks heavily in the document area, image support is > very good, though), and the Media Kit makes sure that all apps (that > use it) support the same set of media encoders and decoders for audio > and video. > > Bye, > Axel. > >