Add @LOCALE@ macro for translation

[mizunashi-mana]

From Issue #158

Feature

The reason why I chose the name, @Locale@

First, I chose @lang@ .
But, @lang@ conflicted with translation plugin's. (If we use page template and write {{page>@LANG@}} on this page, when a instance be created with the template, it is transformed to {{page>en}} or others.)
So, I picked this.

However, I hesitate to judge.
There are @lc@, @INC_LANG@, etc.
Do you have better name?

Macro change flow

1. Getting HTTP_ACCEPT_LANGUAGE from HTTP header
2. Try to translate page name and test to exist the page
3. If the page exists, this macro value is set
4. If there are many accept languages, check each items in the order
5. Else the macro sets wiki default

Changes

• apply_macro function is changed to use resolve_pageid function.

[michitux]

What about HTTP_LANG or BROWSER_LANG in order to make clear that the language code is from the current request? All in all this seems to be okay in my opinion.

[mizunashi-mana]

Thx! BROWSER_LANG seems more than to me!
I will fix.

[mizunashi-mana]

Sorry...
I wrote codes with less survey.

I fixed HTTP_ACCEPT_LANGUAGE pattern based on
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4