Grimm wrote:I've uploaded unident.txt as a straight .txt file from the offline tiles package. It looks clean and easily translatable in Transifex's interface.
Cool, thanks! I've played around with it, and you're right. This does work rather smoothly. I don't like how sentences are split into chunks at the end of each line, for which it might not make sense to translate them separetely. Also, the translations are highly unlikely to reach the line end at the same word. Not sure what to do about that.
In general, we'll need to decide how to deal with look-up words/phrases. Whether terms like "potion" or "deck of cards" are translated in the look-up section of each description or not, either way we'll need a separate file containing translatings for these terms themselves. Actually, it might be easier to define clear keywords for each look-up term (e.g. ITEM_POTION, ITEM_DECK_OF_CARDS) and use those everywhere the item is referenced including the code. That way, English too would get a file listing the proper names for each item.
Also, for the credits file, it strikes me as overkill to start a new translation for every new version, even though the header and footer never change. With that in mind, it might be worthwhile to split those out into separate files, translate these as necessary, and have some kind of script cobble them together for the final file. The same applies to e.g. the aptitudes table.
In general, keeping translations of documentation files that get updated regularly might be tricky. Transifex is supposed to have a translation memory, but we'll have to try out and see how that works when a whole new file gets uploaded that only had a couple of sentences changed.