project-navigation
Personal tools

Author Topic: gettext  (Read 4252 times)

Offline Mattn

  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 4831
  • https://github.com/mgerhardy/vengi
    • View Profile
    • Vengi Voxel Tools
gettext
« on: April 22, 2006, 08:12:51 am »
i think we should change something about the current system:

we should not mark the Console messages for beeing translated.
when there are error reports it wouldn't help us to search a solution if we can't read the console-messages....

and looked through the po-files - there is a lot of stuff to translate that is not game-related. hundrets of strings that handles console-messages.

what do you think?

Hoehrer

  • Guest
Re: gettext
« Reply #1 on: April 22, 2006, 08:51:31 am »
Quote from: "Mattn"
we should not mark the Console messages for being translated.
when there are error reports it wouldn't help us to search a solution if we can't read the console-messages....


I'm trying to do that already for everything error-related, so i'm in favor of translating only game-related messages (i.e. all text used anywhere in the GUI)

This not only makes debugging easier but also reduces the po-files to an easier to handle volume.

Werner

Offline Mattn

  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 4831
  • https://github.com/mgerhardy/vengi
    • View Profile
    • Vengi Voxel Tools
gettext
« Reply #2 on: April 22, 2006, 09:33:16 am »
Ok, whereever you find a Com_Printf, Com_DPrintf, Sys_Error, ri.Con_Printf or something like this - remove the gettext markers _("text").