Date: Sat, 11 Mar 2006 19:37:55 +0000 From: Ceri Davies <ceri@submonkey.net> To: K?vesd?n G?bor <gabor.kovesdan@t-hosting.hu> Cc: remko@FreeBSD.org, doc-committers@FreeBSD.org, doc@FreeBSD.org Subject: Re: cvs commit: www/en where.sgml Message-ID: <20060311193755.GE73523@submonkey.net> In-Reply-To: <441322C7.8020200@t-hosting.hu> References: <200603111503.k2BF3bsI006826@repoman.freebsd.org> <20060311152536.GD73523@submonkey.net> <441302E4.6010805@FreeBSD.org> <441322C7.8020200@t-hosting.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
--sXc4Kmr5FA7axrvy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Mar 11, 2006 at 08:19:35PM +0100, K?vesd?n G?bor wrote:
> Remko Lodder wrote:
>=20
> >Ceri Davies wrote:
> >
> >>On Sat, Mar 11, 2006 at 03:03:37PM +0000, Remko Lodder wrote:
> >>
> >>>remko 2006-03-11 15:03:37 UTC
> >>>
> >>> FreeBSD doc repository
> >>>
> >>> Modified files:
> >>> en where.sgml Log:
> >>> Use &base; in the where.sgml file like other files also use.
> >>>
> >>> PR: www/94098
> >>> Submitted by: Gabor Kovesdan <gabor dot kovesdan at t-hosting=20
> >>>dot hu>
> >>> Revision Changes Path
> >>> 1.81 +51 -51 www/en/where.sgml
> >>
> >>
> >>While I am not wildly opposed to this, I don't really see what this
> >>gains us, other than to make the rendered page (at least) 102 bytes
> >>larger (&base; being equivalent to "./" most of the time).
> >>
> >>I'm all for consistency, but perhaps we should go the other way.
> >>Comments?
> >>
> >>Ceri
> >
> >
> >Well, If we use it throughout the tree we should do it for consistency.
> >That was my goal with the commit. I can agree with you that &base; =3D .
> >seems somewhat bogus, but when we change the base entity declaration we
> >have everything in place to be updated in one go.
> >
> >So i can see your point, and i can see the other point..
> >
> >Do others have ideas as well? Copied -doc for that reason so that we
> >have a broad base to get this right :)
> >
> >Thanks for the feedback though!
> >
> Currently, I'm translating the FreeBSD Webpage to Hungarian, and I=20
> intend to send the webpage back to the project when I have finished it.=
=20
> There are parts that aren't worth to translate, because they're changing=
=20
> fluently or irrelevant for the Hungarian community, etc. For example, I=
=20
> don't want to translate all the release notes, because this means a huge=
=20
> work, and I can't guarantee that I would be able to keep it up-to-date=20
> and translate the release notes after each release. I will link these=20
> pages with using &enbase;. I could use "../" as well, but I think that=20
> would be quite awkward and not really transparent. Using either &base;=20
> or &enbase; in the whole codebase makes the whole code much more=20
> transparent and clear
>=20
> As I see, the French Webpage uses the same approach, but e.g. the German=
=20
> Webpage uses &base;/../ in these case, which is very ugly. It would be=20
> nice if we introduced a new rule for this. If you accept my point I can=
=20
> work on reviewing the translations and sending patches to standardize=20
> this, so that we have smart, transparent and consistent code in the=20
> whole webpage.
Well, if it helps to ease translation then it's cool with me.
Ceri
--=20
That must be wonderful! I don't understand it at all.
-- Moliere
--sXc4Kmr5FA7axrvy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (FreeBSD)
iD8DBQFEEycTocfcwTS3JF8RAi8AAKDHTUVJ4Qn57MGPkdp82oqeovRDDwCgyk8b
Wa+fTPeBLP5+NEMWbp9dQZk=
=ClQo
-----END PGP SIGNATURE-----
--sXc4Kmr5FA7axrvy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060311193755.GE73523>