urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

reply (regression != suboptimal)

master
intrigeri 2010-12-26 02:33:24 +01:00
parent 2fe3f0494c
commit c058488274
1 changed files with 47 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
doc/bugs/urlto_API_change_breaks_wikis_with_po_plugin.mdwn
View File

@ -36,3 +36,50 @@ investigated this yet.
>>> with `po_link_to = current`, always go to the master language,
>>> whereas perhaps it'd be better to go to the negotiated language in
>>> this case? --[[smcv]]
>>>> Thanks for taking care, thanks for these improvements!
>>>>
>>>> OTOH I consider any of these behaviours (either the brand new one
>>>> = link to master language, or the alternative one = link to
>>>> negotiated) as a regression. Any of these is contrary to what
>>>> `po_link_to = current` is supposed to do according to the
>>>> documentation.
>>>>
>>>> Let's be less technical, let me display my practical usecase
>>>> (making this possible was one of the main reasons I initially
>>>> implemented `po_link_to = current`).
>>>>
>>>> Summary: the current state of things is an annoying regression
>>>> and it needs to be fixed.
>>>>
>>>> Context: I participate in building a Live system based on Debian
>>>> Live; the project's multilingual website
>>>> ([T(A)ILS](https://amnesia.boum.org/) is built using ikiwiki. A
>>>> static / offline copy is shipped on ISO images; this is the way
>>>> end-user documentation lands on the CDs. Note that no webserver
>>>> runs on the Live system to serve this wiki, so `po_link_to =
>>>> current` is compulsory. A user can choose her preferred language
>>>> at boot time. Depending on her decision, The desktop shortcut
>>>> that points to the embedded documentation (i.e. static wiki)
>>>> links to a different entry point depending on the chosen
>>>> language.
>>>>
>>>> The previous (documented) behaviour was deadly simple: if I am
>>>> presented a page in English (master language) it means it does
>>>> not exist in my preferred language; the computer always displays
>>>> me the best available version according to my needs. The new
>>>> behaviour brings a troubling seemingly random factor into the
>>>> user navigation experience and IMHO is a mess from a web
>>>> ergonomics point of view (no content negotiation available,
>>>> remember): I sometimes am shown an English page although it is
>>>> fully translated in my language one click away, and on the
>>>> contrary I sometimes I am shown the optimal page. This, is, well,
>>>> interesting. This practically forces the non-English speaking
>>>> website visitor to check the otherlanguages list on every single
>>>> page to make sure *herself* there is nothing better available,
>>>> and sometimes click on her preferred language link to get a page
>>>> she actually can read.
>>>>
>>>> I unfortunately might not be able to dedicate the needed time to
>>>> help fix this in a timely manner, so I don't want to urge anyone.
>>>> Take care! --[[intrigeri]]