Thanks, I just realised this myself at the time you were writing your reply ):

Edit: I just added an extra row in the table (had deleted many spam users)

Unable to fetch guest information. The table 'users' must contain an entry with id = 1 that represents anonymous users.

This is what I get when I try to access the forum...
http://www.kallia.gr/forum/index.php

3

(13 replies, posted in Feature requests)

I have sent to Rickard the tagged files I have created in order to make localization easier for potential translators who use translation memory tools like Trados, Wordfast, MetaTexis, DVX.

If they are not uploaded and anybody wants them just ask.

4

(13 replies, posted in Feature requests)

Hello,

I sent it to you, did you get it?

5

(13 replies, posted in Feature requests)

Just to let you know that the Greek localization is done. Please let me know an email to which I can send the final files.

You can see the first implementation at www.kallia.gr/forum (default language is English). Is there some sort of lang string to change language for guests?

6

(13 replies, posted in Feature requests)

Tobi,

This is not machine translation, it is CAT (Computer Assisted Translation) which means that there is no machine input but the program stores translation units (sentences), translated by a human, in a database and whenever there is a similar translation unit it comes up automatically.

7

(13 replies, posted in Feature requests)

Hello Toby,

Neither of you gets this completely because you have never used translators' tools like Trados and you do not know the methodology ):

These programs apply a style to untranslatable strings (which is visible but does not come up when one opens a translation unit). Thus, it is easy for the translator to focus on translatable text and create a translation memory of all translation units. This is helpful for two reasons: 1. If there is repetition or a partial match this is retrieved by the db. 2. It ensures terminology consistency as you have a concordance option.

In fact, sometimes what we don't know is not strange or absurd: we simply don't know it.

Anyway, I finally found a way:

1. Save files as txt or doc
2. Apply the following regexes in word (having checked the "Use wildcards" option) in order to select untranslatable text and hide it.

^13'*'*=\>*'
,^13
//*^13

The first one selects  this bit:
'Anytexthere'        =>    '

The second one selects  this bit (the end bit):
',

The third one selects  this bit (comment text):
// Anytexthere

8

(13 replies, posted in Feature requests)

Connorhd,

I know ):

This is not my first project of this type. However, this is not what I was asking.
I'll find a way to do it myself using regular expressions to hide the untranslatable bit.

9

(13 replies, posted in Feature requests)

Hello!

I would be happy to offer you Greek localization. However, I need your help. I use translation memory tools and I want you to help me "prepare" the files for localization.

What do I mean by "prepare"? It is simple, mark all the text which is not to be translated with a specific Word style (i.e. "Bold" would do, or simply as hidden text).

This means that when I use the translation memory tool only the translatable bits come up for translation, and the rest is hidden away.

I know that you have a couple localization tools out there but frankly, what one really needs is a tool which stores the translation and can retrieve similarities.

Moreover, please let me know which are the most important files (i.e. the frontend files) for prioritizing.