From doing internationalization work on acs-lang:
This suggestion is inspired by a feature in Greenpeace's
localization UI that supports localization of images (for e.g. for
images holding text). The Greenpeace code figures out whether a
given key is an image url by checking whether the image exists in
the file system.
A better way to do this would be to have a way to store
additional information about the messages' format in the catalog.
Since the information would be the same regardless of locale it
would have to go to a 'father table' keyed only by key and package
for the db to normalised. The sort of 'metadata' could be:
- whether the message string is actual data or an url reference to
some data
- what type of data it is (mime type?)
- whether this should go through the adp-parser or not
The usefullness of letting translated material go through the adp-
parser would be that it made it possible to translate text that was
part dynamically generated content and in some languages had swapped
the order of the words. Like:
- english: Christian's apple
- french: la pomme de Christian
where 'Christian' and 'apple' are dynamically created.
Any comments?
