Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.228 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [WWW] Translating branding and navigation
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <2ab5a4378a43d1a5eb1e5b8d6c37c63a@hdsnet.hu>
Date: Thu, 12 Apr 2012 12:04:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3CFC5B7-B2F6-450E-94A9-CC0500D52AAF@comcast.net>
References: 
 <1540939746.92888956.1333573080817.JavaMail.root@zimbra60-e10.priv.proxad.net>
 <0101A827-4CAE-43CB-B5B7-9E3DA4E5E99F@comcast.net>
 <4F808C0D.2000607@apache.org>
 <A17CA378-B37E-4ACF-B88A-81D3B4288003@comcast.net>
 <3BAC9822-59A3-420B-B5A6-40DC8D183F89@comcast.net>
 <2ab5a4378a43d1a5eb1e5b8d6c37c63a@hdsnet.hu>
To: ooo-dev@incubator.apache.org

Hi Zoltan,

HU is now enabled for translated branding and topnav.

Regards,
Dave

On Apr 12, 2012, at 11:21 AM, Reizinger Zolt=C3=A1n wrote:

> Hi,
> Please make hu next.
> Thanks,
> Zoltan
>=20
> 2012.04.11 17:47 id=C5=91pontban Dave Fisher ezt =C3=ADrta:
>> Hi -
>>=20
>> es, de, nl, fi, pt-br, ru, and ja are now setup for committers to
>> make translations to brand.mdtext and topnav.mdtext.
>>=20
>> I still have the question about Chinese / zh split regarding
>> traditional / simplified (Taiwan / Mainland)
>>=20
>> Next languages? cs, hu? Please respond for the next NL set.
>>=20
>> brand.mdtext
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> home:           home
>> search:         search
>> name:           Apache OpenOffice (incubating)
>> tagline:        (incubating) | The Free and Open Productivity Suite
>> logo:           AOO_logos/OOo_Website_v2_copy.png
>> domain:         www.openoffice.org
>> divid:          bannera
>>=20
>> topnav.mdtext
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> divid:  topnava
>>=20
>> - [Product][m0]
>> - [Download][m1]
>> - [Support][m2]
>> - [Extend][m3]
>> - [Develop][m4]
>> - [Focus Areas][m5]
>> - [Native Language][m6]
>>=20
>>=20
>> [m0]:     /product/index.html
>> "Apache OpenOffice product description"
>> [m1]:     /download/index.html
>> "Download OpenOffice.org"
>> [m2]:     /support/index.html
>> "Find Support for OpenOffice.org"
>> [m3]:     /extensions/index.html
>> "Extensions and Templates for OpenOffice"
>> [m4]:     http://incubator.apache.org/openofficeorg/get-involved.html
>> "Get involved in Apache OpenOffice (incubating)"
>> [m5]:     /projects/accepted.html
>> "Apache OpenOffice development focus areas"
>> [m6]:     /projects/native-lang.html
>> "Apache OpenOffice in your Native Language"
>>=20
>> Regards,
>> Dave
>>=20
>> On Apr 7, 2012, at 1:55 PM, Dave Fisher wrote:
>>=20
>>> Hi Andrea,
>>>=20
>>> On Apr 7, 2012, at 11:48 AM, Andrea Pescetti wrote:
>>>=20
>>>> On 05/04/2012 Dave Fisher wrote:
>>>>> Here is what you would do to effect all of the FR site at once for
>>>>> translated branding and navigation buttons:
>>>>=20
>>>> Thanks for the detailed instructions, that should definitely be put =
on
>>>> the wiki. I tried to apply them to the IT site:
>>>> http://svn.apache.org/viewvc?view=3Drevision&revision=3D1310806
>>>> Everything seems OK, but I can't see the changes at
>>>> http://ooo-site.staging.apache.org/it/ or
>>>> http://www.openoffice.org/it/
>>>=20
>>> I think that there was a hiccup with the CMS. Joe asked that you =
trigger your build again.
>>>=20
>>> I went ahead and added the files for French. I also made a change to =
a comment in ooo-site/trunk/lib/view.pm. This is a trick that will cause =
the staging build to do a full build causing all of the IT and FR sites =
to be changed to the new SSI.
>>>=20
>>>=20
>>>>=20
>>>>> (1) Create trunk/templates/fr/ssi.mdtext from templates/ssi.mdtext
>>>>> ... Change /brand.mdtext to /fr/brand.html Change /topnav.mdtext =
to
>>>>> /fr/topnav.mdtext
>>>>=20
>>>> I did this, just replacing "fr" -> "it".
>>>>=20
>>>>> (2) Copy /trunk/content/brand.mdtext from content/brand.mdtext
>>>>=20
>>>> Here I actually copied content/brand.mdtext to =
content/it/brand.mdtext
>>>> (which is probably what you meant) and edited accordingly.
>>>>=20
>>>>> (3) Copy /trunk/content/topnav.mdtext from content/topnav.mdtext
>>>>=20
>>>> Same as (2).
>>>>=20
>>>>> Commit all three changes at once and the whole of the FR part of =
the
>>>>> site takes these changes at once. O(1) operation.
>>>>=20
>>>> I committed, the build was triggered and succeeded but I don't see =
the
>>>> changes.
>>>=20
>>> The trick with lib/view.pm may be required.
>>>=20
>>>>=20
>>>>> If you would like I'll create the mdtext files and then you can
>>>>> translate.
>>>>=20
>>>> This would probably be helpful to all native-lang projects, since =
even those not familiar with SVN could simply submit the translated =
version of their mdtext files.
>>>=20
>>> Yes, but I want to wait until we do a couple and make sure all the =
proper details are covered.
>>>=20
>>> We may be adding a news.mdtext and index.mdtext for the main index =
page, but that will be a separate thread of work.
>>>=20
>>> And it is not a reason to wait. I'll look into doing it for many NLs =
this week.
>>>=20
>>> Here is a list of the next NLs to setup:
>>>=20
>>> es, de, nl, fi, pt-br, ru, ja
>>>=20
>>> This scheme only goes a single directory level deep. Is a single =
translation viable for both zh_cn and zh_tw? If not then the two sites =
will need to be separated. I want to be careful how that is done.
>>>=20
>>> Regards,
>>> Dave
>>>=20
>>>>=20
>>>> Regards,
>>>> Andrea.
>>>=20
>=20