Marcin Owsiany wrote:
Who decided that we should just drop them all? After all generating a
non-UTF locale and setting an environment variable isn't a very
difficult workaround? I mean, when has lack of UTF support become an
RC-bug? Charset support is not even mentioned in the policy, other
severity 386299 serious
thanks
On Wed, Sep 06, 2006 at 06:14:55PM +0100, Marcin Owsiany wrote:
Unicode support in ekg2 is highly experimental and not yet supported
upstream, therefore the debian package is built without UTF-8 support.
On Wed, Sep 06, 2006 at 05:56:17PM +0200, Tristan
On Thu, Sep 07, 2006 at 06:25:26PM +0100, Marcin Owsiany wrote:
Try running it in some iso-8859 locale.
That's not an acceptable answer, given that almost all locales for etch will
be Unicode by default. This makes the package unreleasable. Of course, the
package seems to only be in
On Thu, Sep 07, 2006 at 02:46:16AM -0700, Steve Langasek wrote:
severity 386299 serious
thanks
On Wed, Sep 06, 2006 at 06:14:55PM +0100, Marcin Owsiany wrote:
Unicode support in ekg2 is highly experimental and not yet supported
upstream, therefore the debian package is built without
Package: ekg2
Version: 20060826+0920-1
Severity: grave
Justification: renders package unusable
Attempting to run ekg2 yields the following:
plugin ncurses cannot be loaded because of mishmashed compilation...
program compilated with: --enable-unicode
plugin compilated with:
severity 386299 minor
retitle 386299 Fails when run in UTF-8 environment
thanks
Unicode support in ekg2 is highly experimental and not yet supported
upstream, therefore the debian package is built without UTF-8 support.
On Wed, Sep 06, 2006 at 05:56:17PM +0200, Tristan Seligmann wrote:
6 matches
Mail list logo