﻿id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
17319	Internationalization documentation	dolma33@…	nobody	"Ok, you won't believe this one: neither do I \\ 
(and I've seen a lot of mistakes done by myself during my programming years --- I'm not such an experienced programmer, but I try)


I'm so involved in internationalization, that I'm always reading online questions about this topic, trying to learn something more, and to help other people in the (rare) fortunate case that I know how to help them.

In several communities/forums/etc I've stumbled on several people posting tickets (with titles like ""Django Internationalization not working"" ) \\ 
where the error was simply that they're copy-pasting the code in this documentation part \\  https://docs.djangoproject.com/en/1.3/topics/i18n/internationalization/#the-set-language-redirect-view \\ 
without noticing that in this line \\ 
{{{<input name=""next"" type=""hidden"" value=""/next/page/"" />}}} \\
The ""{{{/next/page/}}}"" string is just an example. \\ 
(They actually used {{{""/next/page/""}}} as a value)

Ok, things likte this can happen to everyone, we know that. \\ 
At the beginning I thought that it was because the askers were newbies, but I've seen this issue also from more advanced people... \\ 
The reason could be maybe distraction, maybe faith... I don't know... \\ 
But the fact is that too many programmers made the same mistake, \\ 
so maybe this part of the documentation could be improved in someway \\ 
(I don't know... maybe a simple change like ""{{{/next/page/path/}}}"" or ""{{{next_page}}}"" or ""{{{desired_next_page}}}"" could help)

Thank you

Anna Dolma Alonso \\ 
Biodiversity Informatics \\ 
Fundación Charles Darwin \\ 
Galapagos"	Cleanup/optimization	closed	Documentation	1.3	Normal	fixed	internationalization		Ready for checkin	1	0	0	0	1	0
