summaryrefslogtreecommitdiff
path: root/sci-chemistry/pdbcat/metadata.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@koprulu.sector>2022-10-20 07:59:50 +0100
committerV3n3RiX <venerix@koprulu.sector>2022-10-20 07:59:50 +0100
commit2eda3a3b8ebdb3fc8552feb6f49e466d3bc8e88c (patch)
tree69a469da2fa8c3f4920325ac5595300929f5d884 /sci-chemistry/pdbcat/metadata.xml
parent9ed0c42eb618229fa6f45e10155ee535e1f605a2 (diff)
gentoo auto-resync : 20:10:2022 - 07:59:49
Diffstat (limited to 'sci-chemistry/pdbcat/metadata.xml')
-rw-r--r--sci-chemistry/pdbcat/metadata.xml30
1 files changed, 15 insertions, 15 deletions
diff --git a/sci-chemistry/pdbcat/metadata.xml b/sci-chemistry/pdbcat/metadata.xml
index ad3b3d086c24..9f9da7cbec86 100644
--- a/sci-chemistry/pdbcat/metadata.xml
+++ b/sci-chemistry/pdbcat/metadata.xml
@@ -6,19 +6,19 @@
<name>Gentoo Chemistry Project</name>
</maintainer>
<longdescription>
-The Brookhaven Protein Data Bank stores atomic coordinate information
-for protein structures in a column based format. This is designed to
-be read easily read by FORTRAN programs. Indeed, if you get the
-format description (from anonymous ftp to ftp.pdb.bnl.gov, the file
-/pub/format.desc.ps) they show the single input line needed to read
-each record type.
-However, I am a C/C++ programmer in the Unix environment. It is a
-easier for me to deal with field based input than column based ones.
-If the fields are white space delimited I can easily use awk and perl
-to manipulate the coordinate information. So I needed some way to
-convert the ATOM and HETATM records of PDB files from the standard
-column based format to a field based one and back again. It needed
-to denote missing fields if they exist.
-That converter is `pdbcat'.
-</longdescription>
+ The Brookhaven Protein Data Bank stores atomic coordinate information
+ for protein structures in a column based format. This is designed to
+ be read easily read by FORTRAN programs. Indeed, if you get the
+ format description (from anonymous ftp to ftp.pdb.bnl.gov, the file
+ /pub/format.desc.ps) they show the single input line needed to read
+ each record type.
+ However, I am a C/C++ programmer in the Unix environment. It is a
+ easier for me to deal with field based input than column based ones.
+ If the fields are white space delimited I can easily use awk and perl
+ to manipulate the coordinate information. So I needed some way to
+ convert the ATOM and HETATM records of PDB files from the standard
+ column based format to a field based one and back again. It needed
+ to denote missing fields if they exist.
+ That converter is `pdbcat'.
+ </longdescription>
</pkgmetadata>