multilanguage advice: p.a.m or multilanguagefields?

We're building a site that should have very basic multilingual functionality:

* Title and Description should be translatable.
  - This is about custom content types (DT) and Plone's dexterity content types.
  - All other fields are language-independent.
  - Content types may contain Images, which should also not be translated.
* Pages should be translated. (There are not many of these, <10, all
in site root)
* Currently we have 3 languages, later others may be added.

>From the start we were not sure if plone.app.multilingual is a good
solution for this. Will it be possible to mark the Images as not
needing translation? Won't it be an overly complex solution?

We were considering an approach where we create extra fields for the
Title and Description in the desired language, but we might want to
roll out the product to other customers with different selectable
languages.

We are now considering creating a simple dexterity version of
raptus.multilinguagefields.

Can anyone suggest a good reason to use p.a.m? Anyone interested in a
DT version of multilanguagefields? Other thoughts?

Kees

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk