<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">For new users in particular it may not
be easy to find the section they were linked to, as it's sometimes
buried under multiple layers of index pages.<br>
Many links now seem rather meaningless. For example a lot SE posts
are filled with links targeted at specific parts of a section of
documentation.<br>
Now those posts are filled with a lot of links to the same index
page, usually with text like "adjust <setting> to do xyz",
which doesn't make much sense when <setting> goes to an
index page.<br>
<br>
IMO It's a lot easier to define a redirect for every page than to
edit every link in even one corner of the internet such as SE.<br>
We will already be editing (even rewriting in some cases) most of
the pages in the manual at some point or another.<br>
Compared to that, IMO defining a redirect for every page (or at
least most pages) doesn't seem too bad, assuming it's about as
quick as typing "/path/to/wiki/page -> /path/to/manual/page".<br>
<br>
Where does the maintenance come in? Once a page is redirected, I
would expect that to be the end of that.. Right?<br>
<br>
<br>
Translations are important, but I think useful links are important
too. I'm not a translator, so I doubt I could be of much help in a
translation project. But while the manual is being translated I
could redirect things ;)<br>
Also, much of the documentation is out of date/inconsistently
styled/just needs to be redone, so not sure if translating is a
good idea before at least some of the pages are deemed to be in
solid shape?<br>
<br>
I'm not familiar with Sphinx, but I was thinking even just big
file filled with stuff like<br>
<br>
/wiki/page -> /manual/page<br>
/other/wiki/page -> /manual/other/page<br>
/wiki/page/other -> /other/page/manual<br>
<br>
or perhaps some specially formatted comment at the top of each
manual page containing the url(s) of it's wiki equivalent(s) might
work?<br>
<br>
Then some script could collect all these and put them in proper
redirection shape, whatever and wherever that may be.<br>
<br>
On 06/02/15 00:03, Francesco Siddi wrote:<br>
</div>
<blockquote
cite="mid:etPan.556d5558.54e1fa4.8639@fsiddi-macbookpro.local"
type="cite">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi,</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">we have
currently set up section-wide redirects, which point the user in
the right direction. This global approach was chosen because
setting up individual redirects is time consuming and requires
extra maintenance.</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">As afar as I
know, Sphinx does not support smart redirection in the same way
MediaWiki does, so I don’t think setting up pages to make manual
redirects is a good idea.</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">If you can
share a practical example of how we could do this it would be
very interesting, but I first rather focus on the topic of
translations, which is still a bit fuzzy.</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Best regards,</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Francesco</div>
<br>
<br>
<p class="airmail_on" style="color:#000;">On 31 May 2015 at
21:20:44, gandalf3 (<a moz-do-not-send="true"
href="mailto:zzyxpaw@gmail.com">zzyxpaw@gmail.com</a>) wrote:</p>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div>I've yet to find any link to the old wiki which goes to
the correct page <br>
on the new manual.
<br>
Since there are probably thousands of links to the wiki,
this is pretty <br>
important to fix.
<br>
<br>
Assuming that manual pages will get moved around more and
eventually <br>
differ significantly from the structure of the old wiki,
it sounds like <br>
it may not be feasible to get the wiki to redirect
correctly with a few <br>
regex magics. Would it be possible to add some kind of
file in the <br>
manual repo that documentors could edit to manually define
redirects?
<br>
<br>
This would also help with redirecting future structure
changes/page renames.
<br>
<br>
<br>
-- <br>
-gandalf3
<br>
<br>
_______________________________________________
<br>
Bf-docboard mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-docboard">http://lists.blender.org/mailman/listinfo/bf-docboard</a>
<br>
</div>
</div>
</span></blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bf-docboard mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-docboard@blender.org">Bf-docboard@blender.org</a>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-docboard">http://lists.blender.org/mailman/listinfo/bf-docboard</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
-gandalf3</pre>
</body>
</html>