Opened 14 years ago
Closed 14 years ago
#253 closed defect (fixed)
translate sugar strings
Reported by: | tomeu | Owned by: | dfarning |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
Component: | activities.sugarlabs.org | Version: | Unspecified |
Severity: | Unspecified | Keywords: | |
Cc: | Distribution/OS: | Unspecified | |
Bug Status: | Unconfirmed |
Description
We have added some strings that are specific to sugar and need to be translated (including english). For example, main_prettyname_sugar -> Sugar
Change History (3)
comment:1 Changed 14 years ago by mick
comment:2 Changed 14 years ago by tomeu
I agree with starting with en_US, then perhaps we can add the .pot file to pootle like we do with the rest of the Sugar software?
There's the issue of synchronizing afterwards with translations from upstream.
Would be possible to have all the Sugar-specific strings in a separate .pot file?
comment:3 Changed 14 years ago by dfarning
- Resolution set to fixed
- Status changed from new to closed
The work flow is to make string changes in en_US and pootle and the build scripts will handle the rest.
Closing bug as it now not so much a bug as an ongoing effort.
Note: See
TracTickets for help on using
tickets.
What languages do we want to start off supporting? We can either start w/ only en_US or we can choose a subset of the listed languages or we can just try and get them all translated at once (I'd suggest against this).