[publican-list] [Bug 475684] Find solution for using Glossaries with publican

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=475684





--- Comment #10 from Jeff Fearn <jfearn at redhat.com>  2009-01-21 17:27:40 EDT ---
(In reply to comment #9)
> This is not something that is getting fixed.

It breaks our ability to translate content, so from any perspective that
doesn't ignore translation it is broken and needs to be fixed. 

> This is something that is getting
> banned due to opinions.

I think it's highly insulting that you insinuate we have not done due diligence
on this functionality. It takes in to account all aspects of the Documentation
work flow; our customers expectations, and the real history and decisions of
the past that have positively and negatively affected the Docs team and Red
Hat.

> The mere possibility that someone might add a glossary
> to a book that is going to get translated is not a sane reason to ban the
> necessary tags in the first place.

It is not acceptable to break translation work flow regardless of the current
translation status of a particular work.

It is a sane policy given the volume of content, the size of the team we work
in, and that ignoring translation work flow has bitten us in the ass previously
and it cost us significantly to rectify that short sightedness.

I suppose if you don't have to care about the other people in the team and you
chose to ignore that this exact same attitude has occurred before and cost us
dearly, then sure, maybe we are just being silly.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.