On Mon, Jan 6, 2014 at 6:56 PM, Jan Høydahl <[email protected]> wrote: > I'm a bit short on time right now. > > Perhaps the Norwegian contributors should first discuss a strategy for the > web site, and then the first of us who volunteer some time will execute the > plan. > > The old web site is sadly out of date and gives a bad impression for for > users and sends an unfortunate signal that "this product is not actively > maintained". I'm tempted to start afresh with a brand new copy of the site, > starting with a front page translation, and then adding more pages. Perhaps > some of the old content may be re-used, but it will take some effort to QA > all of it, check whether listed companies still provide support etc. >
It can always be done a part at a time. The pages that are not translated would then be in English. For example, even just translating two pages, the home page and the download page, will be an improvement. -Rob > What do you Nowegian guys in here think? > > -- > Jan Høydahl, search solution architect > Cominvent AS - www.cominvent.com > > 6. jan. 2014 kl. 15:17 skrev Rob Weir <[email protected]>: > >> On Sat, Jan 4, 2014 at 3:11 PM, Jan Høydahl <[email protected]> wrote: >>> Hi, >>> >>> Now that 4.1.0 is approaching for Norwegian too, we should refresh >>> http://www.openoffice.org/no/ >>> >>> Should we simply start with http://www.openoffice.org/nl-template/ ? Looks >>> pretty up to date except the social media logos missing. >>> >> >> Actually, the current base is here: >> >> http://www.openoffice.org/xx/ >> >> That has the correct social media logos. But the news stories on the >> right are not current. >> >> I wrote up some instructions/hints on how to translate the website. >> It is HTML and MDText files, with no Pootle involved: >> >> http://openoffice.apache.org/website-native.html >> >> If you are interested in doing this, let me know and I can email you a >> ZIP of the files. >> >> >> >> Regards, >> >> -Rob >> >>> -- >>> Jan Høydahl, search solution architect >>> Cominvent AS - www.cominvent.com >>> >>> 2. feb. 2013 kl. 02:43 skrev Rob Weir <[email protected]>: >>> >>>> On Fri, Feb 1, 2013 at 6:54 AM, Jan Høydahl <[email protected]> wrote: >>>>> Hi, >>>>> >>>>> I have not been able to follow-up on this. >>>>> The Norwegian site is lacking sadly behind, not even promoting the newly >>>>> released 3.4.1 :( >>>>> Any updates on best-practice for keeping translations in sync, other than >>>>> what you described below? >>>>> >>>> >>>> There are a few approaches: >>>> >>>> 1) Some do a complete translation of the www.openoffice.org homepage, >>>> as well as the core pages linked from that page. For example, see >>>> the Spanish homepage: http://www.openoffice.org/es/ >>>> >>>> 2) Some maintain a full website, but following a different design, >>>> e.g., French: http://www.openoffice.org/fr/ or German: >>>> http://www.openoffice.org/de/ >>>> >>>> 3) Some keep a very basic website, translating the home page only and >>>> then linking to the English pages for the the deeper pages, e.g. >>>> Brazilian Portuguese: http://www.openoffice.org/pt-br/ >>>> >>>> There may be other approaches, but those are the ones that I see in common >>>> use. >>>> >>>> Personally, I think a nice approach is to start with approach 3), and >>>> then to add to it over time to get something more like 1). >>>> >>>> If you or anyone is interested in this, let me know and I can put the >>>> right files in place to translate. >>>> >>>> Regards, >>>> >>>> -Rob >>>> >>>> >>>>> Any of the other Norwegian translators want to give it a try? >>>>> >>>>> -- >>>>> Jan Høydahl, search solution architect >>>>> Cominvent AS - www.cominvent.com >>>>> Solr Training - www.solrtraining.com >>>>> >>>>> 20. okt. 2012 kl. 15:36 skrev Rob Weir <[email protected]>: >>>>> >>>>>> On Sat, Oct 20, 2012 at 7:09 AM, Jan Høydahl <[email protected]> >>>>>> wrote: >>>>>>> Hi, >>>>>>> >>>>>>> The Norwegian national website @ http://www.openoffice.org/no/ is in >>>>>>> pretty bad shape. Most links and content in the left menu is outdated >>>>>>> and/or wrong. I'd like to start by moving the old homepage to /no/old >>>>>>> and start a pure translation of the official home-page into Norwegian, >>>>>>> much like they have done for /es/. Then we can start filling in >>>>>>> relevant national content step by step. >>>>>>> >>>>>>> I'm aware of the Apache CMS system, is there some kind of guide for how >>>>>>> to manage a translation, both initially and keeping it up to date? Or >>>>>>> is it all manual? >>>>>>> >>>>>> >>>>>> I've made a copy of the English content and put it into a new >>>>>> nl-template directory here: >>>>>> >>>>>> http://www.openoffice.org/nl-template/ >>>>>> >>>>>> We can use this as a basis for new translations. >>>>>> >>>>>> If you are familiar with SVN you can check it out as: >>>>>> >>>>>> http://svn.apache.org/repos/asf/incubator/ooo/ooo-site/trunk/content/nl-template >>>>>> >>>>>> Then for your working copy, I'd recommend doing an svn copy to a >>>>>> different name, like "no-new". When you are done with the translation >>>>>> then you can send a patch file which we can apply. >>>>>> >>>>>> Or, if you prefer I can send you a ZIP file of that directory (< 2MB) >>>>>> and you can send me a ZIP of the translation and I can take care of >>>>>> checking it in. >>>>>> >>>>>> Of course, doing this kind of non-linked copies will require ongoing >>>>>> effort to avoid divergence. So we should also continue thinking of >>>>>> how we can improve this process. >>>>>> >>>>>> Regards, >>>>>> >>>>>> -Rob >>>>>> >>>>>> >>>>>>> -- >>>>>>> Jan Høydahl, search solution architect >>>>>>> Cominvent AS - www.cominvent.com >>>>>>> Solr Training - www.solrtraining.com >>>>>>> >>>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
