Closed ecmendenhall closed 7 years ago
Hi @mouse-reeve! I think this approach to automatic trial data is a plus for maintainability. This will undo trial data modifications in favor of using config to switch lang and constraints. For all main Mastodon trials, it will run with lang en
and no constraints, but for Oulipo trials, it will run with lang en-OU
and our constraints. It won't be as painful to pull in stuff from Mastodon's main branch. It's also a foothold for additional Oulipo translations—de-OU
, fr-OU
, &c. i18n config could possibly hold "invalid glyph" configuration lang-by-lang, too!
(This is a branch-off-a-branch, so DNM right now! Just want to ask your opinion on this approach!)
I think this is a good plan, both for conflicts and for maintainability
OK, @mouse-reeve, I think this is all good to go! It will also fix #38. I put a handful of thoughts down in this diff for you. Look at this in particular: https://github.com/mouse-reeve/mastodon/pull/34/files#r113320587
*n-OU
locality for both Rails and JS. (This can possibly work for other langs too!)Oulipo.fifth_glyph_r*g*x
, not constantOulipo::Config
to swap invalid symbols according to config