I am going to start this thread as an outreach for assitance with Documentation in a couple languages.
Today I needed to reference some articles in Spanish for a user here on the forums, While selecting the language in the far right corner I was met with a mix of English and Spanish.
The image below shows the “es” for Spanish while everything is in English with the “Quick Links” is in “Documentos Rapidos” .
I’m assuming this is filler so the page is not blank.
There are other examples here but I would rather know what it would require to help the team update these with the proper language. I could potentially help with other languages down the road. What tools are used and how the process works.
I’m going to go through it, and I have already signed up. So I’ll update this thread with questions and issues I come across. Can anyone provide more information on getting started?
Yeah, I appreciate that. I’m looking through and hope to cover about a page a day. How often would the sites get updated to show relevant/updated information?
I am not sure about that, maybe someone from docs team can answer that better. I remember it being less than a week but that was before migrating to GitLab.
Indeed, there is some time lap between one makes translation (in Weblate) and the translation is published on the Fedora Docs site. Because Weblate pushes the translation at a certain time to the translation repository and the Docs site is built also at another certain time(s).
If your translation is not published within a couple of days, you can file a ticket or let us know in the #l10n:fedoraproject.org[1] on Fedora Chat.
Hi all, just started looking into the Spanish translations.
There’s one string which I didn’t feel extremely happy about, but the others should be ok I believe.
Did you sign up already? I was looking at trying to update the Quick Docks (Documentos Rapidos) in Spanish, because. . .There isn’t one? Do you think you can help there too?
Yup, this is the index, isn´t it?
As I said there’s one string that I wasn’t 100% happy about mainly because there were too many IT specific terms. I’m Spanish, but IT-wise I’ve always worked for the same US company, so there’s many times where I might struggle to find the Spanish way of saying something because I’m too used to the English terms
While the Original Post was centered around a translation issue with the Docs, this next post brings up a problem with the Nvidia GPU as a Primary GPU, a function which only works under X11 and not Wayland.
Fedora ships Wayland by default, but Users expectations are different depending on their experience with Linux systems.
The documentation references Xorg and X11 several times including editing of config files, but I believe understanding these nuances from a new user perspective is hard, and requires knowledge of the Distribution that many do not have or understand.
The first image has an invalid text. The server would not automatically be set to xorg, but would only work when logged in using X11/xorg.
The second paragraph in the second image seems important to me. Users should be aware that fedora discourages users installing the drivers from any location other than rpmfusion. Maybe the first sentence of the first paragraph should be changed to indicate that these steps have been verified to work on current fedora releases and not a specific version.
Your commit seems to have covered most of that, but I sent you a PM about additional changes.
I think adding how to troubleshoot, this would be useful considering most new users naively skip the 3rd Party Repos step, or do not have the necessary codecs.
@computersavvy What do you think? Any other contributors welcome.
Since VLC is now in fedora but is stripped of the restricted codecs and those are available in 3rd party repos it would be worth a comment to that effect.
I would suggest a note under the installing section to refer users to rpmfusion.
i was thinking the same. I also had the thought of including flatpaks? Since there is a move towards them. . . I still feel a rewrite of that doc is important becasue of the lack of understanding of the bylaws.
I am seriously hesitant to add flatpaks except as a general topic since most are not fedora created but come from flathub (a 3rd party repo) and do not undergo the fedora QA and testing. Think the recent xz incident with a package from directly upstream!
If the only flatpak source were fedora it would be different.
As far as VLC is concerned now the only apparent issue is the restricted codecs and otherwise that doc seems fine.
Fedora Flatpaks require a flatpak runtime extension, for example shipped by rpmfusion.
There is not much drive to do this, so Flathub is used.
I think Fedora Flatpaks have a real purpose though, and this could be documented. (A consistent and safe build environment, SELinux support (?), a single runtime, 2nd eyes looking at it).
@computersavvy I think we need to create a new Quick Docs page for the Wayland-able Explicit Nvidia Discrete card. Since you’ve tested this recently and I will be testing next week. Would be a good contribution to the Docs, ofcourse I’ll rewrite in several langauges as well.
@computersavvy I am currently also testing this out at the moment, and so far the Desktop is “running” explicitly under the Nvidia card, although I see different results for usage of gnome-shell as I only see about 2MB of usage. I need to further test applications and some more to see if this is effectively reproducible.
If so, Would you like to participate in creating the Quick Docs for this ?
On another Note :
I have a PR in for changes I made to the Quick Docs, yet have not see any movement on this. These first 2 pages were a test for me so i might gauge how the process works, but it’s been 7 days since the PR and 21 days since the fork, so maybe I made a mistake somewhere?
If docs-team Could provide insight, I have about 10 pages I would like to work on in 3 languages and am close to finishing some translations for these.
If @mattdm Can provide some insight it would be appreciated.
!
bylaws.