http://bugs.freeciv.org/Ticket/Display.html?id=40853 >
Apple Bug report follow:
---
Process: Freeciv [24839]
Path:/Applications/Freeciv.app/Contents/MacOS/Freeciv
Identifier: freeciv.org.Freeciv-2.1.6
Version: Freeciv-2.1.6 version 0.2 (0.2)
Code Type: X86
note to myself: remember to send emails also to the mailing list ...
Am Wednesday 08 July 2009 20:50:19 schrieben Sie:
> 2009/7/8 Matthias Pfafferodt :
> >> Patch-for-bug vs. patch-for-new feature might seem clear to those
involved for a time, so it'd probably would give similar results to
simply
Follow-up Comment #3, bug #13867 (project freeciv):
the idea was to switch from a translation after the
wrapper function, i.e.
_(setting_short_help(pset))
to a structure which does the translation within the
wrapper functions, i.e.
const char *setting_short_help(const struct setting *pset)
{
Follow-up Comment #4, bug #13867 (project freeciv):
Ah, oops - my apologies for the noise.
I really should have read the patch before sounding off (since I clearly
misunderstood the translation tags as being used for static text rather than
calculated text). :-p
[Still... it's unfortunate that
Pepeto is #13879:
> I'm sorry to remake an old discussion, but do we still continue to maintain
> all this ancestral clients that nobody didn't update for a long time? I
> think a complicate project like Freeciv would concentrate into one only good
> client instead of having x incomplete clients.
2009/7/8 Daniel Markstedt :
>
> How about this for the definitions of bug and patch:
> * A patch is an issue for which you have prepared a fix or is planning
> to prepare a fix yourself. Typically used by regular contributors.
> * A bug is an issue for which you do not have a fix and wish for
> som
Update of bug #13857 (project freeciv):
Category:None => bootstrap
Status:None => Fixed
Assigned to:None => cazfi
Open/Closed:
