HEADS UP: gettext port update on FreeBSD

Dan writes "FreeBSD's Joe Marcus Clarke has committed an update to the gettext port to 0.12.1 on FreeBSD. GNU `gettext' is an important step for the GNU Translation Project, as it is an asset on which we may build many other steps. This package offers to programmers, translators, and even users, a well integrated set of tools and documentation. Specifically, the GNU `gettext' utilities are a set of tools that provides a framework to help other GNU packages produce multi-lingual messages."

Comments

Important !

[Anonymous Coward]

It is _recommended_ people install sysutils/portupgrade then do:

portupgrade -rf gettext -m BATCH=yes

to upgrade gettext and all of the ports that depend on it. However, if
you use portupgrade to preserve old shared libraries (i.e. you do not
run portupgrade -u), then you do not _have_ to do the full recursive
update. However, you may run into problems later on if you hold off on
doing this.

Re:Ok ?

[Fweeky]

It means any port which uses it needs to be updated too (unless you use portupgrade and have it preserve old libraries), and that's quite a lot. Not sure what it's doing here though ;)

FreeBSD was using 0.11.5 before this change, btw.

Re:Ok ?

[Detritus]

It suggests running "portupgrade -rf gettext -m BATCH=yes" to update all the affected ports. Looks like my system is going to be recompiling ports for a few days.

Re:Ok ?

[Detritus]

That confused me for a minute. I did some research and I found out that "=3D" is how an equals sign is encoded in the "quoted-printable" text encoding. This tends to show up when someone uses a non-ASCII character in a page of text, which can trigger "quoted-printable" text encoding in some software. The software on the receiving end is supposed to convert it back to normal text. Sometimes this doesn't happen, due to bugs or other causes. Then you are left with ugly text that contains "=3D" in every place that an equals sign appeared at in the original text. Whoever invented "quoted-printable" text encoding made the questionable decision of using the equals sign as the escape character in their encoding. That means that the equals sign, a perfectly good ASCII character, has to be replaced with its encoded equivalent "=3D". I found many instances of this problem while doing google searches.