You mean like I did with pidgin some time back nowdroope wrote:Nono, i think we are not understanding each other. The right move here, in order to have the possibility to translate it, is that the program itself does not contain the text, and that the text is kept in a separate .mo file.ttuuxxx wrote:For a full translation lets look at Glibc+Gcc they have a combined 11MB of bin files that don't compress really all that much, we would lose Gxine, abiword, Gnumeric because puppy goal has always been keep it under 100MB. We couldn't even use a full utf8 in English because of the bins would put us over the limit. What I've seen is a lot of community support for localizations and remastering of puppy just for that purpose:)
The most I could foresee in the future is the .desktop files being change. And if people want scripts changed, then if they give me the translations, I'll change the text? We are 4 mb under the 100MB threshold . But addition maybe sfs translation packs could be an idea. But we do need support from the other languages to translate. I've used online translation web pages before and they are really bad. I hope this helps, I'm not trying to stomp on anything, actually I'm trying to build some support so things like this might happen, but just in a way that follows puppy's main path. Well thats how I feel about it, Maybe not everyone.
ttuuxxx
Then, if more people like me are willing to have a fully translated puppy and work towards it, they will be able to translate it themselves (and changes won't be lost every version change!).
This is what i speak of:
http://www.murga-linux.com/puppy/viewtopic.php?t=26790
http://puppylinux.ca/tpp/ttuuxxx/progra ... 1-locales/
ttuuxxx