===============================
Epoz Frequently Asked Questions
===============================

* Will this work with Safari or Opera or ...?

  No, Epoz will only run on browsers with the IE engine (IE 5.5+) or those
  with a Gecko engine (Mozilla 1.3.1+ and Netscape 7.0+), not on the 
  Konqueror one (which Safari uses) or on Opera or any other browser. 
  Actually Mozilla copied a feature unique to Internet Explorer, which is 
  not part of any standard, which Epoz uses. Because it's not part of a
  standard, it is not very likely any other browsers will implement it,
  although we keep hoping some day they will.

* Epoz allows users to do all kinds of things - like coloring text -
  that I don't want in my system.

  All of the epoz style functions can be turned on and off using CSS or in 
  the configuration. Additionally, the element controls can be extended to
  accomodate special needs of your content.

* Is my platform supported?

  It probably is: Epoz has requirements on the client side, but works with
  just about any web server. As long as your server supports POST and some
  server-side scripting language or CGI (to process form variables if Epoz
  is part of a form) or HTTP PUT you can install Epoz on your website or
  application.

* Why do I get all kinds of weird characters?

  Epoz seems to work correctly when you use UTF-8 as the character set for
  encoding, but gives unpredictable results when you use another one such
  as latin-1 (ISO-8859-1). Make sure to always use UTF-8 as the character
  set for incoming data and set the correct Content-Type header or meta-tag,
  and Epoz will send back UTF-8 data.

* Saving seems to work, but my browser keeps showing old stuff

  Browsers tend to store web pages a while to reduce the amount of data that
  has to be transferred. Obviously this can get in the way when using Epoz,
  so the browsers need to be told not to store (cache) the Epoz iframe contents
  on retrieval. This can be done either with HTTP headers or with meta-tags.
  For an example of which meta-tags to use, see fulldoc.html (the example
  content page).

* Can I really open the files straight off the file system?

  At least the files in the 'common' layer are supposed to work this
  way. The epoz.html and epozmacros.html pages (the first is usually a
  copy of the first one, stripped from all TAL (see below)).

* What is all this gibberish in epozmacros.html?

  This is TAL, Template Attribute Language, one way of server-side generation
  of HTML in Zope. Since Epoz was originally Zope based (does it show?) you
  will find some Zope specific stuff here and there in the product. The idea
  is to move all that to a Zope specific one, but the epozmacros.html is still
  used as the base file to test implementations and such, and will therefore
  not be moved until now.
  Note that this does *not* mean that Epoz runs only on Zope! (see above)

* File extensions look different in Zope!

  In fact, they look normal. Thanks to CMF 1.4, we can use .js, .html,
  and friends as file extensions.

* Does Epoz produce valid XHTML?

  Well... Epoz produces *well-formed XML*, which out-of-the-box does not 
  contain any elements that aren't allowed in XHTML anymore, and are written 
  in a form compliant to the XHTML notation (lowercase tag and attribute 
  names, attributes all have values and all values are in quotes) but it is
  theoretically possible to create constructions that are not valid according
  to the XHTML DTD. For most cases, however, the data produced by Epoz is
  perfectly usable, even after copied from another website or notorious Word.

* What about i18n?

  Currently Epoz is not adapted to i18n. The plan is to write i18n support for
  the JavaScript sources in one of the next versions (probably using XML 
  inside the HTML, so-called 'XML data islands', to store all the JavaScript 
  strings) but currently it's not possible to convert the JavaScript strings 
  on the server without having to hack in the sources.
  Note that even when the JavaScript strings are in the HTML, it is unlikely
  that Epoz will ever provide a working i18n implementation. The variety of 
  webservers it will run on is too large to have any dependencies there. 
  By getting all strings in one single point it will however *allow* 
  internationalization and it will probably at some point provide XML mappings 
  for different languages as well. Actual implementation is then up to the 
  integrators (although platform specific i18n code may end up in the platform 
  specific directories later).

* What about Bitflux, Xopus, and others?

  The authors of these editors have done great work. They are superb
  applications, but the major drawback is they work in only one browser (as of 
  this writing). Epoz was created to work in both Mozilla/Netscape and Internet 
  Explorer.
  
Other questions
---------------
Additional questions for the FAQ are welcome. Please post them on:
epoz-development@lists.sourceforge.net.