Latex docs at new URL

From tcreedon@easystreet.com Sun Aug 14 23:34:22 2005 From: tcreedon@easystreet.com (ted creedon) Date: Sun, 14 Aug 2005 15:34:22 -0700 Subject: [OpenAFS-Doc] Latex docs at new URL Message-ID: <20050814223421.95EB929524@smtpauth.easystreet.com> This is a multi-part message in MIME format. ------=_NextPart_000_0088_01C5A0E5.A54E3C50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The Latex versions of the IBM docs have been moved to: ftp://creedon.dhs.org It's a high speed line and downloads should be improved. tedc ------=_NextPart_000_0088_01C5A0E5.A54E3C50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Latex docs at new URL

The Latex versions of the IBM docs have = been moved to:

ftp://creedon.dhs.org

It’s a high speed line and = downloads should be improved.

tedc

------=_NextPart_000_0088_01C5A0E5.A54E3C50-- From jaltman@columbia.edu Thu Aug 18 16:43:21 2005 From: jaltman@columbia.edu (Jeffrey Altman) Date: Thu, 18 Aug 2005 11:43:21 -0400 Subject: [OpenAFS-Doc] Need a volunteer to help with a feature summary for 1.4 Message-ID: <4304AC99.7080801@columbia.edu> This is a cryptographically signed message in MIME format. --------------ms090101020302070201080903 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Folks: The 1.4 release is literally days away. The Gatekeepers need a volunteer to help produce a summary list of major and minor changes to OpenAFS since 1.2. For raw information I have three sources: * a ChangeLog produced from cvs log entries. this includes mostly one or two line entries for each commit. * a manually kept change log that I have maintained for the Windows release. afs-changes-since-1.2.txt * the periodic status report that I produce for the Windows release. What we need is a summary of the major and minor feature changes appropriate for inclusion in an Announcement e-mail and for posting on the web site. The tone of the produced text should provide incentive for end-users and management to commit to upgrading their servers and clients to the 1.4 series. Thanks for any assistance you can provide. Jeffrey Altman --------------ms090101020302070201080903 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJPzCC AvowggJjoAMCAQICAw7NrDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDUwNTI3MTc0MjQzWhcNMDYwNTI3MTc0MjQz WjBrMQ8wDQYDVQQEEwZBbHRtYW4xFTATBgNVBCoTDEplZmZyZXkgRXJpYzEcMBoGA1UEAxMT SmVmZnJleSBFcmljIEFsdG1hbjEjMCEGCSqGSIb3DQEJARYUamFsdG1hbkBjb2x1bWJpYS5l ZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+LutDu/YyHreNfoYd+ZtOjXsL h67F2cmcVuBPBz+ZGDA+WpVEHrqXaZZO8acXBR5uAVfiwA1acE/kvD/CN5kAqx1VJuQ8Pvyk iGHhUYTd27ZTliBIrptC7C/381gVwkS+a8jQFPJPO+OktZDzAYplGRY/MQCV8dIsvXUjucox 7TwTTdoLAJYRvHtfEcaCc6mO4ph6NeXQw8Grlx3IRAlTrkE5fBGyjH6R4fqnFTXRQAh1/bG+ i8hQvE6mud3mXdL2t7NP1Qxd9wW0/F/pnWY12IFP/luc3zEzIPvAe+nJluLuSEj0LZgP16mF xBj1p+u9HPWcHRVX6q7+MQ0RWOv1AgMBAAGjMTAvMB8GA1UdEQQYMBaBFGphbHRtYW5AY29s dW1iaWEuZWR1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAUDUuzxiq8bbI8vq2 swRK513RphZp+fepyKU5mwBI6aF4GcmqITQILtfTG2SXnjSeY99d+bjOdK1DJFvVh9aOy8mh 2NbEnqMnJIZtg5+eEU64DIV5bQdDRpi99H9vA0sRATIquut+3YHba+zArj0VkVof2VI+ToBu sHdtSrZYo0gwggL6MIICY6ADAgECAgMOzawwDQYJKoZIhvcNAQEEBQAwYjELMAkGA1UEBhMC WkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1Ro YXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA1MDUyNzE3NDI0M1oXDTA2 MDUyNzE3NDI0M1owazEPMA0GA1UEBBMGQWx0bWFuMRUwEwYDVQQqEwxKZWZmcmV5IEVyaWMx HDAaBgNVBAMTE0plZmZyZXkgRXJpYyBBbHRtYW4xIzAhBgkqhkiG9w0BCQEWFGphbHRtYW5A Y29sdW1iaWEuZWR1MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvi7rQ7v2Mh63 jX6GHfmbTo17C4euxdnJnFbgTwc/mRgwPlqVRB66l2mWTvGnFwUebgFX4sANWnBP5Lw/wjeZ AKsdVSbkPD78pIhh4VGE3du2U5YgSK6bQuwv9/NYFcJEvmvI0BTyTzvjpLWQ8wGKZRkWPzEA lfHSLL11I7nKMe08E03aCwCWEbx7XxHGgnOpjuKYejXl0MPBq5cdyEQJU65BOXwRsox+keH6 pxU10UAIdf2xvovIULxOprnd5l3S9rezT9UMXfcFtPxf6Z1mNdiBT/5bnN8xMyD7wHvpyZbi 7khI9C2YD9ephcQY9afrvRz1nB0VV+qu/jENEVjr9QIDAQABozEwLzAfBgNVHREEGDAWgRRq YWx0bWFuQGNvbHVtYmlhLmVkdTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAFA1 Ls8YqvG2yPL6trMESudd0aYWafn3qcilOZsASOmheBnJqiE0CC7X0xtkl540nmPfXfm4znSt QyRb1YfWjsvJodjWxJ6jJySGbYOfnhFOuAyFeW0HQ0aYvfR/bwNLEQEyKrrrft2B22vswK49 FZFaH9lSPk6AbrB3bUq2WKNIMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TEL MAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBT ZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcx NzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0 ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnK mVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/ cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8 YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4 oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5j cmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwy LTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4 Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAzswggM3AgEB MGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0 ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMOzaww CQYFKw4DAhoFAKCCAacwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx DxcNMDUwODE4MTU0MzIxWjAjBgkqhkiG9w0BCQQxFgQUccOQbq9oPYZL5VHQxmD5DrFrB9kw UgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcN AwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgweAYJKwYBBAGCNxAEMWswaTBiMQswCQYD VQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAw7NrDB6BgsqhkiG9w0B CRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENB AgMOzawwDQYJKoZIhvcNAQEBBQAEggEASQFZUT/CFy2XkTFCjnRBPS28U2qLAnRRLwrqkAk8 eXNY0bMfeu8//q01pbn+naMwFh8LwDmHYsg1nRORAYNR0/Y9O3BWbNAtLtqc6J0jscAR1Fx3 IDBnx9hPzwrAiCa41fkvM1zLW3LAMZJ+ovE+UbA9toItIgSEUE4hdcbmkdcU8yrkbPJaN+2b HUGylOIY72qWkucvMzmFOw9MqxpKPjA8j9qvJub3aYA+6gTG1iB7a2KKoI8JY92ZT6oYQMCu M86Zm5cWcfTC/PyGu9if8PhM7lCQUZIi/XFev0K3sMu06/mKF4D+Ms84gYKXPdoaUun/OB21 /EwW8sLNlilPyQAAAAAAAA== --------------ms090101020302070201080903-- From rarruda0@gmail.com Fri Aug 19 14:27:11 2005 From: rarruda0@gmail.com (renato arruda) Date: Fri, 19 Aug 2005 10:27:11 -0300 Subject: [OpenAFS-Doc] Apologies about documentation mess Message-ID: <83f1799e05081906276cdf1e22@mail.gmail.com> ------=_Part_6651_31417878.1124458031704 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I guess i should apologize for the mess i probably ended up making in the= =20 documentation project. But here is my side of the story. A while ago i needed some documentation that was better formatted than wha= t=20 was available from the website and i felt it needed to be updated. The=20 documentation project looked kinda dead back then, so i decided to do some= =20 work because then i had a personal need for it.=20 Since the format that the HTML pages followed were very similar to LaTeX= =20 and i already knew LaTeX, for me it seemed like an obvious choice to write = a=20 parser that would convert the HTML to latex and live with that. Now if you= =20 say that LaTeX isnt the best tool for the job, then i will have to agree.= =20 But at the time i didnt have the time to learn a new tool and then write=20 parsers to convert the existing documentation to it. LaTeX seemed ok becaus= e=20 it could generate both HTML and PDF for the manuals (never really thought= =20 too much about the man page to be honest). I never thought that LaTeX would= =20 be a final solution, but that once i got all the manual converted to latex= =20 (which i never did), I could write another parser to some other format like= =20 docbook (or whatever it would be felt to be the most appropriate solution).= =20 I dont intend to start a flame war over a format either, but for an=20 official documentation format Esther should be the most adequate person to= =20 make the call, imho. And in my opinion a single source for all the=20 documentation is a must. I=B4ve been away from the community for a while fo= r=20 personal reasons, but now i should have a few hours here and there to work= =20 on the project helping out on what=B4s needed.=20 I=B4m sorry if i have ended up causing disburbances on the community, I=20 _never_ intended for that to happen. At the time i just wanted something=20 that would work better for me, and if it would help others, then it would= =20 all good too.=20 -Renato ------=_Part_6651_31417878.1124458031704 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

Hi,

I guess i should apologize for the mess i probably ended up making in = the documentation project. But here is my side of the story.

A while ago i needed some documentation that was better formatted than= what was available from the website and i felt it needed to be updated. Th= e documentation project looked kinda dead back then, so i decided to do som= e work because then i had a personal need for it.=20

Since the format that the HTML pages followed were very similar to LaT= eX and i already knew LaTeX, for me it seemed like an obvious choice to wri= te a parser that would convert the HTML to latex and live with that. Now if= you say that LaTeX isnt the best tool for the job, then i will have to agr= ee. But at the time i didnt have the time to learn a new tool and then writ= e parsers to convert the existing documentation to it. LaTeX seemed ok beca= use it could generate both HTML and PDF for the manuals (never really thoug= ht too much about the man page to be honest). I never thought that LaT= eX would be a final solution, but that once i got all the manual conve= rted to latex (which i never did), I could write another parser to som= e other format like docbook (or whatever it would be felt to be t= he most appropriate solution).=20

I dont intend to start a flame war over a format either, but for = an official documentation format Esther should be the most adequate person = to make the call, imho. And in my opinion a single source for all= the documentation is a must. I=B4ve been away from the community for = a while for personal reasons, but now i should have a few hours here and th= ere to work on the project helping out on what=B4s needed.=20

I=B4m sorry if i have ended up causing disburbances on the community, = I _never_ intended for that to happen. At the time i just wanted something = that would work better for me, and if it would help others, then it would a= ll good too.=20

-Renato

------=_Part_6651_31417878.1124458031704-- From tcreedon@easystreet.com Fri Aug 19 15:03:59 2005 From: tcreedon@easystreet.com (ted creedon) Date: Fri, 19 Aug 2005 07:03:59 -0700 Subject: [OpenAFS-Doc] Apologies about documentation mess In-Reply-To: <83f1799e05081906276cdf1e22@mail.gmail.com> Message-ID: <20050819140356.24C2AB029@smtpauth.easystreet.com> This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C5A48C.2CB95F90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The conversion is far more difficult than imagined because of the sophistication of the IBM docs. =20 Latex is the only viable Linux solution in my opinion and there will = have to be Perl more work to capture the IBM nuances. =20 Since the latest version of AFS doesn't work at all here, I doubt that = any further documentation effort is warranted until AFS passes rudimentary = Linux stress testing. =20 tedc _____ =20 From: openafs-doc-admin@openafs.org = [mailto:openafs-doc-admin@openafs.org] On Behalf Of renato arruda Sent: Friday, August 19, 2005 6:27 AM To: openafs-doc@openafs.org Subject: [OpenAFS-Doc] Apologies about documentation mess Hi, =20 I guess i should apologize for the mess i probably ended up making in = the documentation project. But here is my side of the story. =20 A while ago i needed some documentation that was better formatted than = what was available from the website and i felt it needed to be updated. The documentation project looked kinda dead back then, so i decided to do = some work because then i had a personal need for it.=20 =20 Since the format that the HTML pages followed were very similar to LaTeX = and i already knew LaTeX, for me it seemed like an obvious choice to write a parser that would convert the HTML to latex and live with that. Now if = you say that LaTeX isnt the best tool for the job, then i will have to = agree. But at the time i didnt have the time to learn a new tool and then write parsers to convert the existing documentation to it. LaTeX seemed ok = because it could generate both HTML and PDF for the manuals (never really = thought too much about the man page to be honest). I never thought that LaTeX = would be a final solution, but that once i got all the manual converted to = latex (which i never did), I could write another parser to some other format = like docbook (or whatever it would be felt to be the most appropriate = solution).=20 =20 I dont intend to start a flame war over a format either, but for an = official documentation format Esther should be the most adequate person to make = the call, imho. And in my opinion a single source for all the documentation = is a must. I=B4ve been away from the community for a while for personal = reasons, but now i should have a few hours here and there to work on the project helping out on what=B4s needed.=20 =20 I=B4m sorry if i have ended up causing disburbances on the community, I _never_ intended for that to happen. At the time i just wanted something that would work better for me, and if it would help others, then it = would all good too.=20 =20 -Renato ------=_NextPart_000_0003_01C5A48C.2CB95F90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

The conversion is far more difficult than = imagined because=20 of the sophistication of the IBM docs.

Latex is the only viable Linux solution in my = opinion and=20 there will have to be Perl more work to capture the IBM=20 nuances.

Since the latest version of AFS doesn't work at = all here, I=20 doubt that any further documentation effort is warranted until AFS = passes=20 rudimentary Linux stress testing.

tedc

From: openafs-doc-admin@openafs.org=20 [mailto:openafs-doc-admin@openafs.org] On Behalf Of renato=20 arruda
Sent: Friday, August 19, 2005 6:27 AM
To:=20 openafs-doc@openafs.org
Subject: [OpenAFS-Doc] Apologies about = documentation mess

Hi,

I guess i should apologize for the mess i probably ended up making = in the=20 documentation project. But here is my side of the story.

A while ago i needed some documentation that was better formatted = than what=20 was available from the website and i felt it needed to be updated. The=20 documentation project looked kinda dead back then, so i decided to do = some work=20 because then i had a personal need for it.

Since the format that the HTML pages followed were very similar to = LaTeX=20 and i already knew LaTeX, for me it seemed like an obvious choice to = write a=20 parser that would convert the HTML to latex and live with that. Now if = you say=20 that LaTeX isnt the best tool for the job, then i will have to agree. = But at the=20 time i didnt have the time to learn a new tool and then write parsers to = convert=20 the existing documentation to it. LaTeX seemed ok because it could = generate both=20 HTML and PDF for the manuals (never really thought too much = about the man=20 page to be honest). I never thought that LaTeX would be a final = solution, but=20 that once i got all the manual converted to latex (which i never=20 did), I could write another parser to some other format like = docbook (or=20 whatever it would be felt to be the most appropriate = solution).

I dont intend to start a flame war over a format either, but = for an=20 official documentation format Esther should be the most adequate person = to make=20 the call, imho. And in my opinion a single source for all the=20 documentation is a must. I=B4ve been away from the community for a = while for=20 personal reasons, but now i should have a few hours here and there to = work on=20 the project helping out on what=B4s needed.

I=B4m sorry if i have ended up causing disburbances on the = community, I=20 _never_ intended for that to happen. At the time i just wanted something = that=20 would work better for me, and if it would help others, then it would all = good=20 too.

-Renato

------=_NextPart_000_0003_01C5A48C.2CB95F90-- From rarruda0@gmail.com Tue Aug 23 10:26:41 2005 From: rarruda0@gmail.com (renato arruda) Date: Tue, 23 Aug 2005 06:26:41 -0300 Subject: [OpenAFS-Doc] docbook Message-ID: <83f1799e05082302262aca3d49@mail.gmail.com> ------=_Part_1061_11842847.1124789201738 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The PHP project uses docbook for their documentation and they have a pretty= =20 straight forward documentation on how their documentation system works. I= =20 think it might be worth taking a look. Doesnt seem to be too hard to=20 implement or require a steep learning curve for those writing the=20 documentation for the first time. http://doc.php.net/php/dochowto/index.php http://www.docbook.org/ It doesnt look very appropriate for man pages though. Anyhow, just wanted= =20 drop the link and see if that helps to have an idea on what could be done. -Renato ------=_Part_1061_11842847.1124789201738 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline The PHP project uses docbook for their documentation and they have a pretty straight forward documentation on how their documentation system works. I think it might be worth taking a look. Doesnt seem to be too hard to implement or require a steep learning curve for those writing the documentation for the first time.

http://doc.php.net/ph= p/dochowto/index.php
http://www.docbook.org/

It doesnt look very appropriate for man pages though. Anyhow, just wanted drop the link and see if that helps to have an idea on what could be done.

-Renato
------=_Part_1061_11842847.1124789201738-- From tcreedon@easystreet.com Tue Aug 23 16:07:26 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 23 Aug 2005 08:07:26 -0700 Subject: [OpenAFS-Doc] docbook In-Reply-To: <83f1799e05082302262aca3d49@mail.gmail.com> Message-ID: <20050823150720.D6AC1B00A@smtpauth.easystreet.com> This is a multi-part message in MIME format. ------=_NextPart_000_008C_01C5A7B9.B34AF6B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Looks like it would be easier to re-start with cleaned up IBM.htm. Someone should try the release notes, that's the smallest file. tedc _____ From: openafs-doc-admin@openafs.org [mailto:openafs-doc-admin@openafs.org] On Behalf Of renato arruda Sent: Tuesday, August 23, 2005 2:27 AM To: openafs-doc@openafs.org Subject: [OpenAFS-Doc] docbook The PHP project uses docbook for their documentation and they have a pretty straight forward documentation on how their documentation system works. I think it might be worth taking a look. Doesnt seem to be too hard to implement or require a steep learning curve for those writing the documentation for the first time. http://doc.php.net/php/dochowto/index.php http://www.docbook.org/ It doesnt look very appropriate for man pages though. Anyhow, just wanted drop the link and see if that helps to have an idea on what could be done. -Renato ------=_NextPart_000_008C_01C5A7B9.B34AF6B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Looks like it would be easier to re-start = with cleaned=20 up IBM.htm.

Someone should try the release notes, that's = the=20 smallest file.

tedc

From: openafs-doc-admin@openafs.org=20 [mailto:openafs-doc-admin@openafs.org] On Behalf Of renato=20 arruda
Sent: Tuesday, August 23, 2005 2:27 AM
To:=20 openafs-doc@openafs.org
Subject: [OpenAFS-Doc]=20 docbook

The PHP project uses docbook for their documentation and they = have a=20 pretty straight forward documentation on how their documentation system = works. I=20 think it might be worth taking a look. Doesnt seem to be too hard to = implement=20 or require a steep learning curve for those writing the documentation = for the=20 first time.

http://doc.php.net/php= /dochowto/index.php
http://www.docbook.org/

It = doesnt look=20 very appropriate for man pages though. Anyhow, just wanted drop the link = and see=20 if that helps to have an idea on what could be=20 done.

-Renato
------=_NextPart_000_008C_01C5A7B9.B34AF6B0-- From tcreedon@easystreet.com Tue Aug 23 16:09:41 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 23 Aug 2005 08:09:41 -0700 Subject: [OpenAFS-Doc] IBM source docs Message-ID: <20050823150935.B86472952A@smtpauth.easystreet.com> This is a multi-part message in MIME format. ------=_NextPart_000_0090_01C5A7BA.03B3FC50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Are there any contacts at IBM that could provide the original .scr files for the documentation? The IBM doc pdf and htm files appear to have been emitted using a document system possible internal to IBM. tedc ------=_NextPart_000_0090_01C5A7BA.03B3FC50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable IBM source docs

Are there any contacts at IBM that = could provide the original .scr files for the documentation?

The IBM doc pdf and htm files appear to = have been emitted using a document system possible internal to = IBM.

tedc

------=_NextPart_000_0090_01C5A7BA.03B3FC50-- From ecf@psc.edu Tue Aug 23 16:15:14 2005 From: ecf@psc.edu (Esther Filderman) Date: Tue, 23 Aug 2005 11:15:14 -0400 Subject: [OpenAFS-Doc] IBM source docs In-Reply-To: Your message of "Tue, 23 Aug 2005 08:09:41 PDT." <20050823150935.B86472952A@smtpauth.easystreet.com> Message-ID: <200508231515.j7NFFEiW018901@pscuxa.psc.edu> > Are there any contacts at IBM that could provide the original .scr files for > the documentation? > > The IBM doc pdf and htm files appear to have been emitted using a document > system possible internal to IBM. Once again: Nobody has the original source. There are IBM people on the Elders board. Nobody can find them. Lost cause. Give up asking already. From shadow@dementia.org Tue Aug 23 16:12:50 2005 From: shadow@dementia.org (Derrick J Brashear) Date: Tue, 23 Aug 2005 11:12:50 -0400 (EDT) Subject: [OpenAFS-Doc] Re: [OpenAFS] IBM source docs In-Reply-To: <20050823150935.B86472952A@smtpauth.easystreet.com> References: <20050823150935.B86472952A@smtpauth.easystreet.com> Message-ID: On Tue, 23 Aug 2005, ted creedon wrote: > Are there any contacts at IBM that could provide the original .scr files for > the documentation? Thus far they have been unable to find them. We asked, long ago. From chas@cmf.nrl.navy.mil Fri Aug 26 19:38:06 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Fri, 26 Aug 2005 14:38:06 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix Message-ID: <200508261838.j7QIc6Qh009642@thirdoffive.cmf.nrl.navy.mil> since there has seen some interest in a docbook conversion, i took a stab at converting some of the existing .htm documentation. here is a first pass at QuickStartUnix. its looks pretty good and is fully indexed. generating the .pdf with the full index is very slow so you should only do that after making your changes and are producing a "final" document. if someone has a better toolchain for docbook to pdf (with index support) i would like to hear about it. ftp://ftp.cmf.nrl.navy.mil/pub/chas/openafs/QuickStartUnix.tar.gz critiques on the conversion are welcome. the content is a bit dated and otherwise goofy (guaranties). From rra@stanford.edu Fri Aug 26 19:44:48 2005 From: rra@stanford.edu (Russ Allbery) Date: Fri, 26 Aug 2005 11:44:48 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508261838.j7QIc6Qh009642@thirdoffive.cmf.nrl.navy.mil> (chas williams's message of "Fri, 26 Aug 2005 14:38:06 -0400") References: <200508261838.j7QIc6Qh009642@thirdoffive.cmf.nrl.navy.mil> Message-ID: <87mzn44jxb.fsf@windlord.stanford.edu> chas williams - CONTRACTOR writes: > since there has seen some interest in a docbook conversion, i took a > stab at converting some of the existing .htm documentation. > here is a first pass at QuickStartUnix. its looks pretty good and is > fully indexed. generating the .pdf with the full index is very slow so > you should only do that after making your changes and are producing a > "final" document. if someone has a better toolchain for docbook to > pdf (with index support) i would like to hear about it. > ftp://ftp.cmf.nrl.navy.mil/pub/chas/openafs/QuickStartUnix.tar.gz > critiques on the conversion are welcome. the content is a bit > dated and otherwise goofy (guaranties). I like. There are a few minor problems (I noticed a stray empty bullet, for instance), but it looks like a generally high-quality conversion and gets things into a format that would be much easier to work with. The generated HTML, though, is hideous. I assume that's just a matter of finding better DocBook to HTML tools? -- Russ Allbery (rra@stanford.edu) From chas@cmf.nrl.navy.mil Fri Aug 26 21:11:23 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Fri, 26 Aug 2005 16:11:23 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <87mzn44jxb.fsf@windlord.stanford.edu> Message-ID: <200508262011.j7QKBMNA022747@ginger.cmf.nrl.navy.mil> In message <87mzn44jxb.fsf@windlord.stanford.edu>,Russ Allbery writes: >I like. There are a few minor problems (I noticed a stray empty bullet, >for instance), but it looks like a generally high-quality conversion and >gets things into a format that would be much easier to work with. the convertor isnt perfect since some of the things you can do in html arent 'structured'. figures/tables have to be converted manually and some of the list conversions are just plain wrong (which is probably what you see). >The generated HTML, though, is hideous. I assume that's just a matter of >finding better DocBook to HTML tools? i would guess its more a style sheet issue. what is your specific complaint? xmlto might be more to your liking. i couldnt figure out how to get its pdf output to generate indexes. try 'xmlto html auqbg000.xml' and open index.html From rra@stanford.edu Fri Aug 26 21:18:47 2005 From: rra@stanford.edu (Russ Allbery) Date: Fri, 26 Aug 2005 13:18:47 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508262011.j7QKBMNA022747@ginger.cmf.nrl.navy.mil> (chas williams's message of "Fri, 26 Aug 2005 16:11:23 -0400") References: <200508262011.j7QKBMNA022747@ginger.cmf.nrl.navy.mil> Message-ID: <87acj44fko.fsf@windlord.stanford.edu> "chas williams - CONTRACTOR" writes: > Russ Allbery writes: >> The generated HTML, though, is hideous. I assume that's just a matter >> of finding better DocBook to HTML tools? > i would guess its more a style sheet issue. what is your specific > complaint? Mostly all the newlines in the middle of tags, which is okay in SGML but which will confuse some browsers. > xmlto might be more to your liking. i couldnt figure out how to get its > pdf output to generate indexes. > try 'xmlto html auqbg000.xml' and open index.html I'll poke at that. Thanks! -- Russ Allbery (rra@stanford.edu) From chas@cmf.nrl.navy.mil Mon Aug 29 04:24:57 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Sun, 28 Aug 2005 23:24:57 -0400 Subject: [OpenAFS-Doc] docbook conversion update Message-ID: <200508290324.j7T3Ovgp019196@thirdoffive.cmf.nrl.navy.mil> a prelimiary docbook conversion of the userguide and adminguide are now available. the figures and tables were manually converted so they dont look right yet. i modified the gnome docbook stylesheet a bit. the pdf now has bold face where it should and the html might be more palatable. ftp://ftp.cmf.nrl.navy.mil/pub/chas/openafs/AdminGuide.tar.gz ftp://ftp.cmf.nrl.navy.mil/pub/chas/openafs/UserGuide.tar.gz after starting conversion of AdminRef i realized its essentially all the man pages in a single volume. at one point someone said the man pages might be converted to pod, so i dont see a need to convert this document. an alternative to pod though might be to convert the existing html to docbook's refentry format and generate the adminref and man pages from a single source. From rra@stanford.edu Mon Aug 29 04:33:42 2005 From: rra@stanford.edu (Russ Allbery) Date: Sun, 28 Aug 2005 20:33:42 -0700 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <200508290324.j7T3Ovgp019196@thirdoffive.cmf.nrl.navy.mil> (chas williams's message of "Sun, 28 Aug 2005 23:24:57 -0400") References: <200508290324.j7T3Ovgp019196@thirdoffive.cmf.nrl.navy.mil> Message-ID: <873botto15.fsf@windlord.stanford.edu> chas williams - CONTRACTOR writes: > after starting conversion of AdminRef i realized its essentially all the > man pages in a single volume. at one point someone said the man pages > might be converted to pod, so i dont see a need to convert this document. > an alternative to pod though might be to convert the existing html to > docbook's refentry format and generate the adminref and man pages from > a single source. I would strongly prefer to use the already-developed tools and work to convert the AdminRef to POD and maintain the man pages in POD. I find POD about an order of magnitude easier to edit and maintain than DocBook refentry. Note that this work is mostly done and I'm just waiting for 1.4 final and some final consensus to commit it to mainline and start working on it in earnest. -- Russ Allbery (rra@stanford.edu) From mizmoose@gmail.com Mon Aug 29 07:30:59 2005 From: mizmoose@gmail.com (Esther Filderman) Date: Mon, 29 Aug 2005 02:30:59 -0400 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <873botto15.fsf@windlord.stanford.edu> References: <200508290324.j7T3Ovgp019196@thirdoffive.cmf.nrl.navy.mil> <873botto15.fsf@windlord.stanford.edu> Message-ID: On 8/28/05, Russ Allbery wrote: > I'm just waiting for 1.4 > final and some final consensus to commit it to mainline and start working > on it in earnest. AkA moose get off your butt and dig into this stuff harder. will do tomorrow. p.s. don't you idjits ever sleep? :) From chas@cmf.nrl.navy.mil Mon Aug 29 13:46:19 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Mon, 29 Aug 2005 08:46:19 -0400 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <873botto15.fsf@windlord.stanford.edu> Message-ID: <200508291246.j7TCkH8a018734@ginger.cmf.nrl.navy.mil> In message <873botto15.fsf@windlord.stanford.edu>,Russ Allbery writes: >I would strongly prefer to use the already-developed tools and work to >convert the AdminRef to POD and maintain the man pages in POD. I find POD it doesnt bother me as long as you preserve enough information to convert back to docbook meaningfully so a full hardcopy of all the man pages can be printed. this means keeping the index information. pod does have some support for this with via X<>. it cant handle the primary/secondary index terms but judicious use of commas would probably be sufficient. >about an order of magnitude easier to edit and maintain than DocBook >refentry. Note that this work is mostly done and I'm just waiting for 1.4 refentry looks complicated at first, but its not too awful. pod seems more procedural, like *roff, instead of being a true markup language. but for man pages, i dont think that really matters. From rra@stanford.edu Mon Aug 29 18:48:10 2005 From: rra@stanford.edu (Russ Allbery) Date: Mon, 29 Aug 2005 10:48:10 -0700 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <200508291246.j7TCkH8a018734@ginger.cmf.nrl.navy.mil> (chas williams's message of "Mon, 29 Aug 2005 08:46:19 -0400") References: <200508291246.j7TCkH8a018734@ginger.cmf.nrl.navy.mil> Message-ID: <87irxor5wl.fsf@windlord.stanford.edu> "chas williams - CONTRACTOR" writes: > it doesnt bother me as long as you preserve enough information to > convert back to docbook meaningfully so a full hardcopy of all the man > pages can be printed. this means keeping the index information. pod > does have some support for this with via X<>. it cant handle the > primary/secondary index terms but judicious use of commas would probably > be sufficient. I'm personally not horribly interested in this. What matters to me is having really solid man pages; I don't find that sort of index to be that useful, or printing out large sheafs of man pages that useful. That being said, you can certainly get good printed output via nroff, and it shouldn't be too difficult to do a translation to DocBook. For the sort of index entries that are actually useful, I doubt you want to use X<>; indexing the page names will give you 90% of what's actually of interest for the man pages. > refentry looks complicated at first, but its not too awful. No, refentry really is awful in my opinion; I've used it. XML is not a good language for humans to work in. > pod seems more procedural, like *roff, instead of being a true markup > language. but for man pages, i dont think that really matters. It's *so* much easier to use. -- Russ Allbery (rra@stanford.edu) From chas@cmf.nrl.navy.mil Mon Aug 29 19:00:25 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Mon, 29 Aug 2005 14:00:25 -0400 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <87irxor5wl.fsf@windlord.stanford.edu> Message-ID: <200508291800.j7TI0P7H024819@ginger.cmf.nrl.navy.mil> In message <87irxor5wl.fsf@windlord.stanford.edu>,Russ Allbery writes: >having really solid man pages; I don't find that sort of index to be that >useful, or printing out large sheafs of man pages that useful. That being it might be useful for others who are not as wise in the ways of afs. an index can be helpful in finding the right "word". besides, i hate to loose information. someone indexed the man pages it would be nice to keep that work. >For the sort of index entries that are actually useful, I doubt you want >to use X<>; indexing the page names will give you 90% of what's actually >of interest for the man pages. as long as you simply preserve the existing IDX tags i dont see a problem. i can provide a mapping from IDXNNN to a string. even if you didnt in your initial conversion, it probably wouldnt be too difficult to go back through and reinsert them. From rra@stanford.edu Mon Aug 29 19:06:17 2005 From: rra@stanford.edu (Russ Allbery) Date: Mon, 29 Aug 2005 11:06:17 -0700 Subject: [OpenAFS-Doc] docbook conversion update In-Reply-To: <200508291800.j7TI0P7H024819@ginger.cmf.nrl.navy.mil> (chas williams's message of "Mon, 29 Aug 2005 14:00:25 -0400") References: <200508291800.j7TI0P7H024819@ginger.cmf.nrl.navy.mil> Message-ID: <87ek8cr52e.fsf@windlord.stanford.edu> "chas williams <- CONTRACTOR" > writes: > Russ Allbery writes: >> having really solid man pages; I don't find that sort of index to be >> that useful, or printing out large sheafs of man pages that useful. >> That being > it might be useful for others who are not as wise in the ways of afs. > an index can be helpful in finding the right "word". besides, i hate to > loose information. someone indexed the man pages it would be nice to > keep that work. Yeah, that's a good point. I'd hate to lose work. >> For the sort of index entries that are actually useful, I doubt you >> want to use X<>; indexing the page names will give you 90% of what's >> actually of interest for the man pages. > as long as you simply preserve the existing IDX tags i dont see a > problem. i can provide a mapping from IDXNNN to a string. even if you > didnt in your initial conversion, it probably wouldnt be too difficult > to go back through and reinsert them. Yeah, that shouldn't be too bad. -- Russ Allbery (rra@stanford.edu) From rarruda0@gmail.com Tue Aug 30 13:47:57 2005 From: rarruda0@gmail.com (renato arruda) Date: Tue, 30 Aug 2005 09:47:57 -0300 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508261838.j7QIc6Qh009642@thirdoffive.cmf.nrl.navy.mil> References: <200508261838.j7QIc6Qh009642@thirdoffive.cmf.nrl.navy.mil> Message-ID: <83f1799e05083005477ffcdac7@mail.gmail.com> How did you convert from html to docbook? Did you write your own parser or used a generic parser for the conversion? Is there any chance I could look at it to see if i can be of any help? -Renato On 8/26/05, chas williams - CONTRACTOR wrote: > since there has seen some interest in a docbook conversion, i took a > stab at converting some of the existing .htm documentation. >=20 > here is a first pass at QuickStartUnix. its looks pretty good and is > fully indexed. generating the .pdf with the full index is very slow so > you should only do that after making your changes and are producing a > "final" document. if someone has a better toolchain for docbook to > pdf (with index support) i would like to hear about it. >=20 > ftp://ftp.cmf.nrl.navy.mil/pub/chas/openafs/QuickStartUnix.tar.gz >=20 > critiques on the conversion are welcome. the content is a bit > dated and otherwise goofy (guaranties). > _______________________________________________ > OpenAFS-doc mailing list > OpenAFS-doc@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-doc > From dhk@ccre.com Thu Aug 25 16:27:52 2005 From: dhk@ccre.com (Dexter 'Kim' Kimball) Date: Thu, 25 Aug 2005 09:27:52 -0600 Subject: [OpenAFS] Re: [OpenAFS-Doc] IBM source docs In-Reply-To: <200508231515.j7NFFEiW018901@pscuxa.psc.edu> Message-ID: <002c01c5a989$92de19d0$31f29580@blackie> I'm pretty sure the editor du jour was an Xwindows based ugliness called "Publisher" unaffectionately referred to as "Punisher" as it was a PITA. Not that this helps :) Kim -----Original Message----- From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org] On Behalf Of Esther Filderman Sent: Tuesday, August 23, 2005 9:15 AM To: openafs-doc@openafs.org; openafs-info@openafs.org Subject: [OpenAFS] Re: [OpenAFS-Doc] IBM source docs > Are there any contacts at IBM that could provide the original .scr files for > the documentation? > > The IBM doc pdf and htm files appear to have been emitted using a document > system possible internal to IBM. Once again: Nobody has the original source. There are IBM people on the Elders board. Nobody can find them. Lost cause. Give up asking already. _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info From jaltman@secure-endpoints.com Fri Aug 26 19:52:27 2005 From: jaltman@secure-endpoints.com (Jeffrey Altman) Date: Fri, 26 Aug 2005 14:52:27 -0400 Subject: [OpenAFS-Doc] Seeking volunteer(s) to update the Windows OpenAFS Wiki pages Message-ID: <430F64EB.6000309@secure-endpoints.com> This is a cryptographically signed message in MIME format. --------------ms010209050406010304080304 Content-Type: multipart/mixed; boundary="------------000300040501050407080205" This is a multi-part message in MIME format. --------------000300040501050407080205 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Last summer Tommie Gannert put together a set of Wiki pages linked off of http://grand.central.org/twiki/bin/view/AFSLore/NewWindowsDocumentation that attempt to provide the basis for a new set of manuals for OpenAFS for Windows. Since February I have been unable to reach Tommie and I am looking for a volunteer to update these pages for the 1.4 release. 1.3.70 was current when they were written. The source of information for these pages are the text files that I put together for each release. I can provide any volunteer the changes since 1.3.70 to use as part of their effort. After the pages are updated for 1.4 I would like to see them linked to from the AFSLore home page: http://grand.central.org/twiki/bin/view/AFSLore/WebHome Thanks for your assistance. Jeffrey Altman --------------000300040501050407080205 Content-Type: text/x-vcard; charset=utf-8; name="jaltman.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="jaltman.vcf" begin:vcard fn:Jeffrey Altman n:Altman;Jeffrey org:Secure Endpoints Inc. adr:;;255 W 94TH ST PHB;NEW YORK;NY;10025;United States email;internet:jaltman@secure-endpoints.com title:President tel;work:+1 212 769-9018 x-mozilla-html:TRUE url:http://www.secure-endpoints.com version:2.1 end:vcard --------------000300040501050407080205-- --------------ms010209050406010304080304 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJXzCC AwowggJzoAMCAQICAw7NrTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDUwNTI3MTc0NzU3WhcNMDYwNTI3MTc0NzU3 WjBzMQ8wDQYDVQQEEwZBbHRtYW4xFTATBgNVBCoTDEplZmZyZXkgRXJpYzEcMBoGA1UEAxMT SmVmZnJleSBFcmljIEFsdG1hbjErMCkGCSqGSIb3DQEJARYcamFsdG1hbkBzZWN1cmUtZW5k cG9pbnRzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKjPyrF+rdjOUSK/ bWwZHdx5p1+y6iiCd4vvYEVDxouYFp5C/fZEWm5n45ubBUbMSUI1MAZN6ooEoH09UTj6BXhM S8B987ls81dKOIUphTF2jOzq8gsFmeA15yHMRAD20LqUWeLyvYk8FCNQw+dsKMMhX+WdsxOm RY/1jPkJL6oN8kEwoUFkOX9/OfWWh6oFnV6faiEHUKDMFubsb9X0KVD8iIeR7Cxz7i4kXqRX wMlp2fyoxcDIJrBaTY8nA++g3p34IkWt1a5po6g683nIgSnGpwYIwuJheBqSEZfLYWa+1KdD 6Sn27Ud94GqUvPVG5jC6zVC5EJ2aWuoAu+nNuV8CAwEAAaM5MDcwJwYDVR0RBCAwHoEcamFs dG1hbkBzZWN1cmUtZW5kcG9pbnRzLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA A4GBADtvO//tjiAV6VJGtoNtrl34mB5jGyGTiotzw8riB6zz0GvY11bcWDmp6JKif+pVG+8L IySDosbuva13qu2HwYUxBmWc7CoNd2k9kRlcrfbDUTTrGOZK8qyqNqT3gQZTAa9ZnUI0su9G y/n2o5bQcaYdqR3htNrpvdLSPOWhILOXMIIDCjCCAnOgAwIBAgIDDs2tMA0GCSqGSIb3DQEB BAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBM dGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0w NTA1MjcxNzQ3NTdaFw0wNjA1MjcxNzQ3NTdaMHMxDzANBgNVBAQTBkFsdG1hbjEVMBMGA1UE KhMMSmVmZnJleSBFcmljMRwwGgYDVQQDExNKZWZmcmV5IEVyaWMgQWx0bWFuMSswKQYJKoZI hvcNAQkBFhxqYWx0bWFuQHNlY3VyZS1lbmRwb2ludHMuY29tMIIBIjANBgkqhkiG9w0BAQEF AAOCAQ8AMIIBCgKCAQEAqM/KsX6t2M5RIr9tbBkd3HmnX7LqKIJ3i+9gRUPGi5gWnkL99kRa bmfjm5sFRsxJQjUwBk3qigSgfT1ROPoFeExLwH3zuWzzV0o4hSmFMXaM7OryCwWZ4DXnIcxE APbQupRZ4vK9iTwUI1DD52wowyFf5Z2zE6ZFj/WM+Qkvqg3yQTChQWQ5f3859ZaHqgWdXp9q IQdQoMwW5uxv1fQpUPyIh5HsLHPuLiRepFfAyWnZ/KjFwMgmsFpNjycD76DenfgiRa3Vrmmj qDrzeciBKcanBgjC4mF4GpIRl8thZr7Up0PpKfbtR33gapS89UbmMLrNULkQnZpa6gC76c25 XwIDAQABozkwNzAnBgNVHREEIDAegRxqYWx0bWFuQHNlY3VyZS1lbmRwb2ludHMuY29tMAwG A1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAO287/+2OIBXpUka2g22uXfiYHmMbIZOK i3PDyuIHrPPQa9jXVtxYOanokqJ/6lUb7wsjJIOixu69rXeq7YfBhTEGZZzsKg13aT2RGVyt 9sNRNOsY5kryrKo2pPeBBlMBr1mdQjSy70bL+fajltBxph2pHeG02um90tI85aEgs5cwggM/ MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMM V2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25z dWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYD VQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNv bmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5 WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRk LjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2 vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9 A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEw EgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0 ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0R BCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GB AEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZ Ohl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVN d+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDOzCCAzcCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAw7NrTAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNTA4MjYxODUyMjdaMCMGCSqG SIb3DQEJBDEWBBSys/TPHuj4ymHPPMthRdE5iBy1ETBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqG SIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG 9w0DAgIBKDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3 dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgSXNzdWluZyBDQQIDDs2tMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJa QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAw7NrTANBgkqhkiG9w0BAQEFAASC AQCZlRu2LA6kjPV4s19HQG2O38I1pPiPE0zyB4USJLna0VRbOJa/s/0pTMBCb8zrhZb9DyPw IrTx+vsgR361J/fmbUWtIlpad/nLlHF8MTdTAhKIPh27M7Vqr5PxlhMHvKW5dhIPmRuFO16l wA+hNZDNTHKNIdeWHfO1rElpMdFtTUKtDzxz6YuagUrN3WTH8NReXYX+nS8qLaCfnUqDbU5R WxhR0z77/Q+rg3Sr1BWLHS3P2Ec7lJYu7Wr7m6+M4WpyRuqoUWbEt5bvN8LlyMatcWoUOMF0 4DwQ0+oaqVjyrlpOKdinA7pOYLKg/kCe02Hz6DPUjD5ILhh2nF3qnZi8AAAAAAAA --------------ms010209050406010304080304-- From chas@cmf.nrl.navy.mil Tue Aug 30 15:21:21 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Tue, 30 Aug 2005 10:21:21 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <83f1799e05083005477ffcdac7@mail.gmail.com> Message-ID: <200508301421.j7UELKgo015388@ginger.cmf.nrl.navy.mil> In message <83f1799e05083005477ffcdac7@mail.gmail.com>,renato arruda writes: >How did you convert from html to docbook? Did you write your own >parser or used a generic parser for the conversion? Is there any >chance I could look at it to see if i can be of any help? i used this patch to an older version of tidy to do the bulk of the conversion: http://sourceforge.net/mailarchive/forum.php?forum_id=1650&style=flat&viewday=1&viewmonth=200207 i had to make a few modifications (modify hN handling, multiple text nodes, and some list changes) and they arent very pretty. you dont get to see my brain damaged coding). some assorted perl scripts removed the headers and footers, extracted and reinserted the index terms. things that dont have a clear representation in html, like figures and tables need to be converted manually. i pretty happy with the existing conversion. only the windows quickstart document need converted although its more likely its entire content will need replaced. I suppose i could convert the 3.6 releasenotes as well but they should be written from scratch for the 1.4 release. From tcreedon@easystreet.com Tue Aug 30 16:32:24 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 30 Aug 2005 08:32:24 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508301421.j7UELKgo015388@ginger.cmf.nrl.navy.mil> Message-ID: <20050830153214.7BB1DB038@smtpauth.easystreet.com> The aforementined htmltolatex perl script on my ftp server does all that, tables, figures, etc. All you have to do is emit docbook instead of tex. Html2latex parses the tided up html and stores it in an internal tree structure. tedc -----Original Message----- From: openafs-doc-admin@openafs.org [mailto:openafs-doc-admin@openafs.org] On Behalf Of chas williams - CONTRACTOR Sent: Tuesday, August 30, 2005 7:21 AM To: renato arruda Cc: openafs-doc@openafs.org Subject: Re: [OpenAFS-Doc] docbook conversion of QuickStartUnix In message <83f1799e05083005477ffcdac7@mail.gmail.com>,renato arruda writes: >How did you convert from html to docbook? Did you write your own parser >or used a generic parser for the conversion? Is there any chance I >could look at it to see if i can be of any help? i used this patch to an older version of tidy to do the bulk of the conversion: http://sourceforge.net/mailarchive/forum.php?forum_id=1650&style=flat&viewda y=1&viewmonth=200207 i had to make a few modifications (modify hN handling, multiple text nodes, and some list changes) and they arent very pretty. you dont get to see my brain damaged coding). some assorted perl scripts removed the headers and footers, extracted and reinserted the index terms. things that dont have a clear representation in html, like figures and tables need to be converted manually. i pretty happy with the existing conversion. only the windows quickstart document need converted although its more likely its entire content will need replaced. I suppose i could convert the 3.6 releasenotes as well but they should be written from scratch for the 1.4 release. _______________________________________________ OpenAFS-doc mailing list OpenAFS-doc@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-doc From mizmoose@gmail.com Tue Aug 30 16:35:20 2005 From: mizmoose@gmail.com (Esther Filderman) Date: Tue, 30 Aug 2005 11:35:20 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <20050830153214.7BB1DB038@smtpauth.easystreet.com> References: <200508301421.j7UELKgo015388@ginger.cmf.nrl.navy.mil> <20050830153214.7BB1DB038@smtpauth.easystreet.com> Message-ID: On 8/30/05, ted creedon wrote: > The aforementined htmltolatex perl script on my ftp server does all that, > tables, figures, etc. >=20 > All you have to do is emit docbook instead of tex. Html2latex parses the > tided up html and stores it in an internal tree structure. That's nice, except we're not storing things in Latex format, we're storing things in DocBook format. From chas@cmf.nrl.navy.mil Tue Aug 30 16:44:43 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Tue, 30 Aug 2005 11:44:43 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <20050830153214.7BB1DB038@smtpauth.easystreet.com> Message-ID: <200508301544.j7UFih3C017017@ginger.cmf.nrl.navy.mil> In message <20050830153214.7BB1DB038@smtpauth.easystreet.com>,"ted creedon" wri tes: >The aforementined htmltolatex perl script on my ftp server does all that, >tables, figures, etc. it was something like 3 tables. it didnt even require my two working brain cells. the figures (gifs of a text display no less) seem to be missing completely. From tcreedon@easystreet.com Tue Aug 30 17:23:26 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 30 Aug 2005 09:23:26 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: Message-ID: <20050830162317.07B52B00A@smtpauth.easystreet.com> Its parsed and stored as XML internally, you don't need to emit as Latex you can emit as docbook. tedc -----Original Message----- From: openafs-doc-admin@openafs.org [mailto:openafs-doc-admin@openafs.org] On Behalf Of Esther Filderman Sent: Tuesday, August 30, 2005 8:35 AM To: openafs-doc@openafs.org Subject: Re: [OpenAFS-Doc] docbook conversion of QuickStartUnix On 8/30/05, ted creedon wrote: > The aforementined htmltolatex perl script on my ftp server does all > that, tables, figures, etc. > > All you have to do is emit docbook instead of tex. Html2latex parses > the tided up html and stores it in an internal tree structure. That's nice, except we're not storing things in Latex format, we're storing things in DocBook format. _______________________________________________ OpenAFS-doc mailing list OpenAFS-doc@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-doc From tcreedon@easystreet.com Tue Aug 30 17:25:50 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 30 Aug 2005 09:25:50 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508301544.j7UFih3C017017@ginger.cmf.nrl.navy.mil> Message-ID: <20050830162540.C4CD12951D@smtpauth.easystreet.com> Wait until you try the admin reference and guide. They're full of tables. tedc -----Original Message----- From: openafs-doc-admin@openafs.org [mailto:openafs-doc-admin@openafs.org] On Behalf Of chas williams - CONTRACTOR Sent: Tuesday, August 30, 2005 8:45 AM To: ted creedon Cc: 'renato arruda'; openafs-doc@openafs.org Subject: Re: [OpenAFS-Doc] docbook conversion of QuickStartUnix In message <20050830153214.7BB1DB038@smtpauth.easystreet.com>,"ted creedon" wri tes: >The aforementined htmltolatex perl script on my ftp server does all >that, tables, figures, etc. it was something like 3 tables. it didnt even require my two working brain cells. the figures (gifs of a text display no less) seem to be missing completely. _______________________________________________ OpenAFS-doc mailing list OpenAFS-doc@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-doc From chas@cmf.nrl.navy.mil Tue Aug 30 18:09:30 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Tue, 30 Aug 2005 13:09:30 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <20050830162540.C4CD12951D@smtpauth.easystreet.com> Message-ID: <200508301709.j7UH9Ueg018745@ginger.cmf.nrl.navy.mil> In message <20050830162540.C4CD12951D@smtpauth.easystreet.com>,"ted creedon" wr ites: >Wait until you try the admin reference and guide. They're full of tables. the admin reference is going to be pod apparently. a manual can be generated from the pod. i converted the adminguide already. four tables and nine figures. not very difficult. From tcreedon@easystreet.com Tue Aug 30 22:14:12 2005 From: tcreedon@easystreet.com (ted creedon) Date: Tue, 30 Aug 2005 14:14:12 -0700 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <200508301709.j7UH9Ueg018745@ginger.cmf.nrl.navy.mil> Message-ID: <20050830211402.C8C86B0A3@smtpauth.easystreet.com> #grep /TD *.htm|wc -l #1321 tedc -----Original Message----- From: chas williams - CONTRACTOR [mailto:chas@cmf.nrl.navy.mil] Sent: Tuesday, August 30, 2005 10:10 AM To: ted creedon Cc: 'renato arruda'; openafs-doc@openafs.org Subject: Re: [OpenAFS-Doc] docbook conversion of QuickStartUnix In message <20050830162540.C4CD12951D@smtpauth.easystreet.com>,"ted creedon" wr ites: >Wait until you try the admin reference and guide. They're full of tables. the admin reference is going to be pod apparently. a manual can be generated from the pod. i converted the adminguide already. four tables and nine figures. not very difficult. From chas@cmf.nrl.navy.mil Tue Aug 30 22:22:38 2005 From: chas@cmf.nrl.navy.mil (chas williams - CONTRACTOR) Date: Tue, 30 Aug 2005 17:22:38 -0400 Subject: [OpenAFS-Doc] docbook conversion of QuickStartUnix In-Reply-To: <20050830211402.C8C86B0A3@smtpauth.easystreet.com> Message-ID: <200508302122.j7ULMc12024903@ginger.cmf.nrl.navy.mil> In message <20050830211402.C8C86B0A3@smtpauth.easystreet.com>,"ted creedon" wri tes: >#grep /TD *.htm|wc -l >#1321 uhhh... yeah? TD = table data, not a table. there are four "formal" tables and around 20 "informal" tables (docbook speak).