Date: Sat, 17 Mar 2001 14:39:35 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Nik Clayton <nik@FreeBSD.ORG> Cc: doc@FreeBSD.ORG Subject: Re: http://www.freebsd.org/docs/, /FAQ/, /handbook/, and others Message-ID: <7mg0gdt0mg.wl@waterblue.imgsrc.co.jp> In-Reply-To: <20010315103248.A49019@canyon.nothing-going-on.org> References: <20010314212034.A45244@canyon.nothing-going-on.org> <7mk85rvksr.wl@waterblue.imgsrc.co.jp> <20010315103248.A49019@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 15 Mar 2001 10:34:30 GMT, nik wrote: > I was confused about this too -- I can't see the difference, but people > were saying that directory symlinks are bad, but file symlinks are not > (or, at least, less bad). IMHO, problem is not whether file or directory, but how many duplicates caused by that. > I would like all the documentation to be easily accessible from > docs/index.html (or doc/index.html, I'm easy on that point) on the web > site. This page (and/or set of pages) would then contain links to the > actual documentation, shielding the user from the length of the URLs. Ideally, that's good. But usually, I often type URL of the Handbook directory, not use hyper-link on top page. But as you said, we now have many documents to be linked. So I agree with you to use docs/index.html for portal of documents. > 1. Use redirects in the web server config file. > > 2. Symlink the FAQ/ directory to ../docs/en*/books/faq/ > > 3. Symlink the contents of ../docs/en*/books/faq/ in to FAQ > > 4. Duplicate the content by installing copies of the documentation > in to FAQ and Handbook. Hmmm, what I want to know is not *how* to achieve new hierarchy, *what* hierarchy you want to use. > > We should consider how to use language identifier in URL. > > Good question. Again, IMHO, I think that someone going to www.freebsd.org > would expect to see the English home page, going to > www.freebsd.org/handbook/ would expect to see the English Handbook, and > so on. Agreed. > I'm not very comfortable with the current approach of putting the other > languages in subdirectories, such as ja/, although I can see some merits > to it. But as a user, I would expect to go www.ja.freebsd.org and see > the Japanese page by default. I think making new domain (like www.ja) is not good idea. If we decide to use www.FreeBSD.rog/ja for Japanese translated pages, that is enough for us (of course it's my point of view). Japanese translation is often old information than the English version. So we often refer the English version to know latest information. This causes switching both version frequently. I like current structure which includes multiple languages in one domain. I want to know other person's opinion about this... > I also like the work I've seen on other sites where most pages have a > link at the bottom of them that says something like > > This page also available in: [English] [Japanese] [Spanish] [...] > > where the various language names take you to the translation of the same > page. I have not yet given any thought to how we could easily achieve > this, given that different translations have progressed differently in > terms of the amount they have translated. Honestly, I have no idea to use this feature because: o We are using language separated directory. Default behavior of Apache requires language suffix to select localized contents. o We should not request special configuration for mirror site administrators. I hope someone knows neat idea... > [ Speaking of which, is your automated list of where the translations > lag the English version still available? We should probably put a > link to that somewhere prominent, and extend it for the other > translations ] Yes, please refer here: http://www.jp.FreeBSD.org/doc-jp/syncstat/ > Perhaps we should be installing all the HTML files with an additional > suffix depending on the language: index.html.en, index.html.ja, and so > forth. A variable set during install time would then symlink these back > to the regular filename. So if you do "make install" with WEB_LANG set > to en_US.ISO_8859-1 then index.html is a link to index.html.en. If > WEB_LANG is set to ja_JP.eucJP then index.html is a link to > index.html.ja, and so forth. A proof of concept of this is probably > only a couple of hours work, if someone wants to send a patch. > > I'm just kicking out ideas for discussion at the moment. Using content negotiation should be discussed more carefully. Please give me more time to consider. As first step, how about to install books, articles and so on like this (not using docs/en): /index.html /docs/books/handbook/index.html /docs/books/porters-handbook/index.html /docs/articles/committers-guide/index.html /ja/index.html /ja/docs/books/handbook/index.html /ja/docs/books/porters-handbook/index.html /ja/docs/articles/committers-guide/index.html -- Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. <kuriyama@FreeBSD.org> // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mg0gdt0mg.wl>