| *** freeflying is now known as freeflying|out | |
| *** nalioth is now known as nalioth_zZz | |
| *** otep[zzz] is now known as otep | |
| *** seth_k is now known as seth_k|away | |
| *** nmsa_away is now known as nmsa | |
| *** bojan is now known as bojan_na_rucku | |
| *** bojan_na_rucku is now known as bojan | |
| *** \sh_away is now known as \sh | |
| *** SloMoSnail is now known as slomo | |
| <nomed> hi all | |
| <nomed> i trying to find infos about how to make an app translatable | |
| <nomed> i know this is offtopic here but i asked averywhere and nobody can tell me something clear | |
| <nomed> mainly this app uses a glade file whici i can translate .. and *py files from where i can get the strings to translate but i can't get them translated | |
| <nomed> i need a tut about how to solve these problems | |
| <nomed> any suggestions ? | |
| <hunger_> nomed: I think googleing for gettext might be a good idea. | |
| <nomed> hunger_, yes i found some materials | |
| <hunger_> nomed: IIRC that is what is used in C and there should be ports to other languages. | |
| <hunger_> nomed. I never used any of that, so I might be off completly:-) | |
| <nomed> it would be nice to find even an app that uses *.py files a glade files and a po dir | |
| <nomed> as sample | |
| <nomed> i can't figure out how to define the paths within the po file | |
| <hunger_> nomed: You read http://docs.python.org/lib/module-gettext.html ? | |
| <nomed> yes | |
| <nomed> hunger_, think that in that doc they suggest to use pygttext ... | |
| <nomed> it could be deprecated that method .. | |
| <hunger_> nomed: Yeap. that should generate the po files for you IIRC. | |
| <hunger_> s/.po/.pot/ | |
| <nomed> i can generate the message.pot ... | |
| <nomed> but i can't get translations | |
| <hunger_> nomed: Somebody needs to do them for you:-) | |
| <hunger_> nomed: They do not appear automatically:-) | |
| <nomed> hunger_, well from en to it i can :) | |
| <hunger_> nomed: Grab a translation tool then and create some italiean po file from the .pot. | |
| <nomed> hunger_, i did it | |
| <nomed> and i get just glade strings translated | |
| <nomed> not the ones within *.py files | |
| <hunger_> nomed: You used the pysomething file to generate the .pot file? | |
| <nomed> i used both pygettext and xgettext | |
| <hunger_> nomed: You marked all the translateable python code with _("translate me")? | |
| <nomed> yes | |
| <hunger_> Hmmm... then I can not help:-( | |
| <hunger_> Sorry. | |
| <nomed> infact i can translate using gtranslator .. but i don't see then the strings translated when i run the gui | |
| <hunger_> nomed: So the strings are in the .pot? | |
| <nomed> yes all | |
| <hunger_> nomed: That sounds really strange to me:-( | |
| <nomed> i would know if it's important the way i define paths within the pot file | |
| <nomed> well mainly i need a step by step tut that clarify all this to me | |
| <nomed> tut == tutorial ... not a tutor .. a nice link would be perfect :) | |
| *** \sh is now known as \sh_away | |
| *** \sh_away is now known as \sh_away_away | |
| *** \sh_away_away is now known as \sh_away | |
| *** \sh_away is now known as \sh | |
| *** nalioth_zZz is now known as noirequus | |
| *** seth_k|away is now known as seth_k | |
| *** noirequus is now known as nalioth | |
| *** lllmanulll is now known as lllmanulll|plouf | |
| *** \sh is now known as \sh_away |