[bug 398] Discussion thread for bug 398

[denise]

This is the discussion thread for bug 398: Hash out golive process as it relates to translation items.

Let's build a spec here so we can get this fixed up ASAP.

Comments

[pauamma]

Main problem I see with this is the following scenario:
- en text says "You can't have sparkly ponies"
- en_DW text says "You can't have sparkly ponies, unless you have a Very 'Spensive Account" (because sparkly ponies are dw-nonfree)
- en_DW_live text says "You can't have sparkly ponies, unless you haver a <a href="http://www.dreamwidth.org/support/faqbrowse.bml?faqid=23">Very 'Spensive Account</a>" (with the FAQ telling something about Very 'Spensive Accounts)

When we try to push this back to the repo, it's hard to tell automatically whether the change should be pushed to en_DW or en. (The standard case where the text only exists in en or in en_DW is easy - just push it back there.)

However, that sounds like a minor problem, and one that we can tackle later.

[mark]

The database has all strings, so we would write them out to en.dat, en_DW.dat, and en_DW_live.dat.

Do you see any problem with that?

[pauamma]

Mainly, that IMO there shouldn't be an en_DW_live.dat, or at least only as a staging area. Strings in that language in the DB should eventually be merged into either en.dat or en_DW.dat in the source repos. When the string exists in only one, thjat's easy. But when (as in this example) it's present in both, it needs some way (possibly manual input) to decide whether the string should go to en.dat, en_DW.dat, both, or neither.