Issue 12812

Summary: name of Bibliography data source should be localized
Product: Internationalization Reporter:
Component: uiAssignee: AOO issues mailing list <issues>
Status: ACCEPTED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 1.0.2   
Target Milestone: ---   
Hardware: PC   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description 2003-03-29 09:49:31 UTC
One of the source of Data Source is Bibliography. It should be Bibliographie.
Best, Sophie
Comment 1 stefan.baltzer 2003-03-31 17:57:04 UTC
Reassigned to Éric.
Comment 2 stefan.baltzer 2003-03-31 17:58:33 UTC
SBA: Changed target to 1.1 Beta2.
Comment 3 eric.savary 2003-04-02 16:55:33 UTC
Changed terget.

- general problem: the biblio db name "Bibliography" is not localized
at all ("Bibliography" in every language)
- TV told me he can't change this name over his tooling and that you
*may* responsible for this task. Any other victim? ;-)
Comment 4 Oliver Specht 2003-04-04 10:15:39 UTC
os->fs: AFAIK the name of the datasource is defined by the node name
in the DataBaseAccess configuration file which is not be language
This could be changed by introducing neutral node names and a data
source node name property.
Comment 5 Frank Schönheit 2003-04-28 16:18:33 UTC
> This could be changed by introducing neutral node names and a data
> source node name property.

No, bad idea, because this would make the actual name dependent on the
locale of the installation (or client) which is used to access the
configuration where the data source definition is stored.
This would cause a _lot_ of trouble, e.g. if we (perhaps) happen to
have multi-lingual office installations, again (means if the language
of an installation can be switched). We once tried this in StarOffice
5.2 with the "database aliases", and keeping them unambiguous across
_all_ languages was error-prone like hell. Not to mention that users
don't really understand/accept an error like "No. You cannot name your
data source 'foo', because this would conflict with another data
source which, in another language than your current one, is also named
'foo', though in your language, it's named 'bar', thus you cannot see
this conflict, but believe me, it's there!".

So I think the only solution is to name the data source at setup time,
and give it a name which corresponds to e.g. the setup language, but
is fixed from then on, and especially does not change if the same
configuration is accessed with another user locale.
Comment 6 Frank Schönheit 2003-07-15 15:36:35 UTC
changing summary for better reflecting what this is about
Comment 7 marc.neumann 2003-09-16 10:39:24 UTC
"According to the roadmap
( this issue was retargeted to
OOo Later." 
Comment 8 Marcus 2017-05-20 11:13:43 UTC
Reset assigne to the default "".