Hi, I am a member of openSUSE Chinese team. We used to work on a
translation project of openSUSE documentation on Transifex and here are
a lot of translation done. Link:
https://www.transifex.com/opensuse-doc/opensuse-manuals/
However, here isn't a way to read any translation on
https://doc.opensuse.org/ . And the Transifex project was not active for
a long time.
My questions are:
1. Could you add translation support to https://doc.opensuse.org/ ?
2. Does it use GNU Gettext (po) or other technology? Or it just doesn't
support any translation?
3. Could you add a project for documentation on https://l10n.opensuse.org/ ?
4. Can we contribute translation through Github if here is no other way?
Thanks!
--
Guo Yunhe
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
Hello,
I ran today into the issue
https://bugzilla.opensuse.org/show_bug.cgi?id=992375
However, the documentation
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.re…
is not updated as proposed in bugzilla/github.
Is there any reason for not updating the online documentation? I
highly recommend to generate and update the documentation since
Google is referencing it.
Best Regards,
Heinz
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
(On mentioning this on [opensuse-web] it was suggested to discuss here as
possible alternative to simply filing a bug.)
https://lists.opensuse.org/opensuse-web/2017-08/msg00000.html
>From that post:
[quote]
>>> The easiest way to report a documentation bug is: scroll up to the
>>> headline (in this case "2.2.1.2 The Boot Screen on Machines Equipped
>>> with UEFI") and click the "Report bug" link right of the headline.
...
>> Thanks! But for your reply I'd never have seen that:
>> http://fm.no-ip.com/SS/Suse/docOSorg201707.jpg
> Oh yeah, grey on light grey is a great choice :-/ (at least it becomes
> slightly more readable if you hover it)
[/quote]
Why must opensuse.org copy the awful legibility of most of the rest of the
Internet by using tiny gray text and tinier still gray links, or green links
that don't pass any WCAG color contrast test? Why shouldn't it be better, both
respectful of user settings, and highly legible?
Web claims of "too much contrast is bad" pale in comparison to overall poor
legibility. People with too bright/contrasty displays can turn back those
settings. Those whose are properly set shouldn't need to do anything because of
some eagle-eyed stylists' preferences, and those who need more are unable to
dial up past 100%, or may already be at 100% to start with - lots of displays
shipped with settings at 100% so as to stand out alongside competitors on retail
display shelves in brightly lit stores (probably what caused stylists to make
the too much contrast is bad claim in the first place).
#439539 openSUSE green for link text is bad:
http://webaim.org/resources/contrastchecker/
So are gray text and sub-default text size:
http://www.w3.org/2003/07/30-font-sizehttp://terrillthompson.com/blog/589https://backchannel.com/how-the-web-became-unreadable-a781ddc711b6https://jebswebs.net/blog/2013/07/whats-with-all-the-gray/http://contrastrebellion.com/https://www.sitepoint.com/community/t/why-are-so-many-sites-using-gray-text…
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-doc+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-doc+owner(a)opensuse.org
