Carsten Klapp wrote:
[...]
> The formal version would be ideally targeted towards businesses and
> other organizations who may be interested in starting their own
> PhpWiki, and who otherwise would not even be able to consider using
> PhpWiki because it currently employs the informal German language;
that's a good idea, but more important would be to have a _complete_
translation of the texts, i.e. the formatting help was not translated
in 1.3.4 IIRC, and I believe there were other language related
glitches.
I already considered translating the missing texts, but since the
users understood the english version pretty good, I didn't continue.
> Also, I would like to see any formal notation (Sie) as the default for
> a German PhpWiki installation, but we can continue to offer the
The disadvantage is that the delay of the German versions likely
would increase.
I agree with you that for a business environment in Germany the
presentation of PhpWiki should be smoother. But that's IMHO more than
the formal/informal question, a more foolproof introduction to
PhpWiki would be useful.
I offered Wikis for three different groups because I was sure that
they could profit from the simple cooperation principle, but found it
very difficult to get them accepting it. The main problems were:
- too lazy to read the explanations
- didn't understand the explanations
- didn't dare to press "edit" to try how it works
- didn't want to share information
For _non-technical_ people, it seems to be a real hurdle. For the
technical versed, it might be not so important to have a German
version at all.
BTW: Only one of the three Wikis was really alive and (hopefully)
useful for some period. Today I use Wiki as a kind of CMS or PIM, and
I really love it because it's simple and has an open data format.
Another problem in a business environment could be the lack of access
control (and user authentication). I didn't check the nightly
snapshot for a while, is there any progress with PagePermissions?
Oliver
|
