This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
1Anneli
Zeitgeist has different language versions (Zeitgeist by language). This looks OK: Finnish site (fi.librarything.com), but the translation is impossible: suomi sivu (fi.librarything.com). It should be 'suomenkielinen sivu'. But I am not sure if I dare to change 'suomi' to 'suomenkielinen' because 'suomenkielinen' is adjective and it cannot be used as a name of the language (which is suomi). Is trial and error method only possible or is it possible to see beforehand, what happens if I change translation of a word?
2boekerij
>1 Anneli:
With the Dutch edition of LibraryThing -- www.librarything.nl -- we have been encountering that very same problem. A solution was to translate the "website" text snippet into "" (nil).
Thus, instead of having a language name adjective followed by a noun ("website"), the language name itself could be maintained and serve as a noun. In the latter case, no declination is needed--in Dutch, that is. You might use a similar solution in Finnish. I do not know whether "suomi (fi.librarything.com)" is acceptable and could be the solution that you want--in Finnish, that is.
Alas, some smart "corrector" that doesn't bother about cohorence, neither context, is and has been "correcting" the Dutch translation. He "corrected" the earlier "" translation into "Website", making for changing "Nederlands (www.librarything.nl)" into "Nederlands Website (www.librarything.nl)". The former was (is) correct. The latter is dubious at best. Worse, even if one would accept it, the "Nederlands" part cannot mean the language--i.e. : the present "corrected" translation is wrong indeed. The "corrector" doesn't bother. He seems to think this is fun. YMMV.
I do not know what we can do about some "corrector" who seems to have quite poor grammar, spelling and language skills, all of this apart from his many typos still, whose understanding of the target language is abominably poor and who seems not to understand very well the source language, either. The result of his "correcting" is disastrous indeed. He might as well be a trol. What can we do about this?
With the Dutch edition of LibraryThing -- www.librarything.nl -- we have been encountering that very same problem. A solution was to translate the "website" text snippet into "" (nil).
Thus, instead of having a language name adjective followed by a noun ("website"), the language name itself could be maintained and serve as a noun. In the latter case, no declination is needed--in Dutch, that is. You might use a similar solution in Finnish. I do not know whether "suomi (fi.librarything.com)" is acceptable and could be the solution that you want--in Finnish, that is.
Alas, some smart "corrector" that doesn't bother about cohorence, neither context, is and has been "correcting" the Dutch translation. He "corrected" the earlier "" translation into "Website", making for changing "Nederlands (www.librarything.nl)" into "Nederlands Website (www.librarything.nl)". The former was (is) correct. The latter is dubious at best. Worse, even if one would accept it, the "Nederlands" part cannot mean the language--i.e. : the present "corrected" translation is wrong indeed. The "corrector" doesn't bother. He seems to think this is fun. YMMV.
I do not know what we can do about some "corrector" who seems to have quite poor grammar, spelling and language skills, all of this apart from his many typos still, whose understanding of the target language is abominably poor and who seems not to understand very well the source language, either. The result of his "correcting" is disastrous indeed. He might as well be a trol. What can we do about this?
3Anneli
Thanks for the tip! It looks better without the "site". I just hope that the translation for "site" is not needed elsewhere. I wish there would be a note field in translation page, so it would be possible to put explanations and make notes.
4boekerij
>3 Anneli:
I haven't detected any other place use of that text snippet--"website", the one translated into "" (nil), that is--yet. You might take into account that I think that I have got quite a fair insight in the general and overall structure of LT--vis-à-vis different text snippets use, (too), that is. The latter is necessary, of caurse, if one wants to provide for a robust and consistent translation : context is vital.
Though sometimes a workaround is possible, as is the case with e.g. the "Your languagewebsite (URL)" example (see above), some problems are insolvable indeed--as yet, that is.
Take the next example as a test case :
Instruction : Please read aloud : "read".
Wrong !
Give it another try : "read".
Wrong again !
Out of context, you cannot know how you should read aloud "read", for you cannot know what is means. Though "read" and "read" are homographics--i.e. : their spellings are exactly the same--the one is an infinitive or a present tense conjugated form (IPA [ri:t]) and the other is a past participle or a past tense conjugated form (IPA [rEt]). You cannot know which one is which. There is no difference--in English language spelling, that is--though when read aloud, sound difference tells you whether it's either the former either the latter.
Is this example important ? It might be, for LT is using "read" as one single text snippet, using this homograph(s) in both different meanings, making it for a prominent intranslatable.
Does LT Staff know about this ?
They could and should, Methinks. Cf. i.a. LT Talk Translating LibraryThing? (General Talk) : read != read (Oct. 23, 2006). Yes, it has been brought at their attention more than seven months ago indeed, adding several reminders since. At no avail--yet.
I think this is a pity. It seems as if LT staff couldn't care less.
Then again, taking into account that atrol rough "corrector" has been playing old Harry with major part of the (former) Dutch language translation now, turning it into Double Dutch, considering that translation, some remaining instranslatables at LT's might 've become a minor problem indeed. Of course, this is quite a pity, too, Methinks.
One possible solution totrols rough "correctors" messing with and killing coherent translations, might be a call to make and loose non paying members the ability to edit translations--at least when dealing with (nearly) completed translations.
Many hundreds of correct and coherent translations that had been up for many months and that had been cheered multiple times, have been demolished and turned ("corrected") into crap now. He might think this is great fun. YMMV.
I haven't detected any other place use of that text snippet--"website", the one translated into "" (nil), that is--yet. You might take into account that I think that I have got quite a fair insight in the general and overall structure of LT--vis-à-vis different text snippets use, (too), that is. The latter is necessary, of caurse, if one wants to provide for a robust and consistent translation : context is vital.
Though sometimes a workaround is possible, as is the case with e.g. the "Your language
Take the next example as a test case :
Instruction : Please read aloud : "read".
Wrong !
Give it another try : "read".
Wrong again !
Out of context, you cannot know how you should read aloud "read", for you cannot know what is means. Though "read" and "read" are homographics--i.e. : their spellings are exactly the same--the one is an infinitive or a present tense conjugated form (IPA [ri:t]) and the other is a past participle or a past tense conjugated form (IPA [rEt]). You cannot know which one is which. There is no difference--in English language spelling, that is--though when read aloud, sound difference tells you whether it's either the former either the latter.
Is this example important ? It might be, for LT is using "read" as one single text snippet, using this homograph(s) in both different meanings, making it for a prominent intranslatable.
Does LT Staff know about this ?
They could and should, Methinks. Cf. i.a. LT Talk Translating LibraryThing? (General Talk) : read != read (Oct. 23, 2006). Yes, it has been brought at their attention more than seven months ago indeed, adding several reminders since. At no avail--yet.
I think this is a pity. It seems as if LT staff couldn't care less.
Then again, taking into account that a
One possible solution to
Many hundreds of correct and coherent translations that had been up for many months and that had been cheered multiple times, have been demolished and turned ("corrected") into crap now. He might think this is great fun. YMMV.
5royalhistorian
Well, the problem is that some of your translations were not understandable for Dutch people because it was Flemish, as can seen in this topic:
http://www.librarything.com/talktopic.php?topic=14239
Instead of polite communicating it turned in a total mess, even with accusing someone of trolling because you didn't get his translations. In every topic you brought up the 'poor state' of the Dutch translation, and a few weeks ago you even became sarcastic to one of the volunteers. You were very close to trolling.
Translating doens't work with having a go at each other and being sarcastic. That's why I wanted to communicate and discuss submissions for translation, so that everyone could give their opinion with arguments. I don't know much of the history of the Dutch translation group, because the atmosphere in the group wasn't quite good when I joined. After offering some opinions for translation I turned away of the group because of the bad atmosphere.
As I already said in the Dutch group, I hope we can put this kind of behaviour behind us.
http://www.librarything.com/talktopic.php?topic=14239
Instead of polite communicating it turned in a total mess, even with accusing someone of trolling because you didn't get his translations. In every topic you brought up the 'poor state' of the Dutch translation, and a few weeks ago you even became sarcastic to one of the volunteers. You were very close to trolling.
Translating doens't work with having a go at each other and being sarcastic. That's why I wanted to communicate and discuss submissions for translation, so that everyone could give their opinion with arguments. I don't know much of the history of the Dutch translation group, because the atmosphere in the group wasn't quite good when I joined. After offering some opinions for translation I turned away of the group because of the bad atmosphere.
As I already said in the Dutch group, I hope we can put this kind of behaviour behind us.
