what about strings that are not for the user?
like wallet backup / send by mail
that a joe average use will never see
translate those as well?
Topic: [PAID] 100 BTC bounty : Localize Bitcoin-Central.net - page 3. (Read 11713 times)
do you need an italian translator? if you give me the english strings i'll translate them for a donation (different thing if i have to dirty my hands with code)
That's nice of you!I'll let you know when the string extraction part is done so you just have to translate some strings in a file.
do you need an italian translator? if you give me the english strings i'll translate them for a donation (different thing if i have to dirty my hands with code)
-MarkM-
to to github.com, grab a copy of davout/bicoin-exchange/
and start digging around the .ruby files
- creating a XY locale file
- making corresponding changes in the code.
please do that. get your hands dirty with the code and then maybe reflect how could you contribute.
automated capitalizing of text may break the code (you change machine readable instructions, p.ex.)
nor automake it green and blink is an improvement.
Your username is there, so you don't need to sign your posts
They can be made to be green blinking text if they have been successfully converted to the translation system
Sure, but two things, the 
It is simple to mechanically at computer speed change strings in ways that are very easy for a human looking at the site to see that they have been changed.
They can be made to be green blinking text if they have been successfully converted to the translation system, for example.
That might well be much easier to look at and see it has been done to all the strings than looking at simply translations from one human language to another.
-MarkM-
They can be made to be green blinking text if they have been successfully converted to the translation system, for example.
That might well be much easier to look at and see it has been done to all the strings than looking at simply translations from one human language to another.
-MarkM-
how to distinguish a missed/untreated string: really really JIVE jive piratejive otherjive superjive
Not to mention sed -e 's/^/I DID THIS ONE ALREADY>/'
-MarkM- (Or 's/^//' if its htlm strings...)
wtf? Not to mention sed -e 's/^/I DID THIS ONE ALREADY>/'
-MarkM- (Or 's/^//' if its htlm strings...)
how to distinguish a missed/untreated string: really really JIVE jive piratejive otherjive superjive
Not to mention sed -e 's/^/I DID THIS ONE ALREADY>/'
-MarkM- (Or 's/^//' if its htlm strings...)
Not to mention sed -e 's/^/I DID THIS ONE ALREADY>/'
-MarkM- (Or 's/^//' if its htlm strings...)
I only know English and computer-languages, but I have filters that "translate" English into various "jive" type "dialects" would they suffice or would it be better to break out (separate) implementing the yaml/translation (localisation) facilities from actually nonmechanically-translating into some actual non-English language? I can grammar and typo fix (proofread) English along the way of course.
-MarkM-
-MarkM-
i think the main task is to review the whole code and replace plain english strings with references to the localisation file.
so the fact that you speak only english might be a problem while reviewing your own work (how to distinguish a missed/untreated string from a string localized to english?)
this is the reason why the first translation is most difficult. other people just take the finished string list and translate all the text in one place.
proofreading is easier as well when all there's need to be done is to review a single file with all the text (and maybe compare with the web site in use). but again the localization file is the place where to fix typos, so it should be done first.
p.s. the items to translate are pretty everywhere in the code. proofreading now would be difficult
I think chmod755 has started something, it would be nice if he could confirm here
I only know English and computer-languages, but I have filters that "translate" English into various "jive" type "dialects" would they suffice or would it be better to break out (separate) implementing the yaml/translation (localisation) facilities from actually nonmechanically-translating into some actual non-English language? I can grammar and typo fix (proofread) English along the way of course.
-MarkM-
-MarkM-
Hey! Thanks a lot for the complementary explanations!
I still need to setup the staging enviroment
2) check that you set your locale to a different lang than english (p.ex. i use 'slovak SK')
For this, just add ?locale=XX at the end of any URL5) be fast & start localizing on the latest code revision
Or use git rebase PS the bitcoin donation address in page footer should not be localized 
LOLI'm probably free for quality assurance questions and answers and probably testing as well.
That would be awesome!I still need to setup the staging enviroment
& how to test:
1) start your local copy of bitcoin-exchange
2) check that you set your locale to a different lang than english (p.ex. i use 'slovak SK')
3) check all pages if you did not miss any string to extract, if you localize the logo extra kudos
List of pages to check
- register, login
- all account menu links (balance, history, transfer money, deposit money)
- all trade menu links (new order, your orders, order book, trade history)
- help menu entries ...
=> you're halfway done
4) now perform some actions 2 times (once to see OK result and second time to force FAIL results)
- create valid trade orders
- create trade order with amount smaller than 1
- create dark pool trade order for amount smaller than 3000
- try to transfer EUR to bitcoin address
- i must have missed some test cases here ;-)
=> you're almost done
5) be fast & start localizing on the latest code revision
PS the bitcoin donation address in page footer should not be localized
I'm probably free for quality assurance questions and answers and probably testing as well.
1) start your local copy of bitcoin-exchange
2) check that you set your locale to a different lang than english (p.ex. i use 'slovak SK')
3) check all pages if you did not miss any string to extract, if you localize the logo extra kudos
List of pages to check
- register, login
- all account menu links (balance, history, transfer money, deposit money)
- all trade menu links (new order, your orders, order book, trade history)
- help menu entries ...
=> you're halfway done
4) now perform some actions 2 times (once to see OK result and second time to force FAIL results)
- create valid trade orders
- create trade order with amount smaller than 1
- create dark pool trade order for amount smaller than 3000
- try to transfer EUR to bitcoin address
- i must have missed some test cases here ;-)
=> you're almost done
5) be fast & start localizing on the latest code revision
PS the bitcoin donation address in page footer should not be localized
I'm probably free for quality assurance questions and answers and probably testing as well.
Hello all!
I'm putting a 100 BTC bounty for some translation and localization work.
What does it involve ?
- installing rails on your machine,
- check that the bitcoin central code works correctly,
- extract all strings into an english yaml dictionary,
- translate it into a language of your liking (i'd prefer russian, german, or chinese but the main goal is to make it easily translatable)
Do I need to know Ruby/Rails ?
- No, however, without knowledge of HTML it'll be hard for you
How much work does that represent ?
- Probably 3 to 4 hours work.
Since code is usually better than explanations I've commited an example which shows how it basically goes.
I'm putting a 100 BTC bounty for some translation and localization work.
What does it involve ?
- installing rails on your machine,
- check that the bitcoin central code works correctly,
- extract all strings into an english yaml dictionary,
- translate it into a language of your liking (i'd prefer russian, german, or chinese but the main goal is to make it easily translatable)
Do I need to know Ruby/Rails ?
- No, however, without knowledge of HTML it'll be hard for you
How much work does that represent ?
- Probably 3 to 4 hours work.
Since code is usually better than explanations I've commited an example which shows how it basically goes.
Jump to: