Opened 11 years ago

Closed 6 years ago

#676 closed bug (worksforme)

FAQs and language selection

Reported by: fake51 Owned by:
Priority: minor Milestone: unassigned
Component: BW Internationalization Keywords: FAQ language selection
Cc: fake51, micha, midsch


When viewing an answer to a FAQ, selecting a different language from the footer does not behave as you would expect: the same page comes up, in the same language, only the url is different. This is weird to the user, and google doesn't like it either (and neither would other search engines.

Selecting a different language when viewing an answer to a FAQ should bring up the answer in the chosen language or a 404 page stating that sorry, we don't have the answer in that language, but we do have it in these languages (and then a list of available translations).

Change History (5)

comment:1 Changed 11 years ago by micha

  • Cc fake51 micha added

Ok, if I understood right, this is due to a lack of translations in our DB. But this is the general way to deal with translations from our DB - if a translation for a given language is available, we show it. Otherwise, we show the entry for the default language - English. Changing the FAQs in a way that we show something like "We are sorry but..." would mean to also change the rest of the page and that's even "changing our whole translation system". Do you want that with your bug-report, Peter? (Just asking.. :))

Otherwise I would say that this is something we have to live with. We could introduce slight changes though, like improving our translation system in a way that it would show such a notice (like the one you proposed) if a translation for the given language is not given, but only for a specific PHP-command. E.g. for now we use $ww->WordCode?. For a probable missing-translation-report, we could use $wwMiss->WordCode?(+Report for missing translation).

What do you think? I tend to mark this ticket "won't fix" and create a new ticket for the above feature.

comment:2 Changed 10 years ago by crumbking

what's the status here?


comment:3 Changed 10 years ago by fake51

Unless my testing skills fail me completely, this is working on live :) I thin JY fixed it (at least to a certain degree, it might be broken in some languages, please check)

comment:4 Changed 7 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

comment:5 Changed 6 years ago by midsch

  • Cc midsch added
  • Milestone set to unassigned
  • Resolution set to worksforme
  • Status changed from new to closed

Changing the language on FAQ kind of works (showing the demanded language or if not available English).

Note: See TracTickets for help on using tickets.