This page is biased with my specific requirements --
BenoitAudouard 20031217
English is the language of choice to get people to cooperate.
- Ahem... Don't tell this to people working for French speaking Agency (like me)! ;-) -- ProgFou
This is a synthesis of identified requirements, with some comments / how-to / details of possible implementation
| Requirement | WikiNi | WackoWiki | Weight | Comment | planned in wikini |
| tables | 0 | 1 | 3 | Would be nice to have : conversion from Word, default format |
? |
| bold, italic, ... | 1 | 1 | 3 | Not the same syntax, easy conversion (Openwiki compatibility for Wacko) |
? |
| themes | 0 | 1 | 1 | Nice tabs in WackoWiki, would require a theme editor to be fully usable or at least documentation how-to-make/change a theme |
? |
| external links | 1 | 1 | 2 | nicer in WackoWiki (identified with image) but open in a new window (could be parametered) [See LienInterWiki] |
? |
| preview | 1 | 1 | 3 | planned to reappear in WackoWiki R4
"Save & continue" as in egroupware would be fine (I don't understand : it exist in WikiNi, no ? [nope : there's Save, re-edit, not Save & continue editing : you've got to Save then click on Edit after display]) |
? |
| localization navigation | 0 | 1 | 3 | what's not yet available in WackoWiki :
- for WikiLinks (well just choose an international name for page, then take into account suffix to choose the appropriate language) : would require an ID for each page and an alternate name in each language (unique ?)
- from the start (depending on browser configuration, requires registering to select it, a flag for language would be better to understand navigation) |
? |
| Localized-content management | 0 | 0 | 2 | manually it's nearly possible, the biggest problem is with displaying correct characters and editing other language (entities...) |
? |
| translation management | 0 | 0 | 2 | manually, adding links for pages in other languages it's possible to identify those pages that need translation (and make navigation) |
? |
| DocBook extraction | 0 | 0 | 2 | implementation available (tuned for wikini) |
? |
| Automatic ToC | 0 | 1 | 1 | With anchored links to titles [See AncresAutomatiquesPourLesTitres] |
? |
| Boxes for code | 0 | 0 | 3 | I do not want limited number of lines, the scroll works ok in WackoWiki [See AdaptationDeLaTailleDesFenetresDeCode] |
? |
| Wiki Edit | 0 | 1 | 1 | ctrl-B for bold text... well that's not that usefull... |
? |
| Total Score | 10 | 10 | | welcome to fan school on sunday afternoon... ;-) |
http://www.egroupware.org/ Save / Preview / Save & Continue in their wiki (limited functionalities)
- preview appears below the Wikiedit zone, that's nice...
- Save & Continue : it's the possibility to have an intermediate save (in case the network goes down, or someone else is editing it, ...) : it redirects to edit after saving instead of redirecting to view. This is useful after a preview that is correct to continue adding things to a page (well it avoids one click for the lazy and one download... nice for those on 56k modems...).
WackoWiki only manages those pages in the user's configured language
- <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /> for French
- <meta http-equiv="content-type" content="text/html; charset=Windows-1251" /> for Russian
- hence a French cannot visualize Russian content at all, unless he/she switches to Russian for navigation...
- Not exactly, I'm french and I can see (but not read ;-)) Russian content without any problem (I have Russian fonts installed, Unicode fonts actually) just because they put this header correctly: this is what the browser needs to be able to switch automagically to the right encoding and font selection. The main problem here is that we can not mix Russian and French in the same page! This would be solved by using UTF-8 (the XML default charset by the way). -- ProgFou
- That's what I said : you've put language in Russian in your user settings... I can see russian font in this case as well, but then I'm lost with navigation -- BenoitAudouard
- Nope: I confirm I never put anything else than "fr, en, vi" in my language settings. My browser "sees" from the page headers that the Russian web page is using Windows-1251 encoding and automaticaly switch to this encoding (but not language!) and displays Russian text correctly using Windows-1251 compatible fonts (Unicode ones in my case). Or may be it's because you are using a Netscape 4.x (or older) browser? Those ones manage fonts mostly badly, IMHO, apparently because of the lack of a full Unicode transcoding table (to be able to use any font encoding)... Using Netscape 4.x, I had to switch to specific vietnamese encodings/fonts (in user preferences) to be able to display vietnamese, even with right headers in the web page. It's no more a problem with modern browsers, especialy Mozilla (and derivatives, I'm using Gaelon) that does a real great job (they do their job actually ;-)) on this! -- ProgFou
- I'm currently using a proprietary browser named internet explorer 6.0.2800 and this page : http://wiki.oversite.ru/ProJetuWiki?v=10dz only appears with russian when navigation is in russian as well, otherwise in French there's always wiki navigation with "Préférences | Déconnexion", so the page may be interpreted as "mostly" French. At home I'm using Galeon 1.3.x (Mandrake 9.2) and if I remember well, that's the same... I was talking about wiki user settings. Indeed, when I choose Affichage / codage / cyrillique (windows) in IE, well it works better even though I have kept wiki navigation in French (I lose the i circonflexe though, like in Benoît). By default, there's europe occidentale (ISO) -- BenoitAudouard.
Discussion area
And the winner is... !!! well no winner so far, both have advantages, both lack some things the other has, or neither (... yet) ...
I'd like to know if my requirements are legitimate and which ones have a chance to be taken into account, hence I've added a column "planned in wikini" with a priority : 3 being high, 2 medium, 1 no chance (well ...)
To prove the need for internationalization, I've asked Polish and Greek contributors to eagle-usb to add a simple acknowledgement here (Lubek Tolmidisa, please describe what are your problems with french-only sites ?). My main requirement is to add a flag that people can choose that changes at least the navigation to their language (content is the responsibility of translators...). BTW, I've got the same requirement for phpBB2 !
- well that's still too difficult so far for them (as long the navigation is not yet internationalized and buttons like 'Sauver' / 'Aperçu' and no flag to change navigation)
- They could not even reach and modify this page ;-) since 20040114 Maybe I should have told them they can use the link "Editer cette page" (Edit this page) -- BenoitAudouard 20040210