UI strings vs manual strings ?

What's the best way in a DocBook centered process to ensure that the =
list of terms used in a software UI is (semi-automatically?) taken into =
account in the DocBook sources that describe that software?

Problem at hand:

- a Java application with ~2k UI strings (not all users facing), in a =
Bundle.properties file
- a ~80K words DocBook manual

It is not trivial to keep track of the whole string set (searches, etc.)

Also, the l10n process takes place on the DocBook sources, not on the =
HTML output, so tricks like <link linkend endterm/> don't work because =
translators don't see the target terms.

I'm left with having to rewrite the strings explicitly and that's a =
pain, and also adds risks of mistakes in translations.

--=20
Jean-Christophe Helary @[email protected]
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/