- Issue created by @Jose Reyero
- πͺπΈSpain Jose Reyero
Just to get started, let's extract the recipe.yml translatable strings.
- ππΊHungary GΓ‘bor Hojtsy Hungary
I think this is a reasonable start, however we still need the config action strings extracted, when they are translatable things. We don't have reasonable outside sources to verify which are those, so that needs explicit YAML markup I think. Maybe that could be a followup.
What would be good here is a test that has a recipe and proves these work. The text could include config shipped with the recipe and a test that ensures that is parsed too. Which should already work? (Famous last words? :D)
- πΊπΈUnited States phenaproxima Massachusetts
I agree that tagging particular YAML strings as translatable is follow-up material.
- ππΊHungary GΓ‘bor Hojtsy Hungary
Opened π [PP-1] Parse recipe packages and make available on localization server Postponed for l.d.o integration and marked postponed on this as first we need to make sure we have a tested way for potx to parse recipes packages before we unleash l.d.o on them :)