Issue #i43873# (already being fixed) has already reduced the problem of this
issue to only the initial configuration (usually done when the linguistic is
used for the very first time) after an Office installation is starte, or when
the writing-aids data files are actually modified.

The goal is to not annoy the user with this even in the initial start-up.
There are at least two ways that can be thought of:
a) The performance of updating the configuration has to be improved.
    This can probably be done optimizing the function that currently does it and
maybe  
    also by improving the configuration itself in critical areas.
b) We can do the same as many other third party applications do when they are
started  
  for  the very first. Taking some minutes to configure all things that need to
be done 
  only once AND displaying a window that this is currently being done. There is
probably
  no user who will find this odd even if it would take several minutes.
  That way we can not only do the linguistic cinfiguration at that time but also
initialize
  all the Writers templates (which currently also interrupts the users workflow
the very
  first time) and everything else that our other applications need to have
initialized 
  sooner or later.

TL: I would prefer the second solution since it is a more general approach and
can be used for other purposes and applications as well.

TL->FL: Maybe it would be a good idea if someone can make a list of what kind of
tasks 
that need to be done anyway at some point, can usefully be done in such a 'post
installation configuration' to save that time later on.