Re: [l10n-dev] Support addresses in Help

[Clytie Siddall]

(Cc to Uwe for Help)

Reply below...

On 03/07/2008, at 5:30 PM, Gregor Hartmann wrote:

Hi,



so here is my comment:



could I assume e.g. that all localiteable links start with http:
or all not localizeable links refer to xhp fules (end with .xhp)?



Best write an issue to me so I will get to it for sure.

Gregor


Clytie Siddall schrieb:

sorry for my late reply, i was notified in a mailthread this question caused and did not look close enough where it was originated. if there is any way to tell which links are localized and which are not I can add it to gsicheck. please let me know. But be aware that this rule must be correct for ALL links, no exception allowed.

Hi everyone :)

Thankyou for any help you can offer with this. :)
from Clytie
Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n

When we translate the Help, there are quite a few strings where the user needing help is referred to mailing lists, webpages or other support resources. The original string contains the English resource, which is not useful to users of other languages. Even if it were possible for all of these resources, they do not have language-bars, or content-negotiation which automatically provides a page in the correct language for that user. I have found that if I replace the English resource with the one that is useful for my language, e.g. replace <[EMAIL PROTECTED]> with <[EMAIL PROTECTED]>, gscheck reports that as an error. If I add a separate link for the localized resources, gsicheck also reports that as an error. How can we deal with this problem? Our users need the localized Help to direct them to localized support resources, not English resources they can't read.

Suggestions:

1.
Gregor, would it work to tell gsicheck to accept two-letter sub-domains:

.openoffice.org
vi.openoffice.org
fr.openoffice.org
ja.openoffice.org

[EMAIL PROTECTED]
[EMAIL PROTECTED]



http://openoffice.org
http://vi.openoffice.org/about-downloads.html



http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide
"http://wiki.services.openoffice.org/wiki/Documentation/vi/ASIC_Guide

I think that's the recommended format. Is that correct?

2.








from Clytie

Vietnamese Free Software Translation Team
http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
______________________________________________________

It reverses the logical flow of conversation!
Why?
No.
Should I top post?

http://www.google.com/search?q=%22top+posting%22

(and ignore any other changes in the link if it has a 2-letter sub- domain added)? Then that would work for both websites and mailing-lists. Wiki pages are a bit more difficult. Set a "localize" tag we could add to any localized link, so gsicheck recognizes it (messier, means an XML tag which Help can ignore). I'd like to get Uwe's advice, and input from other language-teams, before submitting an issue. Uwe, what do you think would work best in the Help (to avoid problems ;) )? My localization colleagues, where do you see localized links being useful? Until we have content negotiation on the website, I want to be able to specify localized webpages, mailing list and forum addresses, at least.

PGP.sig
Description: This is a digitally signed message part