I cannot see "to much spaces" or other strange things. So probably I cannot help, at all.

I cannot see "to much spaces" or other strange things. So probably I cannot help, at all.

Line 104:

Line 104:

== categorizing pages ==

== categorizing pages ==

−

* '''Pages that are part of the handbook''' will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro topic or sub-micro topics get categories as well, is not as clear. They *could* but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.

+

* '''Pages that are part of the handbook''' will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro, nano, pico, or atto topics get categories as well, is not as clear. They *could* but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.

* Other pages on the wiki, may have the category ''pc-bsd wiki'' and a category of the ''topic'' it fits.

* Other pages on the wiki, may have the category ''pc-bsd wiki'' and a category of the ''topic'' it fits.

* The category, ''categories'' is only for category pages and not to categorize normal pages.

* The category, ''categories'' is only for category pages and not to categorize normal pages.

+

+

* Categorizing images- similar hierarchy would be used as with handbook pages, especially to add a category tag for the page the image appears on.

* It is okay to create new categories by giving a page a new category membership. It will display a redlink for the category which can be used to make it official and add a description for the new category.

* It is okay to create new categories by giving a page a new category membership. It will display a redlink for the category which can be used to make it official and add a description for the new category.

I simply wish to have some clarification on your exact method for translating any particular wiki page. I want to be sure of how you are doing it so that I can avoid any of my own assumptions. So, step by step if you please with screenshots if necessary. Thank you very much.

+

+

I really want to solve the issue that has been causing trouble for you as a translator, which may also solve it for others.

Actually, for ONE page, I think I know the problem. When the original page gets modified, the translations of that page are essentially no longer synchronized. The section(s) that are highlighted as "out of date" are properly marked as being not synchronized and may need attention. However, if a section of the original page is modified, but it has not been marked again to be translated, I believe this is what you may be running into. Since the section is recognized as being not synchronized, it will need to be fixed in translation but there is a moment when the original has been modified but not yet flagged to be translated. I hope this makes sense.

+

+

I have run into it myself, where a section that I have edited multiple times does not seem to get saved, and likely does not- because the modified page section(s) need to be re-approved but I forgot to do that before adjusting the translation (even English has this step afaik though nothing changes).

+

+

This is one problem solved. Whether it is the same problem in all places, I do not know but I doubt that it is.

There is no real reason for any of the 10.0 pages to not be marked for translation. [[Special:PageTranslation|Check this list (Second half: Pages in translation)]] if you have problems, and they can be marked again for translation. I will go through them now for all 10.0 pages.

Revision as of 06:06, 20 April 2014

Hello!

I added some content to the 'text' section of the guidelines page that you asked about. It is still rather sparse. I suppose that part of the reason for this is that much of the site edits have been handled by Dru and myself. She mostly adding the content and usually images, and basically being the editor of the resulting handbook. I have tried to make improvements in other areas and have done some edits and image uploads (which I also tried to document some best methods).

If you have further thoughts on any part of this process, including wiki templates, wiki documentation, and anything else, I am willing to listen. I feel that what we should strive for, is a level nearing wikipedia. There are still many things that can be improved, especially things that would make an editor's job easier, shorter, or more intuitive. You found the style guidelines page, which means either it made sense to seek it, or it is something normally found on a wiki site. I am not sure of all such pages, that is part of the reason why a lot of the editor documentation is missing.

I might suggest to explore the entire wiki site and see what is here already. The special pages are very helpful for discovering problems, such as double redirects and other faulty things. I have tried to have all handbook pages categorized, and all useful pages with one of the two headers.

You're doing fine. I looked at your change to 'security' and don't see any problems with the wording. Its good to have another active editor on the wiki. If you have any questions about the templates or suggestions for new templates, I'm willing to assist with them. Templates can be quite challenging to create, but I eventually succeed with my ideas.

As I said once before, I want editing the wiki to be as simplified as possible while also being as automated as possible, both are accomplished by well-designed templates. It will take time to finesse those solutions in template form, but eventually they will exist.

It also helps you and any other editor, to have written guidelines and other editor documentation. With these, we can remain consistent on the entire wiki site, not only the handbook portion of it.

I think I should set aside a space somewhere for the ideas I desire or plan for. I'll let you know when it exists and where.

Your request for "define numbering consecutively"- is this meant to be part of the Collation section of the style guidelines? I'm not sure if there is a certain 'best' or 'worst' way of doing it. Unless you have a certain example that you could give me to help with defining this in a general way?

The PC-BSD Wiki:Style Guidelines#External Hypertext Links is all wiki markup, although part of it does look like html because it uses < and > to enclose some things. I need to make parts of it bold to better clarify it. In addition to this, there are certain situations where it truly is a mix of wiki markup and html, such as the Wiki Site TODO page.

At the moment, I do not believe there is a specific rule already being followed for when to use numbered lists. It would make sense to use them for specific step-by-step instruction, however, I do not believe that this is used much at all. I believe that the primary method of describing processes is entirely with words rather than numbered lists. I will have to skim through the handbook to see how it might best be used and clarify the conditions that would necessitate it.

The EasyPBI page is missing a number of images, that automatically become red text to indicate this. The odd "2." you noticed seems to be a remnant of an edit, and not intentional. The page may not yet be as perfect as desired or may be incompletely modified, causing some of the consistency issues and other flaws.

Beware, there are templates of various format on the wiki, including more than one way to make the tables. The intent with all variants is to eventually simplify and speed up editing. I will have to set aside somewhere to indicate which templates have been depreciated, or perhaps simply a "depreciated" category tag for those.

Thank you for your help and motivation toward getting things defined. It will help us all to stay consistent. I already now realize PC-BSD Wiki:Style Guidelines appears to incompletely apply to itself.

With regard to the use of hard enter for bullets, I am uncertain if or how this makes a difference because the wiki software will re-interpret all content anyways. I believe a more proper way of handling the "hard enter" would be to add a <br> tag.

Contents

thin client page

Hey there..

I am curious whether you are able to successfully edit & save any edits to the Thin Client page. There is a weird bug of some sort that prevents me from editing the whole page or the first section, and being able to save it. If the content of the first section is all selected, you may see a few places where there appear to be extra spaces (at the end of lines, one is at the beginning of a blank line). I do not believe those are actually spaces, but something else which causes this error I describe.

Anyhow, either the page can be fixed by someone other than myself (no clue why I am lucky to be bitten by this bug), or at the very least, the external links within the page need to be switched to citelink format as described in the style guidelines.

Those will work fine now. Thanks! For future interwiki type links, they can also use the citelink template in a shorter form (similar idea to usual interwiki link). The style guidelines lists the sites that I setup for this interwiki function, in the special external section.

BTW: I am a friend of "simple" things (can be used by everyone). So I prefer the "style" of interwiki links (by using a namespace like syntax. Anyway thanks a lot for the (great) template. Of course I will use it, starting from now.

categorizing pages

Pages that are part of the handbook will have these categories: handbook, macro topic (such as control panel), topic (such as bluetooth manager). Whether micro, nano, pico, or atto topics get categories as well, is not as clear. They *could* but since those are often more verbose, they would probably need to be made a bit more concise (few words, like no more than 2 or three) without losing detail.

Other pages on the wiki, may have the category pc-bsd wiki and a category of the topic it fits.

The category, categories is only for category pages and not to categorize normal pages.

Categorizing images- similar hierarchy would be used as with handbook pages, especially to add a category tag for the page the image appears on.

It is okay to create new categories by giving a page a new category membership. It will display a redlink for the category which can be used to make it official and add a description for the new category.

Exploring to see how things are already and discovering what exists are the best ways to learn what to do. I cannot claim that there is perfect consistency through the entire wiki, or even the entire handbook portion of the wiki, but hopefully there is enough consistency to understand the intent and the general rule being applied. I have tried to document things in the Style Guidelines, and various other places (ie, on templates or categories). It never hurts to ask when you are unsure, but as you've also noticed, recent changes will alert you to where you may take a look whether changes are needed (in other words, you can use your best judgement and 'go for it,' you won't permanently wreck anything :).

Thanks for your time and efforts on the wiki, it is certainly appreciated.

Translation difficulties

Hey there.

I simply wish to have some clarification on your exact method for translating any particular wiki page. I want to be sure of how you are doing it so that I can avoid any of my own assumptions. So, step by step if you please with screenshots if necessary. Thank you very much.

I really want to solve the issue that has been causing trouble for you as a translator, which may also solve it for others.

Actually, for ONE page, I think I know the problem. When the original page gets modified, the translations of that page are essentially no longer synchronized. The section(s) that are highlighted as "out of date" are properly marked as being not synchronized and may need attention. However, if a section of the original page is modified, but it has not been marked again to be translated, I believe this is what you may be running into. Since the section is recognized as being not synchronized, it will need to be fixed in translation but there is a moment when the original has been modified but not yet flagged to be translated. I hope this makes sense.

I have run into it myself, where a section that I have edited multiple times does not seem to get saved, and likely does not- because the modified page section(s) need to be re-approved but I forgot to do that before adjusting the translation (even English has this step afaik though nothing changes).

This is one problem solved. Whether it is the same problem in all places, I do not know but I doubt that it is.