Boen, Jan - janb

I've founded in comments part of i18n/i18n.php some instructions to add a new localisation :

"

How to create a new localization?

 *
 * With each release of YACS a set of templates files (.pot) are generated in directory i18n/templates.
 * To create a new localization you have to:
 * - create a sub-directory in i18n/locale (see below)
 * - use the msginit command to create in the new directory a set of .po files out of .pot template files
 * - use poEdit, or any text editor, to populate .po files
 * - copy the manifest.php file from the 'en' locale, and adapt it for your new locale
 *
 * To name a new locale, you should follow best practices describes in RFC3066 and use any of following options:
 * - language code as defined by ISO 639; e.g., 'en' for English, 'ar' for Arabic, or 'zu' for Zulu
 * - language code, followed with an hyphen '-', then a country code as per ISO 3166-1, lower case; e.g., 'en-uk', 'zh-cn' "

 

---

Alexis Raimbault webmaster free-lance

How do you convert the .po file into a yacs xxx.mo.php file after translation?

Hello Jan !

• the covers section must have little name 'covers' (in fact the title might be anything else, it's the little name that is important) ;
• in the configuration of the home page, you have to chose to use the cover page (including it's title or not).

Hope that helps.

---

Alexis Raimbault webmaster free-lance

Jan: That's good news, thanks for your feed-back.

Hello Jan, 'glad you are still around

Actually the behavior of yacs has not changed that much in this area, so I am puzzled as you are.

For the second site, i have been able to access the control panel http://simwar.sbv54.net/simwar/control/index.php

Can you authenticate there, then change the path to root from / to /simwar/ instead? If this change allows the control panel to render properly, then it means that the symbolic link that used to exist for your virtual site does not exist anymore.

 

 

Christian:Thanks for that hint.

Not really the solution I'm looking for but if this is all that is possible with YACS today then so be it.

Joomla has got a lot of features for multi lingual web sites but I don't like the way you operate/manage a Joomla site so I'm trying to get it working with YACS.

No problem with the English

Hi,

 

Have a look at http://locje.sbv54.net/

As you can see all Tabs (and content) are in Dutch/Flemish.

We would like to rename the tab "Home" so it says e.g. "Thuis".

 

Thanks,

 

Jan

Your page was a private page, but with anyone to discuss with you.

Now it's a page in support

---

Agnès
Il n'y a pas de problèmes, que des solutions.

Christophe Battarel: Hi Christophe, testing is one thing. Adapting another. I downloaded and deployed your Joomla package. Let's see what happens when I try to use it. What are the limitations you know of?

Page has been created

alors la!! rien à redire!!!

Jan : I am glad to support your business through the yacs project!  See you

Boen, Jan : your have to wait one day for first stats. Is it better today.

Display the html source of one page to check if tracker is here.

---

Alexis Raimbault webmaster free-lance

Jan: My suggestion was only aiming to replace some text by a background image. If you want to get a clickable image, why not derive a skin of your own? You could then change template.php to customize it to your needs, with code like the following:

echo '<p id="header_title">'
 .'<a href="'.$context['url_to_root'].'" title="'.encode_field(i18n::s('Front page')).'" accesskey="1">'
 .'<img src="path/to/logo.png" /></a></p>'."\n";

Bernard Paques:Thanks

Indeed in some folders you can just browse around.

OK. Found the complex interface setting and changed to it from enhanced interface.
The naming is a bit misleading though.

Jan: to fix the lack of codec the best option is probably to install VLC, from VideoLan since this small piece of software has almost every codec available on Earth. Also, I will launch some non-regression tests on the development machine to ensure that collections are ok. Thanks for the feed-back.

Jan: inbox is supposed to be at the same level than other directories, just below the YACS installation directory.

More exactly, if the root directory is yacs, then put the update archive in yacs/inbox/yacs.

The version 6.10 will also allow for a manual update of the staging directory, in directory scripts/staging.

This means that different methods are available for the staging:
- updated files are staged individually through the network - configure the reference server, and let YACS do the job - the most simple approach, but may be proven impraticable with heavy updates or poor network
- upload of an entire archive - it is exploded by YACS in the staging directory - quite simple, but requires support for 6M files, plus enough CPU time to explode the stuff
- explode of a local archive - that you would have deposit in inbox/yacs through anothe rmean, such as FTP - still requires enough CPU time
- manual upload of files in the staging store - the ultimate solution in difficult situations

After the refresh of the staging directory, all you have to do is to trigger the update, at scripts/update.php, to finalize the actual update of running scripts.