On 18 November 2010 22:58, Adam Borowski <kilob...@angband.pl> wrote:
> On Thu, Nov 18, 2010 at 03:14:33PM +0100, Johanna Ploog wrote:
>> On 16 November 2010 16:54, Adam Borowski <kilob...@angband.pl> wrote:
>> > On Sun, Nov 14, 2010 at 02:11:41PM +0100, Xavier R wrote:
>> >> Also, I want to translate DCSS in french (a huge work, I know, but im
>> >> ready
>> >> :] )
>> >> is this possible/viable/cool/etc... ?
>>
>> Since you're not going to be the only one with that question, he
>> pretty much said that the question comes up a lot (lately, that is),
>
> I think I'll better edit the reponse I posted here and put in onto the wiki,
> so there's no need to write that over and over.
Yes, that's a very good idea. I actually thought of that as soon as I
was out on the street. :)
This has been discussed before but your reply has been the best
explanation I've seen yet.
>> > After coming up with such a syntax, the biggest part would be going through
>> > all the source and replacing all strings this way. If marked in a
>> > consistent way (like, _("foo") as gettext uses), we would be able to run
>> > some automated tool and gather a list of messages that do need to be
>> > translated.
>>
>> I think Patric Mueller did something similar for NetHack-De: first
>> running a script that found all messages (presumably by looking for
>> quotation marks) and added a predefined marker in that line (in this
>> case "TODO DE").
>> Later, it was easy to grep the source for untranslated (or
>> half-translated) fragments and translate the messages one line at a
>> time.
>
> Unfortunately, that way requires having a distinct source tree for every
> language. This is a nightmare. Doing this in a gettext-like way would be
> so much better - translations are totally independent from the source, and
> you can code as if there weren't any.
Ah, sorry. Being rather in a hurry, I skipped the important part where
I meant to say that in this case the marker obviously should NOT be
language specific (I agree that would be a nightmare) but instead
should simply point out strings that need to be replaced by
translation shorthands (I think that's your term). This might very
well be what you mean by the _("foo") markup, in which case I entirely
agree. The gettext solution sounds good, I simply wasn't aware that it
existed. I'm sorry about any confusion this might have caused.
Johanna
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Crawl-ref-discuss mailing list
Crawl-ref-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crawl-ref-discuss
