Skip to content

[19.0][ADD] l10n_jp_hr_employee_name_kana: kana reading for employees - #139

Open
AungKoKoLin1997 wants to merge 1 commit into
OCA:19.0from
qrtl:19.0-add-l10n_jp_hr_employee_name_kana
Open

[19.0][ADD] l10n_jp_hr_employee_name_kana: kana reading for employees#139
AungKoKoLin1997 wants to merge 1 commit into
OCA:19.0from
qrtl:19.0-add-l10n_jp_hr_employee_name_kana

Conversation

@AungKoKoLin1997

@AungKoKoLin1997 AungKoKoLin1997 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Adds a normalized kana reading (カナ / ふりがな) to employees.

@qrlt QT7089

Employee names are looked up constantly -- in the directory, when assigning
work, when picking an approver -- and a name written in kanji is subject to the
same problem as a contact's: colleagues know the pronunciation, not the
characters.

The reading is exposed on hr.employee.public as well, so an internal user with
no HR access can still find a colleague by pronunciation. That model is a
read-only SQL view over hr.employee, so it resolves its format from hr.employee
rather than looking one up for itself: a setting of its own could disagree with
the format the reading is actually stored in, and the directory search would
then match nothing.

Auto-installed, so that the reading appears on employees as soon as both the
kana module and hr are present.

Assisted-by: Claude Opus 5
@OCA-git-bot OCA-git-bot added series:19.0 mod:l10n_jp_hr_employee_name_kana Module l10n_jp_hr_employee_name_kana labels Aug 6, 2026
@AungKoKoLin1997 AungKoKoLin1997 changed the title [ADD] l10n_jp_hr_employee_name_kana: kana reading for employees [19.0][ADD] l10n_jp_hr_employee_name_kana: kana reading for employees Aug 6, 2026
@AungKoKoLin1997
AungKoKoLin1997 marked this pull request as ready for review August 6, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:l10n_jp_hr_employee_name_kana Module l10n_jp_hr_employee_name_kana series:19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants