[PATCH] EasyHack, fdo#46808, Adapt UNO services to new style, Parts 2 through 5

[Tor Lillqvist]

> MARKER: These services are not intended to be instantiated via their service names.

How is it in general with service names, if one browses services.rdb
(either of them), one doesn't have to look long to notice components
that have identical service names (but different implementation
names). What does this mean? That they are not supposed to be
instantiated via service names but via implementation names? Sorry if
this is a very fundamental question, but I guess I never fully have
understood UNO...

Hmm, I now see that the first such duplicated service name I come
across just visually browsing is css.frame.ContentHandler, which you
indeed mark with MARKER in your message.

> (And there's unfortunately lots of these, needlessly obscuring things in many ways.)

Indeed. Is there any point at all in cluttering services.rdb (and
other configuration files?) with these components if they aren't
looked for from there at run-time anyway?

 --tml