Re: New contributor
Hello Sajolida, I am glad there is at least one member of gnome-user-docs who uses this list to communicate with other members. I have not yet started a discussion on some things that bother me, because I had the impression this list is not used very often. With "elsewhere" you mean perhaps a chat room or something like that? I will start a discussion in a separate email to this list and we'll see if there will be any reactions. Best regards, Hannie Op 24-11-17 om 11:06 schreef sajolida: Hannie Dumoleyn: Hello, Hi Hannie! I'm the main documentation writer for Tails [1], a live operating system for privacy and anonymity based on Debian and GNOME. [1]: https://tails.boum.org/ While translating, I noticed a few things I would like to discuss on this list, hence my subscription today. I would also like to contribute as a reviewer for the gnome-user-docs. I am not yet familiar with the workflow, but I am an experienced user of git. I will send seperate emails to this list about the things I would like to discuss. Unfortunately, I've seen almost no discussion happening on this list since I subscribed years ago. I bet people working on the GNOME documentation do this elsewhere (where?). ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: New contributor
Op 27-11-17 om 18:44 schreef Petr Kovar: On Tue, 14 Nov 2017 10:26:48 +0100 Hannie Dumoleyn <lafeber-dumole...@zonnet.nl> wrote: Hello, May I introduce myself. My name is Hannie and I am a contributor (translator, reviewer, author) for both Gnome and Ubuntu. I am coordinator of the Dutch translation teams (see 1 and 2 below), and team lead of the Ubuntu Manual Project (3). Since Ubuntu (17.10) has decided to drop Unity and use the Gnome environment instead, I think it is important to translate gnome-user-docs in the Dutch language. I am working at it now, but it takes time because the strings are much longer than gui translations. While translating, I noticed a few things I would like to discuss on this list, hence my subscription today. I would also like to contribute as a reviewer for the gnome-user-docs. I am not yet familiar with the workflow, but I am an experienced user of git. Welcome to the project! I think the following page for new contributors is a good starting point and is reasonably up-to-date, though if you spot something incorrect or missing, please let us know: https://wiki.gnome.org/DocumentationProject/Contributing For reviews, I think it is best to start watching the gnome-user-docs-ma...@gnome.bugs Bugzilla user so that you get all the relevant bug mail and don't miss any request for review. Cheers, pk ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list Hi Petr, Thanks for this information. In preparation of possibly becoming a member of the gnome-user-docs-maint team, I had a look at the buglist (1), to see how it works. What strikes me is that some bugs with status NEW are pretty old (2013, 2014). Should the status be updated, or does it mean that there are still people working on it? I have also looked at the structure of gnome-user-docs (2). I am not yet familiar with the location where files are to be edited, perhaps /gnome-user-docs/gnome-help/C (filename.page)? If there is a wiki page with instructions, I haven't found it yet. The best way for me to learn Mallard is by looking at existing user-docs pages and copy tags from them. I will continue to read information on how to become a contributor. If I have any questions, I will use this list or #doc. Hannie (1) https://bugzilla.gnome.org/buglist.cgi?quicksearch=product%3A%22gnome-user-docs%22%20_id=268286 (2) https://git.gnome.org/browse/gnome-user-docs/ ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Change .page, see result
Op 04-12-17 om 19:34 schreef Gunnar Hjalmarsson: On 2017-12-04 17:59, Hannie Dumoleyn wrote: I do not know where the help files which I get when I press F1 reside, and I do not want to mess them up. That is why I stored a copy of gs-use-system-search.page in a separate directory. I can experiment with it, without messing up the branch I downloaded. Messing with the files you downloaded is exactly what you are supposed to do. yelp can't read a file which isn't located together with the other files (at least index.page must be present in the same directory). Hello Gunnar, This is the right answer :) Thanks. I already thought it was not possible to copy a .page file to another directory and then see the result of the changes I made using yelp myname.page in the terminal. I wanted to use this method to be able to experiment with text, tags, code etc. without ruining the branch I downloaded. What I can do is this: experiment with .page files from the local branch, look at the results, and if something is wrong I can delete the branch on my local machine and download the branch again from git. What will happen if I commit/push the branch with the changed .page files I am happy with. Will they be added to gnome-user-docs (patches?). So far, I have only pushed the branch with changes to the nl.po file. @Andre: thanks for the tip (Ctrl L) @Jim: your information is helpful too. At this moment I am experimenting with .page files from gnome-user-docs and gnome-getting-started, but I may also want to work on documentation of applications like gedit. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Lists
Hi, While reviewing gs-use-system-search I decided to remove "and" from the list of matching items, see last comment here [1]. I checked the style guide [2] and found this: Do not connect list items with conjunctions such as "and" or "or". If you agree, I think gs-use-system-search can be pushed to master (I will not do it myself, as promised). The one trailing whitespace, see [1], is not of great importance. Hannie [1] https://bugzilla.gnome.org/show_bug.cgi?id=791340 [2] https://developer.gnome.org/gdp-style-guide/2.32/infodesign-12.html.en ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
New contributor
Hello, May I introduce myself. My name is Hannie and I am a contributor (translator, reviewer, author) for both Gnome and Ubuntu. I am coordinator of the Dutch translation teams (see 1 and 2 below), and team lead of the Ubuntu Manual Project (3). Since Ubuntu (17.10) has decided to drop Unity and use the Gnome environment instead, I think it is important to translate gnome-user-docs in the Dutch language. I am working at it now, but it takes time because the strings are much longer than gui translations. While translating, I noticed a few things I would like to discuss on this list, hence my subscription today. I would also like to contribute as a reviewer for the gnome-user-docs. I am not yet familiar with the workflow, but I am an experienced user of git. I will send seperate emails to this list about the things I would like to discuss. Hannie 1. https://l10n.gnome.org/languages/nl/ 2. https://wiki.ubuntu-nl.org/community/Vertaalteam https://launchpad.net/~ubuntu-l10n-nl 3. http://ubuntu-manual.org/ ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
test
Before I start a discussion, I want to see if my emails make it to this list. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Change .page, see result
Op 05-12-17 om 12:24 schreef Ekaterina Gerasimova: What will happen if I commit/push the branch with the changed .page files I am happy with. Will they be added to gnome-user-docs (patches?). So far, I have only pushed the branch with changes to the nl.po file. That is what will happen. As this would be your first docs contribution, it would be better if you could push a branch for review or attach a patch to Bugzilla. Generally, after seeing a few good patches and when I'm sure that you're not breaking the build, I am likely to suggest that you start pushing minor fixes straight to master. Hello Ekaterina, I understand that it is better NOT to push the gnome-user-docs branch if I have changed .page files. Instead, I will attach the .page file (or part of it?) to a Bugzilla report (is that what you mean by "attaching a patch to Bugzilla?). I do not know how I can push a branch for review. I am currently trying to find out how things work. And I fully understand that you will only allow me to push minor fixes straight to master after I have proven I can do it right. I will go through the buglist to see if I can fix some of them and send my changes, if any, to Bugzilla. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Change .page, see result
Hi Germán, Wow, these sure are encouraging words. I will answer between the lines: Op 06-12-17 om 13:27 schreef Germán Poo-Caamaño: Hi Hannie, I am very sorry that my pointers turned out to be more complex than I anticipated. I believe I was not clear enough on what I meant. Let us step back a bit and be sure we are on the same page (no pun intended with respect to the subject of this thread). My understanding is that you are already using git, and you have a branch with your changes in the documentation. Therefore, you want to know how to submit your changes in bugzilla. That's right. I use git (clone, add, commit, push, and checkout) to upload translations (.po files) to the server. But now I want to start contributing as a reviewer/author for gnome-user-docs and gnome-getting-started-docs as well. I have changed gs-use-system-search.page and I have checked the changes on my pc using Yelp. From what Ekaterina wrote, I understand that I should not push my local branch, gnome-getting-started-docs, to git.gnome. Instead, I should send a patch to Bugzilla. I just checked Gunnar's notes, thanks Gunnar!, and I will try the last steps (git add *, git commit and git format-patch HEAD~). If it works, it will make me very happy indeed :) If not, I will ask further questions on this list or on irc. Considering that, I meant to say that you should consider only the link to submit a patch, not the previous steps about building a project and/or installing Builder or jhbuild. The reason why I looked at the previous steps is because I could not create a patch (step 4). In the example I saw nautilus(~/jhbuild/checkout) master, so my conclusion was I should install jhbuild first. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
my first patch
Hello, Thanks to the help of Gunnar and Germán, I managed to create my first patch!! Could someone please have a look at https://bugzilla.gnome.org/show_bug.cgi?id=791340 and give comment? Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Change .page, see result
Hello Germán, Thanks for the info. In order to be able to submit a patch, I followed the instructions on the wiki, [1] . I installed Flatpak (version 0.10.1) on Ubuntu 17.10, but I got stuck when trying to download Builder (gnome-software message: Don't know how to handle 'file:///tmp/mozilla_hannie0/org.gnome.Builder-2.flatpakref'). I will try to install jhbuild instead, according to 'Set up your testing environment' [3] and see if that will allow me to submit patches. I realize that this mailing list is not a helpdesk, so if I am asking too much help here, I apologize and I will stop asking questions. Hannie [1] https://wiki.gnome.org/Newcomers/SubmitPatch [2] https://wiki.gnome.org/Newcomers/BuildProject [3] https://wiki.gnome.org/DocumentationProject/Contributing A patch is a representation of the minimal changes between your file(s) and the one(s) in the repository. It allows people to focus only in the changes, rather than looking through a whole file. With a little bit of practice, you will get used to and you will find it handy (welcome to the matrix! ;-) That said, you may want to take a look at: https://wiki.gnome.org/Newcomers/SubmitPatch I am currently trying to find out how things work. And I fully understand that you will only allow me to push minor fixes straight to master after I have proven I can do it right. I will go through the buglist to see if I can fix some of them and send my changes, if any, to Bugzilla. Another resource (perhaps not as detailed as you are asking) is: https://wiki.gnome.org/DocumentationProject/Contributing ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Change .page, see result
Op 04-12-17 om 13:44 schreef Andre Klapper: On Mon, 2017-12-04 at 11:56 +0100, Hannie Dumoleyn wrote: I would like to know how I can see the result of the changes I make to a .page file You open the .page file in Yelp (GNOME's help browser). Cheers, andre Hi Andre, Thanks for the answer. I tried this in the Terminal: ~/gnome/gnome-getting-started$ yelp gs-use-system-search The result is: Document not found. The URI does not refer to a valid page. When I add .page to the command ~/gnome/gnome-getting-started$ yelp gs-use-system-search.page I get: unknown error. I do not know where the help files which I get when I press F1 reside, and I do not want to mess them up. That is why I stored a copy of gs-use-system-search.page in a separate directory. I can experiment with it, without messing up the branch I downloaded. Sorry, I am a newbe, so I need more hints :) Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
The Lock Screen
While testing The Lock Screen in Ubuntu-gnome 16.04, I noticed that I do not get the lock screen curtain, as described in *gnome-user-docs*. When I press the lock screen button, I get the log in screen. The reason may be: 1. I am using an older version of Ubuntu-gnome (the latest LTS version) 2. you only get this curtain in other distro's 3. it has something to do with the settings 4. I have missed something Does anyone know why I do not get this curtain? Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: The Lock Screen
Hello Jim, Let me explain why I want to discuss a minor issue like the lock screen curtain on this list. I try to look at the gnome-user-docs from a beginner's point of view, because the docs are mostly used by beginners (I think). If I encounter something that is not working as described in the docs, I want to know why. If it needs to be corrected, I make changes to the .page file and send in a bug report with a patch. In this case, your answer makes me conclude that shell-exit.page does not need any further explanation because my "lock screen problem" occurs in older versions (ubuntu 16.04 and 17.04 (I tried gnome default, gnome classic and gnome on Wayland)). I am forced to use older 32 bit versions at the moment because I not able to use my newer PC with ubuntu-gnome 17.10 at the moment. As a beginning contributor to gnome-user-docs, I am very glad you and others help me to find the best way to help improving the docs. Regards, Hannie Op 30-12-17 om 19:13 schreef Jim Campbell: Hi Hannie, Thanks for giving this a look, and for being so detail-oriented. While Ubuntu 16.04 is an LTS release for Ubuntu, it's a rather old version to be troubleshooting against for docs. Could you see if you have the same question on Ubuntu 17.10? Not seeing the curtain also makes me wonder if you somehow have lightdm as your login manager. Thanks again for your help and efforts. Jim On Dec 30, 2017 10:30 AM, "Hannie Dumoleyn" <lafeber-dumole...@zonnet.nl <mailto:lafeber-dumole...@zonnet.nl>> wrote: While testing The Lock Screen in Ubuntu-gnome 16.04, I noticed that I do not get the lock screen curtain, as described in *gnome-user-docs*. When I press the lock screen button, I get the log in screen. The reason may be: 1. I am using an older version of Ubuntu-gnome (the latest LTS version) 2. you only get this curtain in other distro's 3. it has something to do with the settings 4. I have missed something Does anyone know why I do not get this curtain? Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org <mailto:gnome-doc-list@gnome.org> https://mail.gnome.org/mailman/listinfo/gnome-doc-list <https://mail.gnome.org/mailman/listinfo/gnome-doc-list> ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Single or double quotation marks + Typography
I will comment between the lines: On 01/08/2018 01:00 PM, Ekaterina Gerasimova wrote: On 27 December 2017 at 10:45, Hannie Dumoleyn <lafeber-dumole...@zonnet.nl> wrote: While translating, I encountered many fuzzy strings where only quotation marks have changed. Example: What does "“super user"” mean? The user'’s privileges type ‘rhythmbox’ I have read the guidelines [1] and [2], and found them very interesting. The question is: is there a difference between single and double quotation marks? In my language there is no difference between the two, but it is recommended to use either single or double, not both in one document. The first case is a quotation mark to reference a phrase Good. So this means that, for quotation marks, we use “ U+201C and ” U+201D. (Unicode instead of ASCII). and the second case there is an apostrophe to show ownership. In the case of the genitive we use an apostroph, U+2019 (Not ASCII) We do not use single quotation marks (e.g. to quote, reference or emphasise). What you say here is that my third example should be “rhythmbox” and NOT ‘etc’. On our wiki [1] I see this: quote The following Unicode character usage is *still under discussion*: /Single quotation marks/ (U+2018 and U+2019, ‘‘’ and ‘’’) rather than straight single quotes (‘'’) or backticks (‘`’). These should be used to quote one- or two-word phrases, rather than extended blocks of text (for which double quotation marks should be used). unquote Is this still under discussion (your comment: We do not use single quotation marks)? Personally, I think using single quotation marks is useful as in my third example. I use Right Alt + (). I realize that it is quite a job to change all, but maybe it should be mentioned in the guidelines which is preferred. For translators it means extra work, because a translation becomes fuzzy as soon as one character changes. I find the following site useful: https://www.cl.cam.ac.uk/~mgk25/ucs/quotes.html Regards, Hannie Let me know what you think. Hannie [1] https://wiki.gnome.org/Initiatives/GnomeGoals/UnicodeUsage [2] https://developer.gnome.org/hig/stable/typography.html.en ___ ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Single or double quotation marks + Typography
While translating, I encountered many fuzzy strings where only quotation marks have changed. Example: What does "“super user"” mean? The user'’s privileges type ‘rhythmbox’ I have read the guidelines [1] and [2], and found them very interesting. The question is: is there a difference between single and double quotation marks? In my language there is no difference between the two, but it is recommended to use either single or double, not both in one document. I realize that it is quite a job to change all, but maybe it should be mentioned in the guidelines which is preferred. Let me know what you think. Hannie [1] https://wiki.gnome.org/Initiatives/GnomeGoals/UnicodeUsage [2] https://developer.gnome.org/hig/stable/typography.html.en ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
build gnome-user-docs with nl included
Op 26-02-18 om 13:01 schreef Andre Klapper: Hi, On Mon, 2018-02-26 at 11:15 +0100, Hannie Dumoleyn wrote: After having finished gnome-user-docs 3.28 Dutch translation I want to check it. Can I open a .po file using Yelp? That won't work - Yelp displays help pages, not translation files. :) https://mail.gnome.org/archives/gnome-doc-list/2014-September/msg00075.html explains how to build help files. (Crossing fingers it's still valid.) andre What I have done is this: Pre-commit checks instructions on [1]: I have built gnome-user-docs according to these instructions. What I get in the folder system-admin-guide is C, cs, de, es, gl and ko. My question is: why do I only get 5 languages in this build, while I do have /nl in /gnome-user-docs/gnome-help. Should I add nl somewhere (Makefile, Makefile.am or whatever)? Hannie P.s.: I tried to chat, but nobody was active in #docs [1] https://wiki.gnome.org/DocumentationProject/Tasks/DesktopHelp ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: build gnome-user-docs with nl included
Op 01-03-18 om 11:39 schreef Rafael Fontenelle: 2018-03-01 7:25 GMT-03:00 Hannie Dumoleyn <lafeber-dumole...@zonnet.nl>: Pre-commit checks instructions on [1]: I have built gnome-user-docs according to these instructions. What I get in the folder system-admin-guide is C, cs, de, es, gl and ko. My question is: why do I only get 5 languages in this build, while I do have /nl in /gnome-user-docs/gnome-help. Should I add nl somewhere (Makefile, Makefile.am or whatever)? Hannie For System Admin Guide, you have to add 'nl' to HELP_LINGUAS in the last line of system-admin-guide/Makefile.am (and then run ./configure). You have also to put your translation file "nl.po" inside "system-admin-guide/nl/", as usual. Ah, thanks for the info (Andre as well). Please notice this is similar scenario as "gnome-help/", which already has 'nl'. You are absolutely right. Now, /gnome-user-docs/gnome-help/nl contains the right .page files which I can test. I had expected them to be in /system-admin-guide, so I did not check /nl which orignally only had nl.po in it. I learn a lot from you guys. I have to look further than the length of my nose (Dutch proverb:)). Hannie Best regards, Rafael Fontenelle ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Corrections gud, accounts
Hannie, I committed your changes as f975a12baf884518cb1f397c210638cda8e31620. Looking forward to your next change request, maybe a merge request? :) Cheers, pk ___ Great! Thanks a lot. There is more to come, after I have found out how to do a merge request (using gitlab, I suppose). Let me get acquainted with gitlab first. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Corrections gud, accounts
I am currently taking a close look at gnome-user-docs, subject accounts (accounts-add.page, accounts-disable-service.page, accounts.page, accounts-provider-not-available.page, accounts-remove.page, accounts-which-application.page, accounts-whyadd.page). There are many corrections to be made. For example: online accounts has no + button to add an account (3.28) accounts are listed on the right side, not on the left side etc., etc. I only checked this in Ubuntu 17.10, not in other distributions. For me it would be an enormous task to create a bug report and send in a patch for each correction. Would it be possible to make a list of corrections like this [1], so that someone from the maintenance team can make the changes? I am not allowed to upload gnome-user-docs, so there is no need for me to make corrections in gud locally. Hannie [1] accounts-disable-service Old: Select the account which you want to change from the list on the left. New: Select the account which you want to change from the list on the right. Old: To turn on a service that you disabled, just go back to the Online Accounts window and switch it on. New: To turn on a service that you disabled, just go back to the Online Accounts panel and switch it on. (In another message I see ‘Click on Online Accounts to open the panel.’, so instead of window, panel should be used). accounts-add accounts-add.page Old: Click the + button in the lower-left corner of the window. New: Select an account from the list on the right. ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: user-docs Dutch translation
Op 06-03-18 om 15:53 schreef Petr Kovar: On Mon, 26 Feb 2018 13:01:04 +0100 Andre Klapper <ak...@gmx.net> wrote: Hi, On Mon, 2018-02-26 at 11:15 +0100, Hannie Dumoleyn wrote: After having finished gnome-user-docs 3.28 Dutch translation I want to check it. Can I open a .po file using Yelp? That won't work - Yelp displays help pages, not translation files. :) https://mail.gnome.org/archives/gnome-doc-list/2014-September/msg00075.html explains how to build help files. (Crossing fingers it's still valid.) Hmm, do we have adding a new translation to docs modules documented anywhere? I can't find anything on the wiki. In any case, we need to update https://wik.gnome.org/DocumentationProject/Tasks/DesktopHelp when we migrate to GitLab, so it might be a good idea to document this there, or add a pointer, I guess. Thanks, pk Hi Petr, Since I have succeeded in building the Dutch .page files, so I can check the translation using yelp, I could try and write how I did it. Will it be the same for gitlab? I use git at the moment. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Corrections gud, accounts
Op 06-03-18 om 16:01 schreef Petr Kovar: On Tue, 6 Mar 2018 12:08:47 +0100 Hannie Dumoleyn <lafeber-dumole...@zonnet.nl> wrote: I am currently taking a close look at gnome-user-docs, subject accounts (accounts-add.page, accounts-disable-service.page, accounts.page, accounts-provider-not-available.page, accounts-remove.page, accounts-which-application.page, accounts-whyadd.page). There are many corrections to be made. For example: online accounts has no + button to add an account (3.28) accounts are listed on the right side, not on the left side etc., etc. I only checked this in Ubuntu 17.10, not in other distributions. For me it would be an enormous task to create a bug report and send in a patch for each correction. Would it be possible to make a list of corrections like this [1], so that someone from the maintenance team can make the changes? I am not allowed to upload gnome-user-docs, so there is no need for me to make corrections in gud locally. Hey Hannie, if you can assemble a list of changes like that and send it here, that's still quite helpful as some other team member with a git account can just copy and paste it in the page files for you. You can apply for a git account when you submit a handful of changes. Also, we are about to migrate to GitLab, so I was wondering if it is easier for you to submit a merge request with your changes going forward? I know that the workflow requiring to submit patches in Bugzilla is very clumsy, but that's going away. Thanks, pk Hi Petr, I do have a git and a gitlab account, but I promised here on the list that I would not upload my local changes in the English .page files until, one day, the team trusts me enough to allow me to upload my changes ;) Ah, I do not have any experience with gitlab yet, but if it makes reporting bugs in gud easier, I would be very happy. And I am willing to learn. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Launching Settings
Op 24-03-18 om 13:25 schreef Michael Hill: Another method is to add the Settings icon to the Dock, if it is not there already. It might be useful to add a separate item to Help, explaining the different ways in which one can open Settings. This is covered in general terms in shell-apps-open.page. Maybe it would be appropriate to add a recurring link to it, the way Activities is a link now. Mike This is what I was thinking of too, use a link like with Activities overview. Perhaps someone from the maintenance team can have a look at that. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Announcing a pilot for docs release schedule with string freeze
On 16-03-18 18:17, Petr Kovar wrote: Translators, With the new stable release out, I wanted to ask you to provide feedback on the user docs string freeze pilot. Did you find it useful and worth continuing? My take on this is that with a limited number of content changes affecting user docs (and thus translations), having multiple string freeze periods during the cycle is probably a bit of an overkill. Might be better to only freeze the strings before we release the last stable point release, for instance? Or maybe drop the whole freeze idea? Let me know your thoughts! Thanks, pk On Sun, 6 Aug 2017 19:58:55 +0200 Petr Kovarwrote: Hi all, Based on community input [1], the docs team plans to run a 3.26 release pilot program for docs string freeze that would allow translators more time to update their user docs translations (primarily gnome-user-docs). I've put the details here: https://wiki.gnome.org/DocumentationProject/Tasks/ReleaseSchedule Consider it a draft and let me know your comments or questions. Based on the feedback, we will evaluate the results when the 3.26 cycle ends and decide on the future course of actions. Thanks, pk [1] https://mail.gnome.org/archives/gnome-doc-list/2017-May/msg00010.html ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list Hi Petr, I would be in favour of a string freeze just before the release of the next stable version (same as GUI string freeze). Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Launching Settings
Op 23-03-18 om 22:34 schreef Michael Hill: The user help has these instructions for launching each Settings panel (with Network as an example): 1. Open the Activities overview and start typing Network. 2. Click on Network to open the panel. The reason for this was that not everyone gets the same icon on the Settings button in the system menu (the way I always launch Settings). Network used to be the first hit in the search, but now I get three app icons before it and it shows up in the list part of the search results. Wi-Fi is now a separate panel, so the manual network settings instructions, for instance, are getting ridiculous: 1, 2 above, then if you don't have a wired connection, click Wi-Fi in the left pane. Is there a better way to describe launching settings? Mike ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list Hello Mike, Which distro do you use? I use Ubuntu. If I follow the above instructions, under Settings I get Network (first) and wifi (second). I can choose to go the the Network panel or wifi panel, depending on what I want to configure. Is this different in your distro? Of course one can also launch Settings from the system menu. In my case, all I have to do is click the Settings button. Another method is to add the Settings icon to the Dock, if it is not there already. It might be useful to add a separate item to Help, explaining the different ways in which one can open Settings. Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
user-docs Dutch translation
Hello, After having finished gnome-user-docs 3.28 Dutch translation I want to check it. Can I open a .po file using Yelp? Hannie ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list