Issue 113803 - Add Tower labels
Summary: Add Tower labels
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 3.2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2010-08-11 13:37 UTC by Dwayne Bailey
Modified: 2017-05-20 10:44 UTC (History)
2 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

Tower label patch (12.72 KB, patch)
2010-08-11 13:38 UTC, Dwayne Bailey
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description Dwayne Bailey 2010-08-11 13:37:46 UTC
In South Africa we have a label manufacturer called Tower.  We've created label
specifications for their labels.
Comment 1 Dwayne Bailey 2010-08-11 13:38:30 UTC
Created attachment 71039 [details]
Tower label patch
Comment 2 michael.ruess 2010-08-16 16:11:14 UTC
MRU->OS: please evaluate the patch and eventually apply in 3.4.
Comment 3 Oliver Specht 2010-11-05 09:07:35 UTC
I doubt that it makes sense to add these labels to all localizations of OOo. 
It would make more sense to create an extension which then should be
preinstalled in the localizations where the Tower labels are available. 
See about non-code
Comment 4 Dwayne Bailey 2010-11-05 17:38:33 UTC
os -> localisation are language based not region based.

You suggestion also doesn't adequately address the fact that many South African
users will us en_US and have no regional variant in which to pull in the labels.

Tower labels are available in South Africa and a growing market.  Thus they
impact the not only the South African region but wherever they are exported.

In terms of the current setup we have a situation where in South Africa I see
German and American labels that are not available here.  So this issue affects
the current setup.

Its another bug but the correct approach would be to be able to create list of
regions where we should display labels or allow users to filter based on their
Comment 5 Martin Hollmichel 2011-03-16 11:44:05 UTC
set target 3.x since not relevant for 3.4 release.
Comment 6 Rob Weir 2013-03-11 15:04:37 UTC
I'm adding this comment to all open issues with Issue Type == PATCH.  We have 220 such issues, many of them quite old.  I apologize for that.  

We need your help in prioritizing which patches should be integrated into our next release, Apache OpenOffice 4.0.

If you have submitted a patch and think it is applicable for AOO 4.0, please respond with a comment to let us know.

On the other hand, if the patch is no longer relevant, please let us know that as well.

If you have any general questions or want to discuss this further, please send a note to our dev mailing list:


Comment 7 Dwayne Bailey 2013-09-16 11:20:13 UTC
I haven't reviewed my patch since it was submitted.  But this same patch was accepted upstream by Red Hat and has made it into LO, I'm not sure if any changes where made to the patch to allow the merge, but I assume not.

So still relevant but I'm not able to check the patch.
Comment 8 Marcus 2017-05-20 10:44:17 UTC
Reset the assignee to the default "".