LiloSetup development needs testing (and translating)
Re: LiloSetup development needs testing (and translating)
You're very welcome
Re: LiloSetup development needs testing (and translating)
Do Salix OS only use Trac, or do we also use git, svn or bzr? Because if we only use Trac I think we're stucked with the way we do translations now
Re: LiloSetup development needs testing (and translating)
Sorry, forget about that. I can see that Salix now have a Transifex-account
https://www.transifex.net/projects/p/salix/
https://www.transifex.net/projects/p/salixtools-gtk/
gapan - I think it will be easier, if you just collect the to projects in "salix" That's how other projects do it
EDIT:
And we should only call the new translated files for "da.po" or "fr.po" and so on - because, then Transifex can associate the language code with a language. Much easier
https://www.transifex.net/projects/p/salix/
https://www.transifex.net/projects/p/salixtools-gtk/
gapan - I think it will be easier, if you just collect the to projects in "salix" That's how other projects do it
EDIT:
And we should only call the new translated files for "da.po" or "fr.po" and so on - because, then Transifex can associate the language code with a language. Much easier
Re: LiloSetup development needs testing (and translating)
We're in the process of restructuring our project there, it's not going to stay the way it is now, wait until we announce it.Kristho wrote:Sorry, forget about that. I can see that Salix now have a Transifex-account
https://www.transifex.net/projects/p/salix/
https://www.transifex.net/projects/p/salixtools-gtk/
gapan - I think it will be easier, if you just collect the to projects in "salix" That's how other projects do it
EDIT:
And we should only call the new translated files for "da.po" or "fr.po" and so on - because, then Transifex can associate the language code with a language. Much easier
Re: LiloSetup development needs testing (and translating)
Cool with me
Contact me if you want some help.
Contact me if you want some help.