Translating variables it difficult and we shouldn't do, and i finaly don't know how we are able to solve this. project_issue_init_state (.install) function inserts the states in DB and this should be in english, but we need the strings also inside a t(). Should we put a dummy's variables for potx next to this lines? something like this:

// We add this unused line to get the strings in potx, don't remove.
translation_init_state = array(t('active'), t('fixed'), t('duplicate'), ...)

Or someone have a better idea?

Comments

hass’s picture

hass commented

ohhh - this list can be extended via admin/project/project-issue-status. This makes things more complicated... however - any idea?

dww’s picture

dww
we/he/they
commented
Title: project_issue_init_state not translatable » Allow translation of status names
Category: bug » task
Status: Active » Postponed

I think this should wait until after the initial D6 port, since D6 core provides (at least how I understand it) a lot of new tools for translating dynamic content on the site, not just static interface strings. This will be a big undertaking, and there are more urgent issues to solve in the short term. Plus, I'd rather start from a core API that (at least in theory, makes this easier). Hence, postponed.

aclight’s picture

aclight commented
Version: 5.x-2.x-dev » 6.x-1.x-dev
Status: Postponed » Active

Bumping version and setting back to active.

aclight’s picture

aclight commented
Issue tags: +6.x-1.0 wishlist

Adding 6.x-1.0 wishlist term.

@hass: I assume this is still a problem in the 6.x version of the module. If so, maybe you can provide insight into whether D6 makes this easier to fix, and/or a patch if it is relatively simple.

aclight’s picture

aclight commented

Adding 6.x-1.0 wishlist term.

@hass: I assume this is still a problem in the 6.x version of the module. If so, maybe you can provide insight into whether D6 makes this easier to fix, and/or a patch if it is relatively simple.