From now on translation should be handled through the Translation
Project (http://translationproject.org). Yes, I know some like this, and
some disagree. But this is simplest for me. I have to spend my time on
the development of Solfege where I feel it is most important. And that
is python programming and testing. There are still far too many bugs,
especially related to MS Windows and unicode.

So visit http://translationproject.org and see how things should be done
if you want to translate solfege. Don't try to submit the directly to
me, as I will be kicked out of the Translation Project if I continue
with my previous chaos related to translation.

I uploaded Solfege 3.8.3 a few minutes ago. You will notice there is
only a source code tarball this time. That is because the release is
made mostly to sync my bzr repo and the Translation Project.  Wait for
3.9.3 if you want new bugs to discover.

-- 
Tom Cato Amundsen <[EMAIL PROTECTED]>                 http://www.solfege.org/
GNU Solfege - free ear training    http://www.gnu.org/software/solfege/

Attachment: signature.asc
Description: Digital signature

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Solfege-devel mailing list
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe", or visit
https://lists.sourceforge.net/lists/listinfo/solfege-devel

Reply via email to