Digital Workshop

Hi,
I am working on a multi language project. To make the interface in different languages i
made a variable for every caption.
I did a test using a set variable that holds all the caption text per variable, and i made
an .ini file that holds the text. Both are working fine but what's the best way?

Is it the .ini file so i can easely change the text, even when the project is finished, or is a
set variable a better way.
Like to hear from one of you experts soon.

Linda

Well, I am no expert TBS (to be sure). But I have given this some thought. I plan on using a DB anyway, and will have large amount of text content. So that is an approach that is good for me and my translators.

However, if you have just 'captions', I would begin thinking that an Excel spreadsheet would be an easy way to maintain translations. Opus does not care where you store the "variations" of content segments.

For example, you could use MultiFrame objects. If the language the User chooses to begin with is Italian... simply always point to Index 3 for Italian. (assuming that is how you set it up). To come back to your main question, a variable for every caption... that seems way too complicated. But you could MAKE SETS of captions -- and I think you sort-of point to this (regarding INI files), but there is not enough information to know exactly what you have already, nor how to SCOPE the project.

Morning Danklof,

If the publication is for Windows Client, not SWF / Web, then my first choice would be INI.

Mack