RE: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 15)
To all who gave their ideas on Unlocking Pgf Locked, thanks. Richard Combs unlocked the secret! Jing Torralba -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 14, 2006 11:01 PM To: framers@lists.frameusers.com Subject: Framers Digest, Vol 14, Issue 15 Send Framers mailing list submissions to framers@lists.frameusers.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.frameusers.com/mailman/listinfo/framers or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Framers digest..." Today's Topics: 1. checking location of graphics (Karen Mardahl) 2. Re: checking location of graphics (Rick Quatro) 3. Re: Searching in text insets (Shmuel Wolfson) 4. Difference between us and international english Framemaker (Andersen, Verner Engell VEA) 5. Re: DTD graphic tool? (Wolfgang K?hn) 6. RE: Difference between us and international english Framemaker (Phil Heron) 7. RE: Difference between us and international english Framemaker (Gillian Flato) 8. RE: Difference between us and international english Framemaker (Steve Rickaby) 9. RE: Difference between us and international english Framemaker (Mark Southee) 10. RE: Cross reference keyboard shortcut (Conole, David (SNL US)) 11. RE: Unlocking "Pgf Locked" (Combs, Richard) 12. RE: Unlocking "Pgf Locked" (Steve Rickaby) 13. RE: Unlocking "Pgf Locked" (Combs, Richard) 14. RE: Difference between us and international english Framemaker ([EMAIL PROTECTED]) 15. Heading rows overridden in table (Susan Nishi) 16. RE: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14) (Torralba, Jing) 17. Re: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14) (Peter Gold) -- Message: 1 Date: Thu, 14 Dec 2006 11:02:10 +0100 From: "Karen Mardahl" <[EMAIL PROTECTED]> Subject: checking location of graphics To: framers@lists.frameusers.com Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi How can I be sure that a linked graphic is where it is supposed to be? I just had a situation where the reviewer of my doc had trouble because the graphic wasn't where it was supposed to be for him. Under Edit > Links, the particular graphic is shown in the window as ...\.vsd with Type Visio and Update Automatic For source, it states \\server\...\Graphics\.vsd The path is a bit long, so I get three dots instead of the full path. Policy is to have all graphics in a folder called Graphics, so everything looks great to me. I will never see a problem because I only use the one server. The fastest way to determine whether the location is truly correct, is to click Change Source and open the Look in drop-down menu. Only then can I see something is wrong. With 69 graphics, this procedure is a pain. Other docs have twice as many. The dialog box cannot be widened. How can I easily check that locations are correct as a part of my preparing-for-review process? I just had a case where the graphic was recycled. A copy of the graphic was in the correct, new folder, but my pointer was to the original in another location. This could be disastrous if I made any updates to the graphic. I'd be updating the wrong one and not know it. During review, the person doing a new build of the document in FM ran into big trouble. The other folder I was using (unknowingly) is in Denmark. He is in California. Framemaker hung for ages. At least we got an error message, and I could track down the miscreant, but this happens at a time when time is at a premium (of course). I know about http://home.comcast.net/~bruce.foster/Archive.htm, but I want to know the status before taking that step. I have FrameScript if someone thinks that is the route to go. A List of References doesn't work, because these are .vsd files imported as objects. Thanks. regards, Karen Mardahl -- Message: 2 Date: Thu, 14 Dec 2006 07:16:14 -0500 From: "Rick Quatro" <[EMAIL PROTECTED]> Subject: Re: checking location of graphics To: "Karen Mardahl" <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Hi Karen, Unfortunately, FrameScript won't help because it "sees" imported OLE objects as if they were imported by copy. In other words, FrameScript (or the FDK) cannot determine the path to an OLE object. Rick Quatro Carmen Pu
Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 15)
To all who gave their ideas on Unlocking Pgf Locked, thanks. Richard Combs unlocked the secret! Jing Torralba -Original Message- From: framers-bounces+jtorralba=saratogasystems.com at lists.frameusers.com [mailto:framers-bounces+jtorralba=saratogasystems.com at lists.frameusers.com] On Behalf Of framers-requ...@lists.frameusers.com Sent: Thursday, December 14, 2006 11:01 PM To: framers at lists.frameusers.com Subject: Framers Digest, Vol 14, Issue 15 Send Framers mailing list submissions to framers at lists.frameusers.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.frameusers.com/mailman/listinfo/framers or, via email, send a message with subject or body 'help' to framers-request at lists.frameusers.com You can reach the person managing the list at framers-owner at lists.frameusers.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Framers digest..." Today's Topics: 1. checking location of graphics (Karen Mardahl) 2. Re: checking location of graphics (Rick Quatro) 3. Re: Searching in text insets (Shmuel Wolfson) 4. Difference between us and international english Framemaker (Andersen, Verner Engell VEA) 5. Re: DTD graphic tool? (Wolfgang K?hn) 6. RE: Difference between us and international english Framemaker (Phil Heron) 7. RE: Difference between us and international english Framemaker (Gillian Flato) 8. RE: Difference between us and international english Framemaker (Steve Rickaby) 9. RE: Difference between us and international english Framemaker (Mark Southee) 10. RE: Cross reference keyboard shortcut (Conole, David (SNL US)) 11. RE: Unlocking "Pgf Locked" (Combs, Richard) 12. RE: Unlocking "Pgf Locked" (Steve Rickaby) 13. RE: Unlocking "Pgf Locked" (Combs, Richard) 14. RE: Difference between us and international english Framemaker (hedley.finger at myob.com) 15. Heading rows overridden in table (Susan Nishi) 16. RE: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14) (Torralba, Jing) 17. Re: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14) (Peter Gold) -- Message: 1 Date: Thu, 14 Dec 2006 11:02:10 +0100 From: "Karen Mardahl" Subject: checking location of graphics To: framers at lists.frameusers.com Message-ID: <60e0e50d0612140202i755deb36h3b3bd556cf7c92f5 at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi How can I be sure that a linked graphic is where it is supposed to be? I just had a situation where the reviewer of my doc had trouble because the graphic wasn't where it was supposed to be for him. Under Edit > Links, the particular graphic is shown in the window as ...\.vsd with Type Visio and Update Automatic For source, it states \\server\...\Graphics\.vsd The path is a bit long, so I get three dots instead of the full path. Policy is to have all graphics in a folder called Graphics, so everything looks great to me. I will never see a problem because I only use the one server. The fastest way to determine whether the location is truly correct, is to click Change Source and open the Look in drop-down menu. Only then can I see something is wrong. With 69 graphics, this procedure is a pain. Other docs have twice as many. The dialog box cannot be widened. How can I easily check that locations are correct as a part of my preparing-for-review process? I just had a case where the graphic was recycled. A copy of the graphic was in the correct, new folder, but my pointer was to the original in another location. This could be disastrous if I made any updates to the graphic. I'd be updating the wrong one and not know it. During review, the person doing a new build of the document in FM ran into big trouble. The other folder I was using (unknowingly) is in Denmark. He is in California. Framemaker hung for ages. At least we got an error message, and I could track down the miscreant, but this happens at a time when time is at a premium (of course). I know about http://home.comcast.net/~bruce.foster/Archive.htm, but I want to know the status before taking that step. I have FrameScript if someone thinks that is the route to go. A List of References doesn't work, because these are .vsd files imported as objects. Thanks. regards, Karen Mardahl -- Message: 2 Date: Thu, 14 Dec 2006 07:16:14 -0500 From: "Rick Quatro" Subject: Re: checking location of graphics To: "Karen Mardahl" , Message-ID: <000b01c71f79$a67926d0$4217414a at CARMENOFFICE> Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Hi Karen, Unfortunately, FrameScript won't help because it
Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14)
I don't have a real clue, but I'm wondering if perhaps the status of the inset source file could cause this to happen. This is just a wild guess: For example, if the source file is set to read-only, or the author doesn't have sufficient permission to access the file, or perhaps the file is in a checked-out state from a content-management system, do these cause the problem? We have seen that there's a problem with insets sometimes affecting adjacent paragraphs in the container file. Perhaps a combination of these and/or similar factors is involved. Another thought: is it possible that the inset source files and/or the container files belong to more than one book, or more than one author, and there are multiple simultaneous accesses involved? And one more: are these files on a network file server, or on a local drive? Does the problem occur only on server-based files, or only on local files, or no significant relation to either? HTH Regards, Peter Gold KnowHow ProServices Torralba, Jing wrote: > Hi Fred, > > I'm so glad you brought this subject up. > > I found the same problem in some of the files I inherited from the > previous staff. It's awful because the generated paragraph is sometimes > an AppendixNum. I tried your solution but perhaps I'm missing something > because it did not work for me. All my paratags have PgfLocked set to > No. Can you share more details? Incidentally, this is my first time to > work with MIFs. > > Does anyone know if the auto-generated paratag after an inset still > shows up in Frame 7? >
Re: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14)
I don't have a real clue, but I'm wondering if perhaps the status of the inset source file could cause this to happen. This is just a wild guess: For example, if the source file is set to read-only, or the author doesn't have sufficient permission to access the file, or perhaps the file is in a checked-out state from a content-management system, do these cause the problem? We have seen that there's a problem with insets sometimes affecting adjacent paragraphs in the container file. Perhaps a combination of these and/or similar factors is involved. Another thought: is it possible that the inset source files and/or the container files belong to more than one book, or more than one author, and there are multiple simultaneous accesses involved? And one more: are these files on a network file server, or on a local drive? Does the problem occur only on server-based files, or only on local files, or no significant relation to either? HTH Regards, Peter Gold KnowHow ProServices Torralba, Jing wrote: Hi Fred, I'm so glad you brought this subject up. I found the same problem in some of the files I inherited from the previous staff. It's awful because the generated paragraph is sometimes an AppendixNum. I tried your solution but perhaps I'm missing something because it did not work for me. All my paratags have PgfLocked set to No. Can you share more details? Incidentally, this is my first time to work with MIFs. Does anyone know if the auto-generated paratag after an inset still shows up in Frame 7? ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Unlocking "Pgf Locked"
Richard Many thanks for a clear exposition of this oh-so-irritating and confusing bug. Am I correct in assuming that this affects only formatted insets, and not plain ASCII insert files? (As they contain no formatting...) -- Steve
RE: Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14)
Hi Fred, I'm so glad you brought this subject up. I found the same problem in some of the files I inherited from the previous staff. It's awful because the generated paragraph is sometimes an AppendixNum. I tried your solution but perhaps I'm missing something because it did not work for me. All my paratags have PgfLocked set to No. Can you share more details? Incidentally, this is my first time to work with MIFs. Does anyone know if the auto-generated paratag after an inset still shows up in Frame 7? Jing Torralba Saratoga Systems, Inc. (408) 558-9606 -Original Message- Message: 16 Date: Wed, 13 Dec 2006 18:07:25 -0800 From: "Fred Staal" <[EMAIL PROTECTED]> Subject: Unlocking "Pgf Locked" To: Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Every now and then I get stuck with one of those auto-generated paragraphs that appears after a text inset that refuses to cooperate with being retagged for the subsequent paragraph and can't even be deleted. As a last resort, I recently converted a file with this problem to a .mif and in Notepad found the offending paragraph, which included the following notation: "Pgf Locked." When I deleted this line, and then opened the file in FM, the paragraph tag could be deleted. Is there a keyboard shortcut in Framemaker for unlocking a paragraph with this problem? (FM6, XP, etc.) Fred Staal Supervisor, Technical Publications Schilling Robotics, LLC Phone: (530) 753-6718 x155 Fax: (530) 753-8092 [EMAIL PROTECTED] -- ___ You are currently subscribed to Framers. To unsubscribe send a blank email to http://lists.frameusers.com/mailman/listinfo/framers Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. End of Framers Digest, Vol 14, Issue 14 *** ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Unlocking Pgf Locked (Framers Digest, Vol 14, Issue 14)
Hi Fred, I'm so glad you brought this subject up. I found the same problem in some of the files I inherited from the previous staff. It's awful because the generated paragraph is sometimes an AppendixNum. I tried your solution but perhaps I'm missing something because it did not work for me. All my paratags have PgfLocked set to No. Can you share more details? Incidentally, this is my first time to work with MIFs. Does anyone know if the auto-generated paratag after an inset still shows up in Frame 7? Jing Torralba Saratoga Systems, Inc. (408) 558-9606 -Original Message- Message: 16 Date: Wed, 13 Dec 2006 18:07:25 -0800 From: "Fred Staal" Subject: Unlocking "Pgf Locked" To: Message-ID: <825CF3FE62B1D54A8D41BBE45AF941AF01E6F9BF at EX20DAV.schilling.loc> Content-Type: text/plain; charset="us-ascii" Every now and then I get stuck with one of those auto-generated paragraphs that appears after a text inset that refuses to cooperate with being retagged for the subsequent paragraph and can't even be deleted. As a last resort, I recently converted a file with this problem to a .mif and in Notepad found the offending paragraph, which included the following notation: "Pgf Locked." When I deleted this line, and then opened the file in FM, the paragraph tag could be deleted. Is there a keyboard shortcut in Framemaker for unlocking a paragraph with this problem? (FM6, XP, etc.) Fred Staal Supervisor, Technical Publications Schilling Robotics, LLC Phone: (530) 753-6718 x155 Fax: (530) 753-8092 fred.staal at schilling.com -- ___ You are currently subscribed to Framers. To unsubscribe send a blank email to http://lists.frameusers.com/mailman/listinfo/framers Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info. End of Framers Digest, Vol 14, Issue 14 ***
Unlocking "Pgf Locked"
Steve Rickaby wrote: > Richard > > Many thanks for a clear exposition of this oh-so-irritating > and confusing bug. > > Am I correct in assuming that this affects only formatted > insets, and not plain ASCII insert files? (As they contain no > formatting...) You're welcome, Steve. The only plain text insets I can think of (some Java code examples) are followed by non-breaking spaces -- but I think that's just habit. :-) I'm sure your assumption is correct -- the container can't "inherit" a named pgf format from an inset that doesn't contain pgf format names. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Unlocking "Pgf Locked"
Fred Staal wrote: > Every now and then I get stuck with one of those > auto-generated paragraphs that appears after a text inset > that refuses to cooperate with being retagged for the > subsequent paragraph and can't even be deleted. As a last > resort, I recently converted a file with this problem to a > .mif and in Notepad found the offending paragraph, which > included the following notation: "Pgf Locked." When I deleted > this line, and then opened the file in FM, the paragraph tag > could be deleted. > Is there a keyboard shortcut in Framemaker for unlocking a > paragraph with this problem? (FM6, XP, etc.) I don't understand what you did in the MIF and have never heard of locking/unlocking pgfs, but I have some insight regarding how text insets work that may help. There's no such thing as an "auto-generated paragraph that appears after a text inset." There can, however, be an undesired pgf format change. Do you work with View > Text Symbols turned on? You should. You can't tell what's going on with text insets (among other things) if you don't see the pilcrows (end-of-pgf symbols) at the end of each pgf. A text inset always "sits in" a container paragraph in the destination document. The container pgf is the place that your text cursor was when you executed the File > Import > File command to import the text inset. If you're like most people, this was at the end of a pgf, and often it's an otherwise empty pgf. If you have text symbols showing, how this works becomes obvious when you click your text inset to select it. You'll see that the literal "black box" of the selected text inset ends just to left of the pilcrow (if the text inset is in an empty pgf). The problem with this stems from a weird FM bug: If the text inset is the only thing in the container pgf, or if it comes at the end of the container pgf, the container pgf assumes the formatting of the first pgf in the text inset. This can cause some serious grief if, for instance, that first pgf is a 24-point heading. There's an easy solution: Don't let your text insets sit at the end of a paragraph (adjacent to the pilcrow). Make sure there is something -- anything -- to the right of the cursor before you import the text inset. I use non-breaking spaces so that I can see the symbol (I always work with text symbols displayed). For existing text insets, just insert something -- anything -- between the end of the text inset and the end of the container pgf. Then you can change the container pgf's format, and the change will stick. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
RE: Unlocking "Pgf Locked"
Steve Rickaby wrote: > Richard > > Many thanks for a clear exposition of this oh-so-irritating > and confusing bug. > > Am I correct in assuming that this affects only formatted > insets, and not plain ASCII insert files? (As they contain no > formatting...) You're welcome, Steve. The only plain text insets I can think of (some Java code examples) are followed by non-breaking spaces -- but I think that's just habit. :-) I'm sure your assumption is correct -- the container can't "inherit" a named pgf format from an inset that doesn't contain pgf format names. Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Unlocking "Pgf Locked"
Richard Many thanks for a clear exposition of this oh-so-irritating and confusing bug. Am I correct in assuming that this affects only formatted insets, and not plain ASCII insert files? (As they contain no formatting...) -- Steve ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: Unlocking "Pgf Locked"
Fred Staal wrote: > Every now and then I get stuck with one of those > auto-generated paragraphs that appears after a text inset > that refuses to cooperate with being retagged for the > subsequent paragraph and can't even be deleted. As a last > resort, I recently converted a file with this problem to a > .mif and in Notepad found the offending paragraph, which > included the following notation: "Pgf Locked." When I deleted > this line, and then opened the file in FM, the paragraph tag > could be deleted. > Is there a keyboard shortcut in Framemaker for unlocking a > paragraph with this problem? (FM6, XP, etc.) I don't understand what you did in the MIF and have never heard of locking/unlocking pgfs, but I have some insight regarding how text insets work that may help. There's no such thing as an "auto-generated paragraph that appears after a text inset." There can, however, be an undesired pgf format change. Do you work with View > Text Symbols turned on? You should. You can't tell what's going on with text insets (among other things) if you don't see the pilcrows (end-of-pgf symbols) at the end of each pgf. A text inset always "sits in" a container paragraph in the destination document. The container pgf is the place that your text cursor was when you executed the File > Import > File command to import the text inset. If you're like most people, this was at the end of a pgf, and often it's an otherwise empty pgf. If you have text symbols showing, how this works becomes obvious when you click your text inset to select it. You'll see that the literal "black box" of the selected text inset ends just to left of the pilcrow (if the text inset is in an empty pgf). The problem with this stems from a weird FM bug: If the text inset is the only thing in the container pgf, or if it comes at the end of the container pgf, the container pgf assumes the formatting of the first pgf in the text inset. This can cause some serious grief if, for instance, that first pgf is a 24-point heading. There's an easy solution: Don't let your text insets sit at the end of a paragraph (adjacent to the pilcrow). Make sure there is something -- anything -- to the right of the cursor before you import the text inset. I use non-breaking spaces so that I can see the symbol (I always work with text symbols displayed). For existing text insets, just insert something -- anything -- between the end of the text inset and the end of the container pgf. Then you can change the container pgf's format, and the change will stick. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Unlocking "Pgf Locked"
Every now and then I get stuck with one of those auto-generated paragraphs that appears after a text inset that refuses to cooperate with being retagged for the subsequent paragraph and can't even be deleted. As a last resort, I recently converted a file with this problem to a .mif and in Notepad found the offending paragraph, which included the following notation: "Pgf Locked." When I deleted this line, and then opened the file in FM, the paragraph tag could be deleted. Is there a keyboard shortcut in Framemaker for unlocking a paragraph with this problem? (FM6, XP, etc.) Fred Staal Supervisor, Technical Publications Schilling Robotics, LLC Phone: (530) 753-6718 x155 Fax: (530) 753-8092 fred.staal at schilling.com
Unlocking "Pgf Locked"
Every now and then I get stuck with one of those auto-generated paragraphs that appears after a text inset that refuses to cooperate with being retagged for the subsequent paragraph and can't even be deleted. As a last resort, I recently converted a file with this problem to a .mif and in Notepad found the offending paragraph, which included the following notation: "Pgf Locked." When I deleted this line, and then opened the file in FM, the paragraph tag could be deleted. Is there a keyboard shortcut in Framemaker for unlocking a paragraph with this problem? (FM6, XP, etc.) Fred Staal Supervisor, Technical Publications Schilling Robotics, LLC Phone: (530) 753-6718 x155 Fax: (530) 753-8092 [EMAIL PROTECTED] ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
