[CF List] Questions about CF 1.0.0

Michael Toennies michael.toennies at nord-com.net
Wed Jun 20 00:28:24 CDT 2001


We can do a simple thing:
Include a special language tag to the text outputing commands
in the arch files.

like name_german or name_french.
Also: msg_german/endmsg_german.

On collect time, the collect tool generate for the server then the
right name cmd. The other language parts will be in arch but not be
in archtypes file which the server use.

With this, you can collect -german of collect -french and get a native
language
version of the arches.

I mean, for what reason have we a scripted object system when not for this?

Its of course some work - so if one want do it, he should start and tell me,
i include
then the collect syntax in the editor.

Btw, the CFJavaEditor can eat html as online help, so writing a help there
will usable for
web and editor.
Michael



>
     
     
     >
     
      Egbert Hinzen wrote:
     
     >
     
     
     >
     
      > Sorry, but you misunderstood my question. I tried this, but the
     
     >
     
      compiling
     
     >
     
      > died with lots of errors.
     
     >
     
      >
     
     >
     
      > Can you build theese files? They would be useful on the download servers
     
     >
     
      > and in the CVS...
     
     >
     
      >
     
     >
     
      > Thanks before!
     
     >
     
     
     >
     
       After some minor tweaks, the spoiler.ps built without problems (the
     
     >
     
      cupid.111.xpm file was using too many colors and confused the
     
     >
     
      xpm->ps parser)
     
     >
     
      and my tetex installation did not allocate enough
     
     >
     
      memory (I've added a note to doc/README about this, since it is
     
     >
     
      likely a common
     
     >
     
      problem)
     
     >
     
     
     >
     
       The handbook does not build - it doesn't look the equip.tex file
     
     >
     
      that gets
     
     >
     
      generated.  It may make more sense to just write one up by hand
     
     >
     
      than try to have
     
     >
     
      one get generated by the system (as I notice the file as listed
     
     >
     
      has things like
     
     >
     
      Elf player_force lines.
     
     >
     
     
     >
     
       The playbook itself is probably out of date, since it has never
     
     >
     
      been updated
     
     >
     
      for the split beween classes and races.  So the equip.tex
     
     >
     
      contains the races,
     
     >
     
      and of course many do not have any inherent equipment which may
     
     >
     
      be a problem.
     
     >
     
      And there is probably no mention about the differing classes.
     
     >
     
     
     >
     
     
     >
     
     
     >
     
      > >  Done properly, localization should purely be a client issue
     
     >
     
      (ie, connecting to
     
     >
     
      > > an american server, I should be able to tell my client I want
     
     >
     
      german as my
     
     >
     
      > > language).  This also gets a bit harder.
     
     >
     
      >
     
     >
     
      > Using GNU's gettext this wouldn't be such a big problem...
     
     >
     
      > We've done it with freeciv (an server/client civilization clone) and it
     
     >
     
      > runs well...
     
     >
     
     
     >
     
       The harder part I think will be all the archetypes, since they
     
     >
     
      have embedded
     
     >
     
      names/text in it (maps have a similar problem).  I don't know how this can
     
     >
     
      really dealt with reasonably well - either that portion remains
     
     >
     
      in English (to
     
     >
     
      localize all the objects/maps to each language would probably be
     
     >
     
      a lot of work),
     
     >
     
      or external references are needed (ie, messages don't contain
     
     >
     
      text, but rather
     
     >
     
      point to some message number, which of course gets harder to do).
     
     >
     
      _______________________________________________
     
     >
     
      crossfire-list mailing list
     
     >
     
     
      crossfire-list at lists.real-time.com
      
      
     >
     
     
      https://mailman.real-time.com/mailman/listinfo/crossfire-list
      
      
     >
     
     
     
    


More information about the crossfire mailing list