I just read that orca has replaced gnopernicus as the screen reader for
gnome 2.16 and was wondering if this was going to make it to fc6?
| Thomas Baker email: tjb(a)unh.edu |
| Systems Programmer |
| Research Computing Center voice: (603) 862-4490 |
| University of New Hampshire fax: (603) 862-1761 |
| 332 Morse Hall |
| Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb |
> Unfortunately, gcjwebplugin was pulled from the distro due to security
> that we will not have time to resolve by the final release. :/
should be updated with that information.
The inclusion of gcjwebplugin was highlighted in the last test release
It would be good to highlight why gcjwebplugin was pulled so reviews of
the next test release don't have conspiracy theories about the missing
Forwarded to the more "technical" list following discussion.
> Ya I really am saddened that no other distros have taken advantage of
> YaST being open source. Everyone keeps wasting resources and
> rebuilding when YaST is a good alternative and includes an ncurses gui
> too. I really like YaST and is probably the reason I keep having a
> hard time deciding between Fedora and openSUSE and keeping both of
> them on my HD. Porting YaST should be way simpler for Fedora as it is
> already RPM based. So many modules are there that rebuilding something
> else just seems like a waste of time.
> On 8/30/06, Nicola Losito <n.losito(a)yahoo.it> wrote:
> > So here i am again.
> > I've let settle down a little dust in the discussion with Raul.
> > From a Marketing point (yes, techicians ALL hates marketing) point how
> > can/want we "force" the developers to appeal more customers ?
> > And i do not mean professional ones which uses XEN or SElinux in a
> > "conscious" way, but everyday people. I mean the point & click
> > I might say to look on how Novell has worked on the desktop
> > SLED starting from the openSUSE, there are some yards of difference
> > the two projects.
> > From my point of view we can welcome more people:
> > - talking till come blue in the face of Fedora, of what's going on
> > (possibily);
> > - continuing this road of "disclosure" i am enjoying since Max has come
> > "the" chief :-P
> > - simplyfing the package management & retrieval (again to give a
> > i would *love* a hugest as possible fedora-extra repo, an external
> > FC-compatible non-US repository for packages that are allowed almoust
> > everywhere but not in the USA and a "Penguin Liberation Front" style
> > - answering in a clear and motivated way to people approaching ....
> > told "your vision is wrong or different" is useless. We have to
> > people who subscribes here or another no help-desk list has read and
> > understood our "policies" and still has a different take on them.
> > always perfectible (hope it's the right word) and welcoming new
ideas is not
> > always bad. On the contrary to stick obsessively with self made
> > end in a closed environment, and we - i suppose - are for the Open.
> > - try to develop more friendly and unified "control center" .... now for
> > Fedora (and also Debian) i see a tendency to put this effort on Gnome or
> > KDE. I like the Mandriva Control Center and YaST approach, and since
> > told me YaST is smart enough to leave untouched hand-modified files and
> > since it has become GPL'd i would like other distro approach and make it
> > better than it is (as it's being done with Smart Package management).
> > So, lunch is coming my way .... i'll stop bothering this list !
> > Thanks for reading ++ i do hope to have been "understandable"
> > --
> > Nicola .:kOoLiNuS:. Losito
> > http://koolinus.wordpress.com
Fedora-marketing-list mailing list
For reference, a copy of this posting as well as any updates on this
topic are available at
Per discussion on the Fedora Advisory Board mailing list, openmotif
currently does not meet Fedora's licensing requirements. The openmotif
developers have been contacted, but it appears openmotif's licensing
will not be changing soon.
The hard decision has been made that openmotif will be removed from
Fedora and the current plan is to make this happen by October 2, 2006,
the final development freeze for Fedora Core 6.
Currently, the following packages in Core and Extras contain runtime or
build time dependencies on openmotif:
Maintainers need to update their packages to use another motif
implementation, lesstif (in Extras). It is not 100% ABI-compatible (and
provides a different shared library soname), but all that should be
required for most motif-dependent applications is changing
Just a quick pointer to a madwifi patch to be able to compile the
modules for the latest Rawhide kernels :
I was sticking with 2.6.17-1.2339.fc6 (the last kernel I successfully
compiled the modules for) because of that problem, until I found that
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 5.91 (FC6 Test2) - Linux kernel
2.6.17-1.2617.2.1.fc6 Load : 0.52 0.80 0.98
Spell checking in our desktop is sort of a bit messy.
At the moment OpenOffice.org 2.0.X uses hunspell, the successor of
"myspell". Our OOo build has these hunspell libs as part of the OOo
The various hunspell dictionaries are then bundled in each OOo langpack.
I see that our Fedora Thunderbird contains a copy of myspell lib, but no
bundled dictionaries (?) So it's a unfortunate that OOo has dictionaries
for a pile of languages which thunderbird is unaware of, but would be
able to use without (probably) too much effort.
And then we have our traditional aspell and the various aspell
Recently I see that vim has added some sort of support for using the OOo
But I'm not sure what our fedora vim's status is here re that.
So, here's the hunspell webpage http://hunspell.sourceforge.net
and some commentary on aspell/hunspell/myspell and firefox
So what would be our *ideal* situation here ?
>From my side it'd be something like...
a) standalone hunspell (easy)
b) OOo uses standalone hunspell (easy, maybe a bit of tweaking
to autodetect system install dictionaries instead of existing config
c) firefox/thunderbird migrates from myspell to hunspell
autodetects available dictionaries
d) something or other is done to sanity-ify the vim usage of the
hunspell dictionaries to use them directly to avoid the rather baroque
procedure of the vim spell README (?)
e) someone else maintains the various hunspell per-language dictionaries
as separate rpms :-)
f) migrate other stuff from aspell to hunspell ? Add some aspell
compatibility stuff to hunspell to be a drop in replacement for aspell ?
Keep aspell, tweak it to handle hunspell dictionaries ? Ignore that the
hunspell dictionaries are just extended aspell dictionaries, and keep
the parallel set of aspell format dictionaries and aspell.