Re: [documentation-dev] External links in HC2 files

[Uwe Fischer]

Hi,

Frank Peters wrote:

Hi Sophie,

Working on the HC2 l10n of 3.0, there is some blog links (to OOo TNT 
if I remember well :) inside to give more help on special features. 
Those blogs entries are great of course, no question here, but very 
difficult for us to localized, where the wiki page links gives no 
problem.
For a quality matter, could it be possible to find a solution that 
allow us to have only localizable links inside HC2 files ? Or are 
allowed to translate the blog content to put it on the wiki (what is 
the licence) and wouldn't that break the file if the links are 
different ?

...
Uwe, maybe we should do that with some of the tips anyway (moving
them to the wiki as FAQs or Howtos)?

Currently I only see 5 occurences of links to the OOo blog:
2 in /text/swriter/guide/spellcheck_dialog.xhp
2 in /text/shared/optionen/01010400.xhp
1 in /text/shared/guide/language_select.xhp

For the 5 occurrences above, should Uwe move them to the wiki and
change the links (we have one more chance to change that before
OOo3 deadline).



what would be the correct place to copy the blog entries to? For 
example, the blog entry 
http://blogs.sun.com/oootnt/entry/adding_more_languages_to_ooo obviously 
belongs to 
http://wiki.services.openoffice.org/wiki/Documentation/FAQ/Writer/FormattingText 



But there are already some FAQ entries which cover the blog topic in 
parts or that are closely related. Just copying the blog entry would not 
look good.
And the whole page is to be divided into separate pages anyhow. And I 
don't like the idea that the entry I'm linking to from the application 
help will be changed by someone who doesn't know it is referenced from a 
certain application help page, may be adding some special developer info 
to a page that is aimed at the beginner user, or deleting some 
paragraphs because they can be found at another place, and so on.
And translators would not want to translate such a whole long page like 
http://wiki.services.openoffice.org/wiki/Documentation/FAQ/Writer/FormattingText 
just because a link exists to one subtopic.
So I would like to have separate pages for all the FAQ topics first. 
Then I can easily copy blog pages to the Wiki and mark them as this is 
linked from the application help - please do not change it too much.
And I would like to have the time to read through all the FAQ pages and 
insert links to them from the application help where applicable.
But then, we plan to publish the application help pages as Wiki pages 
anyhow, so where is the benefit? May be this: the application help 
*must* get translated,  no matter if on the Wiki or not, while the other 
Wiki pages *can* be translated.


Uwe

--
 [EMAIL PROTECTED]  -  Technical Writer
 StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
 http://www.sun.com/staroffice
 http://documentation.openoffice.org/online_help/index.html
 http://wiki.services.openoffice.org/wiki/Category:OnlineHelp
 http://blogs.sun.com/oootnt


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [documentation-dev] External links in HC2 files

[sophie]

Hi Frank, Uwe,

Frank Peters wrote:

Uwe Fischer wrote:


so back to Sophie's question. What is better (and can be done *now*):

- remove the links to external English-only web pages

no, that would mean to deprive the English audience of
this information.


I agree, and Uwe and you are giving a lot through those blog entries so 
their is really no mean to remove those links.



- translators mark the link as English page in their translations

I'd suggest that. Sophie, couldn't you do something like

... blablabla link_to_english_only_text (English only)

and change the link once you have the translation done, or even
leave it and point to the localized page from inside the wiki,
which should be possible once the migration is done (which
is due this week).


If there is no problem for us to translate the page on the wiki and let 
also the pointer to the original blog entry, this might be the solution. 
My concern is that I find that frustrating when you search for help to 
find it in a language you don't understand.



- define a new tag show in English help only

no, that would mean to deprive non-English speakers
trhat may still have sufficient knowledge of English of this
information


Yes, I completely agree with you. So let says the default is English, we 
are allowed to translate the pointed entries on the wiki and we put the 
link to the blog in the translation, so that people who understand 
English is able to discover your great work. Is it ok like that ?


Kind regards
Sophie


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[documentation-dev] External links in HC2 files

[sophie]

Hi all,

Working on the HC2 l10n of 3.0, there is some blog links (to OOo TNT if 
I remember well :) inside to give more help on special features. Those 
blogs entries are great of course, no question here, but very difficult 
for us to localized, where the wiki page links gives no problem.
For a quality matter, could it be possible to find a solution that allow 
us to have only localizable links inside HC2 files ? Or are allowed to 
translate the blog content to put it on the wiki (what is the licence) 
and wouldn't that break the file if the links are different ?


Thanks in advance
Kind regards
Sophie

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]