Open pibinko opened 10 years ago
I think one aspect would be to adopt convention of adding columns with original name + @{lang-id} e.g. title@fr for french title. We could then choose to display french version. For start and end you would not bother .
Assume I have a multilingual site (my typical case is Italian and English).
If have have a listing of events I would like to "timemap", I would need multiple languages for
title end Description web page media caption media credit tags
I would avoid automated translations, and would maintain translations for the records.
an option is to have two parallel sheets, and generate two separate timemaps (or one per each language, in general).
I am wondering if there could be a more elegant way to optimize the management of such information (i.e. avoid the duplication of information for the columns which are language-independent: start, end, place, location).
an example I can think of is to maintain a master sheet with the two languages, and then have some script to generate separate sheets.
note: I would figure that once the direct support for raw CSV/JSON discussed on the issue, this whole issue could be simplified, as the source CSV/JSON could be generated more easily from a master table with all the required language sources..