nur auf englisch · seulement en anglais
| LatinByrd Frequently Asked Questions |
| What are these damn X's in the converted web pages?
This is a demo mode restriction. In demo mode, every 8th character will get x'd out. Buy a license key, or request a free test key, and the X's will go away. Same for the 'DEMO' strings in the middle of converted images.
Will my LatinByrd II license key work with LatinByrd III as well? Yup. You can install your LatinByrd II license key in any version of LatinByrd III, and perhaps even in LatinByrd IV. (The latter I'm not sure of yet. But chances are you will be able to. That is, there might be no upgrade fee for LB IV. There definitely is no upgrade fee for LatinByrd III.)
SSS's web site's images seem to be destroyed... Nope, they aren't. Most of SSS's web site's images are in the new & promising PNG graphics format. Furthermore, these are paletted transparent PNGs -- converted with LatinByrd, of course. The PNG graphics format is the designated successor to GIF, with GIF showing its age for years now. Unfortunately, most common browsers, too, show their age -- the big players concentrate on battling out the featuritis war, and meanwhile forget to do their homework on basic stuff like support for image formats of the future. A note to NEXTSTEP/OPENSTEP users: to my knowledge, the only way to correctly display SSS's PNG images is to make use of a ToyViewer 2.4+ / OmniWeb 2.1.1. combo, w/OmniWeb's own support for PNGs disabled. (To suppress OmniWeb's own support, "Open as Folder" OmniWeb.app, locate the subfolder "png.omniimage" within OmniWeb's app folder, and rename png.omniimage to, say, png.omniimage~ or alike.) Note that this apparently doesn't work with OmniWeb 2.5 -- for whatever reason. Blame the omni folks on this one. Maybe they can fix it in OmiWeb 2.6.
My own images seem to be destroyed! First of all, to display your converted GIF / PNG / JPEG images in its Image Conversion panel, LatinByrd needs help from an image filter app. ToyViewer 2.4 (or later) is strongly recommended. Further, if you can't see your converted images in your favorite browser -- blame your browser. (See the above FAQ for further explanation.)
LatinByrd's RTF conversion results suck! LatinByrd is tuned for NeXT's version of RTF. If you try to convert a document created with, say, M$Word, then the conversion will probably deliver poor results. That's because LatinByrd doesn't parse an RTF-document directly, but instead lets an object of the NEXTSTEP API's 'Text' class do the job. LatinByrd then takes that Text object apart, gathering all the necessary layout info from. So if an RTF document won't display good when opened with Edit.app, the conversion results won't display good, too. |
