Fwd: Re: Logisim Greek Translation

2 views
Skip to first unread message

Thanos Kakarountas

unread,
Feb 19, 2011, 7:53:08 PM2/19/11
to log...@googlegroups.com
And this is the reply of Ilia

I believe I get the concept, although I do not understand what Ilia
means for SVN-logisim/doc/en/html in 2.3 about the
omegat-logisim-doc_de. Wouldn't OmegaT handle everything about the
structure and the files after selecting "Create Translated Documents"?
Or should I create a file hierarchy using the appropriate svn subcommands?

Thanos

-------- Original Message --------
Subject: Re: Logisim Greek Translation
Date: Sat, 19 Feb 2011 14:54:05 +0300
From: Ilia Lilov <lil...@gmail.com>
To: kakar...@ieee.org

Good day, Thanos!

I'm very glad to see you again! My close friend have friends in Greece
and I know about very hard situation in your country. I hope situation
will come to normal and I wish you to be firm!

Translation process structure had changed since September and now it's
more easy: Carl wrote the script to do all the routine work related to
image links etc. I'm note sure which version of my translation guide
you had seen recent. You could try to visit this page:
http://circuit.svn.sourceforge.net/viewvc/circuit/trunk/xlate/guide/general-translation-guide.txt?view=log
and to choose two versions (the one you had seen recent and the
current one) for diffs, so you can see what's changed. Anyway you can
read current version:
http://circuit.svn.sourceforge.net/viewvc/circuit/trunk/xlate/guide/general-translation-guide.txt
It is up to date.
I know it is large document and it's boring to read it again, but I'm
sure you understand it's much more boring to type all the steps again.
:) Briefly: we still use OmegaT and it's even more handy now; you
shouldn't care about links to images within OmegaT now, so you should
open "File filters" preferences window in OmegaT and uncheck "src"
checkbox for HTML files; as of .properties files, it's more easy to
handle with them too now (read item 2.2 of translation guide). Also,
there are many minor changes and I can't remember them all, but they
all make our work more easy, not more hard.

Also, library structure had changed too, and it's reflected in
documentation of course. So some files added and some deleted. But you
don't have to worry about it: OmegaT will re-read new file structure
and will "remind" all the phrases you've already translated. Remember:
OmegaT stores translations for every text segment separately and
substitutes translation when finds the same original segment anywhere.
So, just reopen your OmegaT project, translate, and don't worry about
anything! When you will finish, upload results to SVN. It's very
probably you will make some little mistakes with file structure within
SVN repository; don't worry, I'll fix them all.

File legacy.properties doesn't exist anymore; as of data.properties, I
don't know which unrecognized characters are there. In case you mean
three whats... they are just three whats!

We use our Google group mailing list for all the discussion, so it
would be OK to post your letter there. It's very good when Carl keeps
abreast of anything! If you aren't against it, please repost you
letter and this mine one to the mailing list.

If you have any additional questions, please ask. And it's normal to
do that in mailing list. Evermore, it's not OK to do that outside
mailing list. :)

Ilia.


Reply all
Reply to author
Forward
0 new messages