April 28, 2008
Multi-lingual? Why not help translate ScribeFire?
Filed under: Development, ScribeFire -- Christopher Finke @ 08:16amDo you know more than one language? Why not help us translate ScribeFire into as many languages as possible?
There are about 400 words/phrases that make up a full translation, but you don't have to translate all of them yourself. Multiple translators can work on a translation, and any phrases you don't translate will still appear in English.
If you want to help out, just sign up at Babelzilla, select a language, and start translating!
April 29th, 2008 at 6:25 am
For es_ES locale, should I use this way or can I continue using Google Code?
April 29th, 2008 at 6:37 am
Hi Chris:
Now I have used Babelzilla I must say it´s much easier to translate this way.
I have reviewed es_ES locale and it has been very easy to find the few phrases left.
Only one thing:
overlay.properties says 124 of 97 Strings translated = 128 %
and
overlay.dtd says 413 of 309 Strings translated = 134 %
¿???
contents.rdf says when trying an edition: Sorry, but it's not possible to edit this file online.
April 29th, 2008 at 8:46 am
For pt-BR:
I have translated all the strings on overlay.dtd and overlay.properties, but some of the strings didn't was showed as for my locale, but as in en-US ("Draft" checkbox, the "Example Notes", "Modify Timestamp", "Promote" tabs ans some info, and some "Settings"). Any idea of what's happening?
April 29th, 2008 at 10:06 am
When I translated ScribeFire to es_ES I had to insert some lines from us_US overlay files and then translate the phrase. Maybe pt_BR locale lacks some lines in those files. So, download both locales and insert the lines needed. Finally you can upload your locale. I think this will be OK as it was in Google Code.
April 29th, 2008 at 10:57 am
Enrique: The reason you're seeing percents greater than 100% is because there are some strings leftover in Spanish that have since been removed from the English locale files, as they are not used anymore. Nothing to be concerned about.
And contents.rdf doesn't have any strings in it for translating, it just identifies what files are in the locale.
April 29th, 2008 at 10:59 am
Fabio: I'm not sure why you're not seeing those lines in your locale. I'll upload the very latest version of ScribeFire to Babelzilla today to see if that fixes it.
April 29th, 2008 at 12:14 pm
Hi folks!
I'd like to know if it's possible to use Scribefire from OmeaReader... there's an option 'BlogThis' in their software, but I can't find the .dll to configure it... can u help me?
Cya!
April 30th, 2008 at 2:52 am
OK, Chris.
Now es_ES locale is 100% translated.
May 5th, 2008 at 3:38 pm
Sorry about this, but you really owe the users a complete set of documentation before you begin haring off in directions like this. It is just about impossible to get a complete understanding of ScribeFire from your site, much less a guide to maximizine its usefulness. Beyond that, if you run into trouble, you are most definitely on your own. For example, you claim to be compatible with WordPress, and even use it here, but myself and others have had trouble publishing to WordPress blogs for no apparent reason.
Give us all a break and publish a manual, or hire me to do it.
May 6th, 2008 at 9:43 pm
James: We've started a help section at http://www.scribefire.com/help/ and we offer support via a bug tracking system: http://code.google.com/p/scribefire/issues/list
And a few possible solutions have been raised for the problem with signing into Wordpress here: http://code.google.com/p/scribefire/issues/detail?id=8
May 10th, 2008 at 3:20 am
Hi.
I know there is a Japanese version of ScribeFire.
here:http://repse.blogspot.com/2008/05/scribefire-210-with-japanese-language.html