Thanks Robert for this answer.

As you said, Fields names, Template names, Tag names will be a very good starting point.

I also understand the complexity to go at the folder level and I also do agree that this one can't be done right now.

However, for fields values, I was mainly looking a dropdown fields value managment. Laserfiche could be providing an interface to allow providing list values for each language. This new interface could maybe also be used to manage Dynamic Fields so users can have an interface to update database values.

This is something that has come up a few times.  If we were to do it, I don't think there would be server support, it would be Web Access translating entity names.  For the most part this would work ok since Web Access generally deals with object ids and not names.  There are a few places like advanced search strings, where users would need to use the "real" name of an entity and using one of these aliases would be an error; I don't know that there's an easy way to improve that case.

Hi Brian,

Can you please specify for which of the three request your comment will apply?

If you are thinking to use within WebAccess an external translator engine like Google/Bing/etc..., I don't think this will be a great solution for numerous reasons.

- Need to have the client and WebAccess to behave the same.

- Very often, translation will be poor and not be relating to the subject. If I am deploying in a laywer office, terms used will be very picky and the need to be the exact wording, so we can't rely on Google translation one day being this and another day being that.

Fields names and Dropdown values need to be controlled values.

These translation sites may be good to have an overall understanding of a text in another language but everyone that uses them regularly will absolutely say they are poor translation and can't be used officially in a document or in an interface. So I would not want to implement such solution officially to a Customer.

I'm open to suggestions and ideas but Translating sites doesn't seems to me to be an official solution.

Hi again Laserfiche development team,

If Laserfiche goes ahead with multi-Language fields support, I would like to bring to your attention one important thing to consider and has an effect in the Workflow and Forms.

When configuring a Template name and Template field name, there should be a way to setup a "default name" that will not change and then provide values for each languages "display names", including the English Display names.

In Forms and Workflow, all Templates token and Fields token are using the actual template or field name, and if there are any changes in these Templates/fields names, warnings are appearing and WF creators are invited to update these tokens.  I would like to see the Workflow and Forms to officially use something else than the Display Name in the tokens.  Could there be a "Purpose Name" associated to its ID that doesn't change, and then a "Display Name" for every languages?

This Hard Coded Template name or Field name should be set at creation time.  If a change is required in that hard coded name, then a special warning could be poping up to the administrator doing the change thatn Workflows and Forms may be affected.