<br><br><div class="gmail_quote">2010/12/14 Michael Meeks <span dir="ltr"><<a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
On Mon, 2010-12-13 at 14:33 +0100, Jan Holesovsky wrote:<br>
> I think the biggest issue is the offline editing; and I think here we<br>
> can use the Wiki Publisher<br>
> (<a href="http://extensions.services.openoffice.org/project/wikipublisher" target="_blank">http://extensions.services.openoffice.org/project/wikipublisher</a>) to<br>
> edit the pages in LibreOffice.<br>
<br>
</div> Ooh - that is an interesting idea :-)<br>
<div class="im"><br></div></blockquote><div><br>I believe that is not a good idea. It will reformat the content and make changes tracking a nightmare. Also, translating from changed US wiki to other languages will be a nightmare.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
> I did not test it yet, but if the<br>
> extension misses the functionality to merge the changes done in the<br>
> wiki, it will be easy to plug it to LibreOffice document merge feature.<br>
<br>
</div> Sure; but I suspect there are issues around dictionaries, and other<br>
helpful tooling that make translators lives easy :-)<br>
<br>
Anyhow - it'd be great to collect the ideas for flows into the wiki<br>
page; quite possibly there are several flows possible, and we can choose<br>
per language. eg. if there is already a near-perfect translation, I can<br>
understand people might not want it 'vandalised' by others changing<br>
it :-) On the other hand, if there is simply no translation at all<br>
currently for a language, almost anything might look better than nothing<br>
- so perhaps an in-wiki-editing policy might make sense.<br>
<br>
Either way, I for one am excited by the idea of having something that<br>
is easier to edit and improve in English, although clearly the more, and<br>
higher quality help in English we have, the harder the (already huge)<br>
help translation problem becomes I guess.<br></blockquote><div><br>I don't have time to go to wiki and edit it, please someone do it if you deem my thoughts worth published there.<br><br>I guess from all the discussion here we see that the LO developers and documentation team wish to get help onto a new platform, where it will be easier to maintain.<br>
<br>On the other hand the localization teams who have invested big resources into translating the huge help system wish to continue working like before in a Pootle or similar environment.<br><br>I propose you develop a system to have English help editable on wiki but fully transportable back to the po/xliff system (interchangeable).<br>
All the translations would start from the English po/xliff help files and decide whether to<br>a) strictly translate English help (like we Slovenians decided) and keep working with po/xliff files; the online help would be updated from these files at least with every minor and major release;<br>
or<br>b) develop their own help in the wiki and never go back again;<br><br>Before I go on I need an answer to a question. I tried the help in RC1 and it seems that help items do not get passed to wiki i.e. the default module help page opens even if you press F1 in a certain dialog (the previous bundled help showed that definite topic in the help). Is this how the wiki help is envisioned? If it is, one need a lot of searching to even get to a certain topic and this makes the help totally unusable. If this is the case the wiki help should only be a web version of the bundled help, just a copy made after every release from the release translations.<br>
<br>Lp, m.<br></div></div>