-
Notifications
You must be signed in to change notification settings - Fork 23.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[IMP] base, l10n_jp: titles on contact.
In multiple countries, adding honorifics near the names of your customer/vendor/… is seen as basic politeness and not doing so is considered rude. One well-known example is Japan, Korea is another country with similar needs. As of today, Odoo has no way to do that easily, and users have no choice but to use Studio to customize the reports manually. This feature aim to improve that by providing a standard way of providing titles when sending documents to your contacts. This is done by adding the title to the contact qweb widget by default if it is set on the contact record. This also adds a new field on the title model in order to define whether the title should be a prefix or a suffix. Note that this is a simple, naive approach that may not fit all scenarios perfectly. task id # 3272592
- Loading branch information
Showing
6 changed files
with
51 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<odoo noupdate="True"> | ||
<!-- These are set directly in japanese, are you cannot really translate english in all cases. --> | ||
<record id="res_partner_title_sama" model="res.partner.title"> | ||
<field name="name">様</field> | ||
<field name="position">after</field> | ||
</record> | ||
<record id="res_partner_title_sensei" model="res.partner.title"> | ||
<field name="name">先生</field> | ||
<field name="position">after</field> | ||
</record> | ||
<record id="res_partner_title_hakase" model="res.partner.title"> | ||
<field name="name">博士</field> | ||
<field name="position">after</field> | ||
</record> | ||
<record id="res_partner_title_onchu" model="res.partner.title"> | ||
<field name="name">御中</field> | ||
<field name="position">after</field> | ||
</record> | ||
</odoo> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
<?xml version="1.0" encoding="utf-8"?> | ||
<odoo> | ||
<record id="res_partner_view_form" model="ir.ui.view"> | ||
<field name="name">res.partner.form</field> | ||
<field name="model">res.partner</field> | ||
<field name="inherit_id" ref="account.view_partner_property_form"/> | ||
<field name="arch" type="xml"> | ||
<!-- in Japan, honorifics should also be added to companies. --> | ||
<field name="title" position="attributes"> | ||
<attribute name="invisible">is_company and country_code != 'JP'</attribute> | ||
</field> | ||
</field> | ||
</record> | ||
</odoo> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters