Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Jan,

2010/12/16 Jan Holesovsky <kendy@suse.cz>


Only one problem I can think of is the time; I am not sure if I can get
that 100% before the final release, so - it might happen that the
wikihelp will be English only at the time of 3.3 final, but filed with
the translated versions as soon as the above works (but it is an online
thing, so the deployment can be independent of the release date, there
is still room for improvements).  We will have the translated helppacks,
so hopefully it is not an issue.


I think online help must be available in all languages - it is a stopper, if
it isn't. Otherwise the lang teams will not ok the release thus only the
English version will be an official and tested release, and all the rest
will be untested. Think what that means for adoption of LO in enterprises
and government sector. Not good at all. For all other languages 3.3 seems to
be a preview what a LO will look like in 3.4, and not a full featured
version, a kind of LO beta.


This is a very good question.  In the current implementation, I do not
treat embedding in a special way, and just copy the text there directly.

The following is the page you have shown on the screenshot:

http://help.libreoffice.org/Writer/Shortcut_Keys_for_Writer

Ie. the 'Some shortcut ...' text is directly there, not an embedded
string.

If we want to address this, it is of course solvable too; the only
problem might be that for everything that is supposed to be embedded, it
has to have a special page, like Embed:Some_id, an in the text, it would
be used like {{Embed:Some_id}}.

For example, a text like:

file swriter/file1.xhp:
 <paragraph ...><variable ..."something">Something to
embed</variable></paragraph

file swriter/file2.xhp:
 <embed href="...file.xhp#something>

would in the wiki look like:

Page Embed:file1_something
 Something to embed

Page Writer/file1
 {{Embed:file1_something}}

Page Writer/file2
 {{Embed:file1_something}}

Documentation team - is that acceptable for you?


The transport of (English) help from wiki back to xliff/po must get all the
keywords references, links etc. How is that handled? Will the index in LO
offline help work after such a backport from wiki? This is of major
importance. Offline help without index and table of contents etc. is not
usable.

Kendy, why do you have to rush at this online solution for 3.3? I propose to
leave things as with OOo for 3.3, with help packs as separate downloads if
they are too big to be included in the international package. In the
meantime you can get the conversion procedures working so that no metadata
from help gets lost and on the road to 3.4 all the teams and LO projects
decide about the future of LO help system.
What you are driving at is having a non-fully-working solution for 3.3 with
already some decision in place at very short notice (and such decisions
mostly lead to headache) and then decide for future. What I propose is a
fully working solution for 3.3 with enough time later to decide and make a
new system working fully for the 3.4 release.

Lp, m.

-- 
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.