Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9553106FE for ; Fri, 23 Aug 2013 23:00:22 +0000 (UTC) Received: (qmail 8775 invoked by uid 500); 23 Aug 2013 23:00:22 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 8709 invoked by uid 500); 23 Aug 2013 23:00:22 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Delivered-To: moderator for dev@openoffice.apache.org Received: (qmail 67898 invoked by uid 99); 23 Aug 2013 21:33:36 -0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of palbuquerque73@gmail.com designates 74.125.82.47 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=9PyEl0YrujoaA88FB/2LGbcjSeFrNxXC/bU0LV75lzk=; b=iMzNV1F1iKSaE4nB09FfXswYrMBgzRPsCKFz+VcPJ/AczqcloDaOn/DdVst94IVJRB ooyjrnSVQ5enBPLGBZJxuWIseuCT6GVbyabzRdlTIaPXVh/tYp+SKqkyW+sen3ByozbA 1U14GP+tCM52i78K/Wq1yaUxtA5aQD5ux6pxBBAFT46bSl0VEmmOGddYJBfVL8tjGt1I hBJvyEjPIbhzwdksDK7WnS5XDPUmR7ruBQNGBxtgm2SvbXdJLsZEcol18cJm3C8/CSqw d1vcoBykDRDiKHkXgmdaL9xlMEkDKHCOaaw3CDtZJDG/+9MJB3szmhfESeMqHKnDTPcS IV8w== X-Received: by 10.194.48.74 with SMTP id j10mr1265612wjn.41.1377293588278; Fri, 23 Aug 2013 14:33:08 -0700 (PDT) Message-ID: <5217D511.7040004@gmail.com> Date: Fri, 23 Aug 2013 22:33:05 +0100 From: Pedro Albuquerque User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: dev Subject: Re: Brainstorming: Can we refactor the website to make translation easier? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, Em 23/08/2013 16:58, Rob Weir escreveu: > (Responses to dev@openoffice.apache.org, please) > > As a test I tried to create my own NL page, in the fictitious "xx" > locale. You can see it here: http://www.openoffice.org/xx/ > > 1) I had to hunt around and guess which files to copy. Do I copy > scripts, images and CSS, or just content pages? Some of the > directories had out-dated content that was not linked to my anyone. > It was hard to figure out what the minimum amount of content needed > was, and where it was located. Likewise here with the Portugal site! > 2) The main index.html file had to be edited to refer to CSS in the > root, rather than current directory > > 3) Download page is missed up, missing CSS and/or scripts. > Presumably I need to copy something into the xx/download dir, or edit > scripts to make them refer /download off the root. > > 4) The /xx/why pages are not showing the right side navigation now. I > must have missed something there as well. I suppose that's why I had to ask for help on the download link. > Of course, I could figure the above out eventually. It just requires > some time and effort and trial and error. But none of this is > documented, and even if it were this is a fragile approach and > probably beyond th web development skills of a typical translator. Couldn't agree more! > 1) What if we refactored the home page so it was all self-contained > into these directories: /scripts, /styles, /images and /en/? > > 2) Make the /en directory be pure content. Only the stuff that needs > to be translated. It loads everything else, scripts, images, etc., > via URLs relative to the root, e.g.., in /scripts, /styles, etc. Being a ignorant as I am, seems a lot more simple, anyone could choose what to do with the localized site accordingly to its own skills. > This is obviously more than a one-person task. So I'd be interested > in hearing what you think in general about this approach, whether > there is a simpler alternative I've missed, and whether this is > something you'd be interested in helping with. > As I'm not a developer or programmer but just a curious, I'm whiling to help in every way possible. So I'll give my opinion. I think that basically there are not many mandatory things to be in an official localized site. Those should be automatically inserted (I think that they already are). Other than that, a simple request to translate the /en directory (if this is the localized one) should be enough for most translators, and allow a continuous maintenance of the site for those available without much trouble for them. A simple warning mail would suffice. To go a little bit further, maybe a list of the links in the site should be mandatory and perfectly distinguished from others (local ones) and automatically updated so that someone like me doesn't have to test all the previously existing ones just to verify that most of them are broken or out of date. Besides this, for the experts or others alike, there should be an option, somewhere, to create or upload (?) there own ideas. Subject to approval from the responsible (the one in charge;-) ), of course. Above all, please keep it simple. Best regards, Pedro --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org