[pacman-dev] Several output issues

[Xavier]

On Thu, Sep 27, 2007 at 11:09:30PM -0500, Aaron Griffin wrote:
> On 9/14/07, Xavier <shiningxc at gmail.com> wrote:
> > On Fri, Sep 14, 2007 at 11:15:19AM -0500, Aaron Griffin wrote:
> > > On 9/14/07, Xavier <shiningxc at gmail.com> wrote:
> > > > Just did some testing with pacman 3.0 :
> > > > using english output, it worked fine, but in french, there already was a little
> > > > problem :
> > > > (1/1) Analyse des conflits entre fichiers           [############################################] 100%
> > > > Avertissement: /etc/X11/twm/system.twmrc installé en tant que /etc/X11/twm/system.twmrc.pacnew        %
> > > > (1/1) Mise à jour xorg-twm                          [############################################] 100%
> > > >
> > > >
> > > > Just the % appeared at the end of the line.
> > > > That's still better than the current pacman 3.1 output, as seen in my first post.
> > >
> > > Random guess without looking at it, this is another "fail at
> > > calculating the line length due to accented chars".
> >
> > Yes, that was the problem indeed.
> > Since I didn't know anything about this stuff, I asked for some help on ##c :)
> > So it's possible to compute the real number of characters using mblen in a
> > loop. I did that on pacman 3.0 and it works fine, the above problem is fixed.
> >
> > About pacman 3.1 , I see Dan removed that pm_printf function, and later added
> > back a much simpler version of it, without all that padding stuff.
> > So maybe the old version should be restored?
> 
> Prodding here. Is this still an issue with the git version? It seems
> the output functions are much improved

The issue is mainly with 3.1.
The first post in this thread was made with 3.1. You then pointed me to
some padding stuff, which I found only in 3.0.
Indeed, 3.0 behaves better, except that there was a minor issue with
widecharacters, eg. french accent é. I proposed a fix for that, but it only
applies to 3.0 .
3.1 removed all that padding, so now the whole bar is displayed after output
messages (again, see the first post in this thread).