>> As far as I know there are no dropped commands.
>
> What about \Telefon, for instance?
\Telefon has not been dropped, it was replaced by \TelephoneRowA. That's what I meant should be
converted when we switch from g-brief to g-brief2.
>> > How about letters that include style files that rely on
>> > gbrief? For instance, my university's official LaTeX letter templates
>> > uses gbrief (not gbrief2). What you propose would break all my
>> > correspondances.
>
> This doesn't break any correspondance, you can use g-brief2 and get the
> same output.
>
> I cannot, since gbrief is hardwired in the university's template, which I'm
> not allowed to change.
But you can send them an email to ask that they change it. Every template has to be adapted from
time to time but the computer guys have to be informed. Besides this, why is this not possible? We
also have here an old template that uses g-brief and I can replace the class in the file to
g-brief2, and the commands to the corresponding new ones and get what I want. When you have
installed g-brief on your LaTeX-system you automatically also have installed g-brief2.
>> Note that g-brief is obsolete since 2003 now,
>
> Where is it declared obsolete? It's still shipped in the gbrief bundle, and I
> didn't find a statement in the docs that flag gbrief "obsolete".
OK, what do we do when a user reports a problem with e.g. LyX 1.2.x? We tell him: "LyX 1.2 is no
longer supported, please use LyX 1.5." There is no reason why LaTeX-package authors are not allowed
to do the same. So "obsolete" is perhaps not the right term, better is "no longer supported".
>> and that g-brief
>> doesn't work on MiKTeX and I guess also not with TeXLive 2007, is a fact we
>> can't ignore. Providing a layout for a class that don't work with recent
>> LaTeX-systems cannot be a solution.
>
> It works if you patch marvosym, gbrief or downgrade marvosym.
This cannot be done by normal users as you need admin proviledges for this. And you know that nobody
except of real experts know how to do this and that they have to do this.
> What I want to say is: we can just drop gbrief, if we feel like it. But
> converting gbrief documents automatically to gbrief2 is error-prone and will
> annoy people (like me) that rely on the original gbrief class.
Of course every conversion is error-prone but this should not prevent us from doing it. When the
conversion is done correctly, users won't have troubles so why should they be annoyed?
regards Uwe
