Translating the basic search bar is troublesome

Bug #1221411 reported by Pasi Kallinen on 2013-09-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Because the search bar translatable strings consist of three separate translatable words -- "Search", "for" and "in" -- it's nearly impossible to translate well.

This branch changes it, so there's one complete sentence to translate, with placeholders for the input controls.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/paxed/i18n-basicsearch-bar

Ben Shum (bshum) wrote :

Marking this as incomplete pending further evaluation now with the changes merged to master as of 2013-09-25.

Changed in evergreen:
status: New → Incomplete
milestone: 2.5.0-beta1 → none
Pasi Kallinen (paxed) wrote :

Now the translatable strings look like "Type: " or "Format: "

This is an improvement over the old style, but not as good as my solution was. The strings should have a placeholder for the place where the drop-down boxes are placed... and I'm still advocating for context for translatable strings: https://bugs.launchpad.net/evergreen/+bug/1178557

I am very puzzled. Making each label for an input field separately
translatable is completely standard practice. I don't see any advantage to
using placeholders. Do you mean to put all of the input fields and their
labels into a single translatable string? That would complicate any
reordering, addition, or deletion of individual input fields significantly.
At the very least it would require new translations.

As for advocating for context, sure, I'm in favour of that too. We need an
implementation that supports it, though, and as far as I know no one has
created such a branch.

Changed in evergreen:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers