Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Call to help translate (now via GitHub)
Hi all.
I’m the former translator of the Spanish textpack. I find Github a very complex plattform, but I finally managed to send my first suggestions to the es-ES pack. A question: who validates the proposals and when do I know if proposals have been accepted?
Anyway, in the former RPC Server, when I entered the site I knew immediatly what where the tags that needed to be translated or updated (by comparison with English version). Is there some way of detecting that a particular textpack needs to be updated?
Cheers.
Offline
Re: Call to help translate (now via GitHub)
Hello Jose,
I’ve merged your pull request in GitHub and also updated the RPC server with these changes. I’ll eventually update the language contribution instructions on this forum (when the new forums go live) but in the meantime a couple of ways to track whether languages need updating:
- Keep a track of the history of the English (GB) file, since that is the default that all other Textpacks use as a base.
- Look at the Travis CI build message and see if your language has empty strings.
You can also ‘watch’ the GitHub repo, which will generate messages when any changes are made to the repo.
Offline
Re: Call to help translate (now via GitHub)
wet wrote #274633:
A hint:
mysql> select name, translate, last_access from txp_users where last_access > date_sub(now(), interval 1 year) order by last_access desc;...
Requesting an up-to-date output of this command to help with translation efforts, please. Thank you.
Offline
Re: Call to help translate (now via GitHub)
gaekwad wrote #292687:
Requesting an up-to-date output of this command to help with translation efforts, please.
Running that on the RPC server reveals… just me, Phil and Robert in the past year. And I’m only in the list because I just logged in to run the command!
Most people have been contributing on Github the past year, which explains it. But going back three years, this is what we have:
name translate last_access
Bloke en-gb,en-us 06/07/2015 22:02
philwareham en-gb,en-us 02/07/2015 20:58
wet de-de 29/09/2014 05:27
Pat64 fr-fr 11/02/2014 09:03
alexsander pt-br 07/02/2014 10:06
kees-b nl-nl 19/01/2014 19:38
pompilos es-es 17/01/2014 14:58
milosberka cs-cz 05/01/2014 12:19
nn-- ja-jp 18/12/2013 14:53
lll9p zh-cn 20/09/2013 04:40
beztak cs-cz 22/04/2013 08:20
gour hr-hr 16/03/2013 08:34
cbasilio pt-pt,pt-br 09/03/2013 10:43
giampablo it-it 23/01/2013 20:06
papuass lv-lv 13/12/2012 14:28
Natalya uk-ua 06/12/2012 07:01
els nl-nl 23/10/2012 23:27
sinacher fa-ir 15/09/2012 10:03
the_ghost ru-ru 10/09/2012 21:07
eg lt-lt 24/08/2012 08:48
elwins lv-lv 05/08/2012 11:13
arif id-id 04/08/2012 09:50
gerhard ro-ro 02/08/2012 09:57
playpiggy zh-cn 01/08/2012 02:25
anton sv-se 31/07/2012 21:05
tizrom he-il 31/07/2012 10:57
mamash cs-cz 31/07/2012 09:28
Dragondz ar-dz 17/07/2012 10:08The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Online
Re: Call to help translate (now via GitHub)
Thanks, Stef – appreciate it.
Offline
Re: Call to help translate (now via GitHub)
Bloke wrote #292691:
Most people have been contributing on Github the past year, which explains it.
I think Phil has locked logins to the RPC server back in 2014, which explains it even more ;)
Offline
Re: Call to help translate (now via GitHub)
wet wrote #292740:
I think Phil has locked logins to the RPC server back in 2014, which explains it even more ;)
Yep, I’ve locked everyone out of RPC so the GitHub repo and (untracked) RPC changes don’t fall out of sync.
It means more work for me as I have to then take the stuff from GitHub and replicate it in RPC – but at least I know its done correctly then. Also, RPC database still needs more cleanup which I continue from time to time. e.g. some languages have strings totally missing database entries, which I then fix.
Offline