Issue 71279 - A default template file for each application
Summary: A default template file for each application
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-07 05:51 UTC by tora3
Modified: 2013-02-07 22:32 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description tora3 2006-11-07 05:51:36 UTC
IMHO, having a default template file for Writer, Calc, Impress, Draw, and 
others would solve many requests related to the default settings at a time.

In case of enterprise wide installation, system integration vendors or system 
administrators have to achieve customers requirements. A large enterprise 
tends to have defined their own document policy such as default font name 
and size, size and margins of sheet, and the number of lines per sheet and 
characters per line. 

Yes, current implementation of soffice is capable of specifying a default 
template file for each application, but a way of instructions through the 
menu File - Templates - Organize to do so is slightly complex and cannot be 
done without user interaction. Because of a large amount of client machines, 
a simple way to deploy template files is demanded.

Some experienced vendors know short cut tips for deployment of default 
template files by modifying one of the configuration files under the folder 
'share/registry/data/' and by putting the template files in the publicly 
accessible directory, but such a fashion could not be widely accepted. 		

One of the possible solutions:
 1. Prepare directories share/template/<locale>/default/ and presets/....
 2. Put null template files: swriter.ott for Writer, scalc.ots for Calc, 
    and so on in the directory.
 3. Each application will confirm at startup if a template file exists and 
    use it. If it does not exist, go fallback to the current implementation.

I could not find any similar issue directly discussing deployment of template 
files. If already filed, please forgive me and close this for duplication.

Thanks
Comment 1 thorsten.martens 2006-11-13 11:52:51 UTC
TM->requirements: please have a look, thanks !