Getting rid of 'oldref' in the help files

[Jan Holesovsky]

Hi Jan,

Jan Iversen píše v Pá 16. 12. 2016 v 16:27 +0100:

> > this change is supposed to be transparent for L10n and
> > Documentation teams, but they should know :-)
> 
> It does not seem transparent for the few languages that do not use pootle (sl and sr) please do not forget those.

Thanks for the reminder.  I hope Cloph can do the upgrade for them some
way that fits them too, though?

> It does also influence the help repo (of course), since the change will be a very big commit.
> 
> > [Or - any objections to this change?]
> 
> No objections as I think it is a good and welcome change, just a question.
> 
> As we discussed in ESC (and Oliver sort of pushed) it seems the goal
> is to move away from .xhp to .xhtml (if I understood it correct). If
> decided do we then want to do that as a set of small steps or make 1
> script that does it ?

I tried to explain on the documentation@ why a big-bang move to html is
not a good idea from many reasons in another thread; to name the most
important ones:

* big-bang "let's abandon one technology and hooray for another one"
  always brings lots of regressions that are hard to fix in a timely
  manner; incremental changes are easier to maintain

* html does not have markup for some of the semantics that we have (and
  need) in the help files (like <section> or <embed> to name few)

* there are many ways how to describe the same thing in html (<b>'s and
  <i>'s vs. <strong> and <emph> vs. <div>'s with css vs. who-knows-what)
  which would make the help harder to maintain, if we eg. want to reuse
  the information from there to generate other representations (like
  eg. books or so)

> Please just see this as a question of how often to we want to run these conversions.

One more may be needed if we agree that the id="..." attribute could be
done non-mandatory, because that one affects the msgctx too.

If we want to make the XHP markup look more like HTML markup (which I
don't object in general & this is up to agreement between between the
Documentation and L10n people), there might be additional conversions
needed, for things like <image> -> <img> etc. - but I'd like to keep
this separate from the cleanup effort / topic.

All the best,
Kendy