Hi,

As this is a credo of drupal 6, I think it could be good to put this module multilanguage (support of i18n which will be core soon I think).

As recipe is a content type, it is possible to translate all different field content with i18n but ingredients are not translatable so why not do this ?

zmove

Comments

reallyclueless’s picture

I too would love this. Maybe have an option to have the recipes (with description, ingredients etc) in two languages: one English for example and the other Italian. This way we target people from both countries.

reallyclueless’s picture

I too would love this. Maybe have an option to have the recipes (with description, ingredients etc) in two languages: one English for example and the other Italian. This way we target people from both countries.

2222a’s picture

me too!!! Hands down a great idea.

zmove’s picture

I'm getting some news about that. I tested the last 1.0 for drupal 5.x and it seems ingredients are not i18n friendly. Is there a patch to make them available ?

robertdouglass’s picture

Component: Miscellaneous » Code
Category: feature » bug

Is this an issue of the strings in the module not having t() wrappers? What's the technical issue here?

samchok’s picture

Similar translation problem with version 6.x-1.0-beta1: I can't find a way to translate the dropdown ingredient's units list (gram, kilogram, pound...).
I don't know if it is a missing t() wrapper because I have no idea where those strings are stored.

scottprive’s picture

Version: 5.x-1.x-dev » master

Ingredients and measurements are both referenced by numeric IDs... you could easily intercept those and point them at different localized terms.
Sorry, I don't know a lot about i18n and localization in Drupal yet, but I know that nothing is really hard coded in a way that makes things difficult.

scottprive’s picture

Category: bug » feature
scottprive’s picture

Title: internationalization » i18n: Ingredients not easily translatable
jvandervort’s picture

Version: master » 6.x-1.x-dev
dcam’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Closing old 6.x issues.