Re: [w3c/manifest] multiple natural language text fields share language/direction [I18N] (#968)

> Yes, I looked at the proposal. If I understand correctly, the problem solved by that proposal is different from the problem to be solved in this issue. You can read my explanation for the miniapp folks in w3c/miniapp-manifest#12 (comment)

I totally understand where you're coming from. We talked a bit about string replacement previously, which is how I've handled translations in the past, but the main issue is that it breaks backwards compatibility. I've also gotten pushback on maintaining separate translation files, so I suspect that will be a hard sell too.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/968#issuecomment-964793941