From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] bidi / fribidi useflag harmonization
Date: Tue, 23 Feb 2016 17:04:10 -0800 [thread overview]
Message-ID: <56CD018A.10909@gentoo.org> (raw)
In-Reply-To: <56CADE4B.3040801@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 02/22/2016 02:09 AM, Patrick Lauer wrote:
> We have two useflags expressing the same thing: bidi and fribidi.
>
> I suggest collapsing it into one useflag, and to make it a global
> useflag.
>
> Affected packages:
>
> dev-libs/efl/metadata.xml: <flag name="fribidi">Enable
> bidirectional text support</flag>
> games-action/supertuxkart/metadata.xml: <flag
> name="fribidi">Support for right-to-left languages</flag>
> games-strategy/megaglest/metadata.xml: <flag
> name="fribidi">Enable FriBIDi support</flag>
> games-strategy/wesnoth/metadata.xml: <flag
> name="fribidi">Support for right-to-left languages</flag>
> media-libs/avidemux-plugins/metadata.xml: <flag
> name="fribidi">Enable unicode bidirectional algorithm support via
> <pkg>dev-libs/fribidi</pkg>.</flag>
> media-video/ffmpeg/metadata.xml: <flag
> name="fribidi">Enables fribidi support in the drawtext
> filter.</flag> media-video/vdr/metadata.xml: <flag
> name="bidi">fribidi support, for languages, written from right to
> left</flag> x11-wm/fluxbox/metadata.xml: <flag
> name="bidi">
>
>
Is there more than one implementation of bidirectional text? If not,
I'm maintainer of x11-wm/fluxbox and would be willing to switch the
flag with the next release (or perhaps a revbump?) Any suggestions?
- --
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWzQGJAAoJEAEkDpRQOeFwAU4QAKgk8ncqoTN7H0e+e+IynGSi
mM8nIPoxDOdqTvXnuZWA/T6JqVyfzqLfZDD0zp6X5sktAsD/5yzNjaaUF1EcSdFs
u5J9SUY8E24hmm9ZXbmFhaYlRR8Xhh19G1nMS44zKUrHpcHraTGV4lZavAG8bHpi
jKHPIV5eaG2x2qdNkMRpWoqls0AONBXC+iOKKtevBPhIH+0a4HD6f4m4RMt2lxGZ
xzQ/5fAWtboTkmQa6QJptHCTdiUMalJL3AvGJ6oNeXlzBlEUP+ExPZNZNn3oJZ1d
XYUcvdBpQcQHClN1nA0SN5XyTje/cCpnXMY93528bh29oYXapLPbRXhvuRYvgkF0
e0RPveOLngM2DPZqBRC0BNIWIt0DgbQDi7shnD0aGefHkuKOn8ssM8eTZHOG1Yxa
2NTMqRVUt+MT09lPwC7HJwKqV2qkmVT3exXP4BYkGVMOtMhsfX71WG9ocE0QxdzS
vJEXoO/s1bVbD09noRO+rsjWKbIMdGfL/VpMcRG/stkU6kKK5EnpSM/g0iKmz+0j
fM3eTwwKboGnegLf+YfU+JzrSswcSnrEa5ohuJ8yRJ9EMABfXZWJCHvM5NkLm/er
lbBog8P03kdnoNXt6so11zrHe+YsSQlfS56UfAF3VOgnshY6RES81gpVTH/yUaFz
zzzgMrxnvHoPOGmOLbOM
=LqG2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2016-02-24 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 10:09 [gentoo-dev] bidi / fribidi useflag harmonization Patrick Lauer
2016-02-24 1:04 ` Daniel Campbell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CD018A.10909@gentoo.org \
--to=zlg@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox