ben chen邀请您加入领英
ben邀请您加入全球领先的职业社交网站 LinkedIn (领英)。领英能帮助您管理职业生涯，让您接触到全球各地的工作机会。 快来加入领英，创建您的职业档案，轻松拓展职场人脉！ ben chen XinLi Industrial Co., ltd.-BOPP Thermal lamination Film Manufacturer/www.wonfilms.com/ben.xinlif...@hotmail.com 中国 广东其他地区 接受邀请: https://www.linkedin.com/comm/start/accept-invitation?sharedKey=T6jW4WqA&invitationId=6271681405344944134&trk=eml-china-m2g-a-cta&trkEmail=eml-invite_guest-null-31-null-null-wel5f%7Ej8mqx6vz%7E40-ssuw-start%7Esignup%7Ewarm&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3BAkhVvbWLQnab6ZwZzFETzQ%3D%3D 有会员邀请您建立联系。在“猜您认识”等功能中，领英将使用您的邮箱地址来向会员推荐人脉。在此处退订: https://www.linkedin.com/e/v2?e=wel5f-j8mqx6vz-40&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&loid=AQE4hLwEsRhtoQAAAV8Kc2XzBi-XsuIMvRn-hWBMaZgHGbYF3ibIlFpWap9GKuw-G5sOZm7JmF7bV-zQWshMCRdcH52cUFM&eid=wel5f-j8mqx6vz-40 此邮件的收件人是d...@freebsd.org。 If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=wel5f-j8mqx6vz-40&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3BAkhVvbWLQnab6ZwZzFETzQ%3D%3D&a=customerServiceUrl&ek=invite_guest © 2017 LinkedIn Corporation, 1000 West Maude Avenue, Sunnyvale, CA 94085.LinkedIn 和 LinkedIn 标志是领英的注册商标。 ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Make your web page appear on top of Google
Dear Doc, If you see that you're involved into PPC bidding war and it costs you a fortune when someone bids higher than your bid, there is some other way to control and be always on top of search engines. If you want to see how we beat AdWords in prime positioning, traffic, pricing by placing your website banner on top of search engine results, you can go to our website, go to ONLINE DEMO section, type your website freebsd org and your keyword, submit form and see results. You can get information about terms if you fill online quote or call us. Basically, we give you exclusive rights of keyword ownership during whole year and no other company can get on first position during this time. You will have first right of renewal on all keywords that you lock with us. Thank you for your consideration, Alexis ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
Here is chapter 1 in an odt since it's a new work and I wanted to bang it out without formatting. I'll add it to the sources after I get a good start on Chapter 2 and post a patch. I assume phabricator the preferred tool for commenting on documents? Russ On Mon, Oct 9, 2017 at 3:48 PM, Benjamin Kaduk wrote: > On Mon, Oct 09, 2017 at 12:22:11AM -0700, Russell Haley wrote: >> On Mon, Oct 2, 2017 at 9:21 AM, Russell Haley wrote: >> > On Fri, Sep 29, 2017 at 7:58 AM, Warren Block wrote: >> >> On Mon, 25 Sep 2017, Russell Haley wrote: >> >> >> >>> Thanks! I'll play with this on the weekend. >> >> >> >> >> >> Please create a review at https://reviews.freebsd.org/ and add me as a >> >> reviewer. >> >> >> >> Thanks! >> > >> > Will do. Just a progress update: I got the handbook sources and found >> > the section in chapter.xml. I created a Geany project with everyone's >> > raw notes and the sources. To be continued... > > IIRC Warren had volunteered to help get that text committed, but if > not, feel free to add me to the phabricator review when it's ready. > >> >> Hi, >> >> So I got a good chunk of work done moving koobs’ description into the >> correct format and then started looking at how everything hangs >> together. I don’t want to offend anyone on this list, but I think the >> organisation and some of the English in the first 4 chapters needs >> work. I know how hard it is to create content from nothing (and how >> easy it is to be critical), so my hat is off to the original content > > Given how deep a tangle of patchwork and incremental change on top of > incremental change it is, it's unsurprising that the overall organization > of things does not make the best of sense. > >> creators. However, what I would like to propose is this: >> >> 1) Re-write the introduction to describe what the ports system is and >> point to the correct references in the handbook for running ports. I >> would also include reference to how to use subversion (handbook) and >> the correct repository names. I would also point users to websvn. I >> would indicate that the pkg system works off of the ports and include >> some other helpful links such as freshports, github and the build >> system. I would include a paragraph about how bugillza can be searched >> for issues for ports and also describe how phabricator is used to >> submit new patches to the ports system. Finally, it should be >> emphasised that anyone can create a new port for their software and >> submit it to the system. >> >> 2) The second chapter should be a description of how the ports system >> works. This description can be found in the how things work section of >> chapter 4. Include further description of the make files and where >> they can be found. A note should be made that while the makefiles are >> source code, they are well documented at the top and can be referenced >> when needed for more information. Chapter 2 should describe how >> additional targets can be created (content also from chapter 4). >> >> 3) Chapter 3 should remain and should be renamed Port Files Overview >> (or something to that effect). The first page should outline the files >> and involved. Most of them are quite simple and dedicating an entire >> ‘section’ to each step is cumbersome. Section 3.1 and 3.2 should be >> combined and beefed up (not sure the name yet). Section 3.3. and 3.4 >> should be combined and called Validation and Verification (or >> something to that effect). A description of what portlint does should >> be added. The new "V&V" section should describe why testing is >> important and what things to pay attention to, as well as reference >> the do’s and don't s section. >> >> 4) Chapter 4 should be called adding or updating ports. It should >> briefly describe what should be done to create a new port and then >> describe the processes as outlined by koobs'. The manual porting >> instructions should be removed. >> >> If there is any interest in me doing this, please speak up now as I >> might be able to take a day off this week and bash it out in one >> sitting. Okay, it's late... > > This sounds like a pretty good strategy, especially the part where > we actually introduce the subject matter! > > I don't want to tell you to take a day off, but would be happy to > see something like this appear eventually. > > Thanks for putting these thoughts together, > > Ben ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
I had not commented before because I am on a long road trip. But I'm very glad you have taken on this work. I had always wanted to do something very much like this but never made the time to do it. My old thought was that we have conflated "User's Guide to Ports" and "Ports Reference Handbook". Certainly the bulk of the existing text is the latter type (even if not well organized; it kind of "grew".) I'm indifferent if the Guide parts (basically what you have been working on) remain in the PH or become a separate piece. But depending on the degree of rewrite, do you think that might be easier? It's certainly true that the current PH is too bloated. I won't have the cycles to look at your work for another week or two, so consider this just "a voice from the peanut gallery". mcl ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 222939] refactor `make po'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222939 Bug ID: 222939 Summary: refactor `make po' Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Documentation Assignee: freebsd-doc@FreeBSD.org Reporter: wo...@freebsd.org I looked at the code in doc/share/mk/doc.docbook.mk I wish we refactor the code and move it out to a separate make file, lets call it doc.translate.mk (or doc.docbook-translate.mk) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[Bug 222939] refactor `make po'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222939 Wolfram Schneider changed: What|Removed |Added CC||wbl...@freebsd.org Assignee|freebsd-doc@FreeBSD.org |wo...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
On Wed, Oct 11, 2017 at 11:23:58AM -0700, Russell Haley wrote: > Here is chapter 1 in an odt since it's a new work and I wanted to bang > it out without formatting. I'll add it to the sources after I get a > good start on Chapter 2 and post a patch. I assume phabricator the > preferred tool for commenting on documents? No harm in banging it out without formatting (nothing wrong with plain-old-UTF-8, even). Phabricator is the preferred tool, yes. It will take me a few days to have a chance to look, most likely. Thanks again, Ben ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
Benjamin Kaduk wrote: On Wed, Oct 11, 2017 at 11:23:58AM -0700, Russell Haley wrote: Here is chapter 1 in an odt since it's a new work and I wanted to bang it out without formatting. I'll add it to the sources after I get a good start on Chapter 2 and post a patch. I assume phabricator the preferred tool for commenting on documents? No harm in banging it out without formatting (nothing wrong with plain-old-UTF-8, even). Phabricator is the preferred tool, yes. It will take me a few days to have a chance to look, most likely. Thanks again, Ben Have nothing to add here, but this post peaked my interest about what your talking about. What is Phabricator? What is its use in generating doc markup file for handbook changes? ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
On Wed, Oct 11, 2017 at 06:40:20PM -0400, Ernie Luzar wrote: > What is Phabricator? A code review system up at http://reviews.FreeBSD.org . It claims to "provide code reviews, image mocks, voting, and other tools." For purposes like this where multiple people have their blue pencils out, it is a more useable tool than Bugzilla, which is intended more for "problem reports". OTOH for small patches there is an overlap. These days the documentation people mostly use Phabricator instead of the Bugzilla instance. The separation is kind of artificial and still a little controversial. I personally don't care as long as work gets done :-) mcl ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
On Wed, Oct 11, 2017 at 06:40:20PM -0400, Ernie Luzar wrote: > > Have nothing to add here, but this post peaked my interest about what > your talking about. > > What is Phabricator? Phabricator is a project/software for doing code review of all sorts. The FreeBSD documentation tree contains a lot of XML file, which can be treated as code and subjected to pre-commit review as well. > What is its use in generating doc markup file for handbook changes? It doesn't help with converting non-marked-up text to XML form, it's just a convenient place to post a draft patch and be able to make line-by-line comments on it that are archived in a useful way. https://www.phacility.com/phabricator/ seems to be the upstream project's home page. -Ben ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Porters Handbook section 4.4
Hi, This is a rough cut of three new chapters at the beginning of the book. I have left all the original content in place (I think). I haven't attempted to get all the markup but I seem to have worked through all my xml errors. Unfortunately I'm getting an error about a missing xsl file "http://docbook.sourceforge.net/release/xsl-ns/current/xhtml/chunk.xsl";. I was able to manually download the file but I don't know where to put it yet. I'd like to get the new chapters to compile and at least take a stab at cleaning up the formatting before I put it on the review board. However, a patch file can be found here for now: https://github.com/RussellHaley/portershandbook . Build error: russellh@prescott:~/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook% make install /usr/home/russellh/FreeBSD/doc/share/xml/catalog-cwd.xml /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/catalog-cwd.xml echo '' >> /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/autogen.ent env XML_CATALOG_FILES="file:///usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/catalog-cwd.xml file:///usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/share/xml/catalog.xml file:///usr/home/russellh/FreeBSD/doc/share/xml/catalog.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/book.xml > book.parsed.xml.tmp /bin/mv book.parsed.xml.tmp book.parsed.xml /usr/bin/sed 's|@@URL_RELPREFIX@@|https://www.FreeBSD.org|g' < book.parsed.xml > book.parsed.print.xml /usr/bin/sed -i '' -e 's|@@URL_RELPREFIX@@|../../../..|g' book.parsed.xml cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/1.png imagelib/callouts/1.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/2.png imagelib/callouts/2.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/3.png imagelib/callouts/3.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/4.png imagelib/callouts/4.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/5.png imagelib/callouts/5.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/6.png imagelib/callouts/6.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/7.png imagelib/callouts/7.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/8.png imagelib/callouts/8.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/9.png imagelib/callouts/9.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/10.png imagelib/callouts/10.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/11.png imagelib/callouts/11.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/12.png imagelib/callouts/12.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/13.png imagelib/callouts/13.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/14.png imagelib/callouts/14.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/15.png imagelib/callouts/15.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/16.png imagelib/callouts/16.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/17.png imagelib/callouts/17.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/18.png imagelib/callouts/18.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/19.png imagelib/callouts/19.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/20.png imagelib/callouts/20.png cp -f -p /usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/../../../share/images/callouts/21.png imagelib/callouts/21.png /bin/rm -f docbook.css /bin/cat /usr/home/russellh/FreeBSD/doc/share/misc/docbook.css > docbook.css env XML_CATALOG_FILES="file:///usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/books/porters-handbook/catalog-cwd.xml file:///usr/home/russellh/FreeBSD/doc/en_US.ISO8859-1/share/xml/catalog.xml fi
Grüße von Franz Moser
Ich möchte Sie gerne zu meinem beruflichen Netzwerk auf LinkedIn hinzufügen. Franz Moser Franz Mosers Profil anzeigen https://www.linkedin.com/comm/start/accept-invitation?sharedKey=2C3U7ebl&invitationId=6323926069426683951&trk=eml-invite_guest-invite_guest-267-germany_f_v2_b&trkEmail=eml-invite_guest-invite_guest-267-germany_f_v2_b-null-wel5u%7Ej8o16ema%7Eae-ssuw-start%7Esignup%7Ewarm&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3BMJdRgulSRJOtxFfaEcU%2F6A%3D%3D Sie haben eine Einladung zur Kontaktaufnahme erhalten. Ihre E-Mail-Adresse wird in Funktionen wie „Personen, die Sie vielleicht kennen“ verwendet, um Kontaktvorschläge zu machen. Hier abbestellen: https://www.linkedin.com/e/v2?e=wel5u-j8o16ema-ae&t=lun&midToken=AQFmrFVhGEd36Q&ek=invite_guest&loid=AQFM29K00ovu2QAAAV8PFOEPP8VQ-aOJx5jfj7cJiEeJkhMeTlePgQEJS_WjZCyRC2wGIdQZGgZmlsoNufkm7dd3srq5n66KXDiU22i0pw&eid=wel5u-j8o16ema-ae Diese E-Mail wurde an freebsd-doc@freebsd.org gesendet. If you need assistance or have questions, please contact LinkedIn Customer Service: https://www.linkedin.com/e/v2?e=wel5u-j8o16ema-ae&lipi=urn%3Ali%3Apage%3Aemail_invite_guest%3BMJdRgulSRJOtxFfaEcU%2F6A%3D%3D&a=customerServiceUrl&ek=invite_guest © 2017 LinkedIn Corporation, 1000 West Maude Avenue, Sunnyvale, CA 94085. LinkedIn und das LinkedIn Logo sind eingetragene Marken von LinkedIn. ___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
