Any ideas on how this table could be made better looking?










9















usepackagemultirow
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file HYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & It defines the simulation time in seconds \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the SMS program following the calculations. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & It defines the time interval (in seconds) for which the data of the node strings are written to the Q_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity allowed \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in the viscosity formula \
SCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
hline
endtabular
endtable


enter image description here










share|improve this question
























  • I would put "used value" on two lines.

    – Jay
    Nov 13 '18 at 13:04















9















usepackagemultirow
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file HYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & It defines the simulation time in seconds \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the SMS program following the calculations. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & It defines the time interval (in seconds) for which the data of the node strings are written to the Q_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity allowed \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in the viscosity formula \
SCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
hline
endtabular
endtable


enter image description here










share|improve this question
























  • I would put "used value" on two lines.

    – Jay
    Nov 13 '18 at 13:04













9












9








9


1






usepackagemultirow
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file HYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & It defines the simulation time in seconds \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the SMS program following the calculations. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & It defines the time interval (in seconds) for which the data of the node strings are written to the Q_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity allowed \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in the viscosity formula \
SCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
hline
endtabular
endtable


enter image description here










share|improve this question
















usepackagemultirow
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file HYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & It defines the simulation time in seconds \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the SMS program following the calculations. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & It defines the time interval (in seconds) for which the data of the node strings are written to the Q_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity allowed \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in the viscosity formula \
SCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
hline
endtabular
endtable


enter image description here







tables multirow multicolumn parbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 13:37









pluton

7,965960131




7,965960131










asked Nov 13 '18 at 11:50









BoboloBobolo

755




755












  • I would put "used value" on two lines.

    – Jay
    Nov 13 '18 at 13:04

















  • I would put "used value" on two lines.

    – Jay
    Nov 13 '18 at 13:04
















I would put "used value" on two lines.

– Jay
Nov 13 '18 at 13:04





I would put "used value" on two lines.

– Jay
Nov 13 '18 at 13:04










3 Answers
3






active

oldest

votes


















13














A few points:



  • use booktabs package for better spacing


  • use siunitx package to get the space between values and units right


  • use a tabularx to keep the table within the available textwidth, yours was much wider


  • subdivide the middle rule


  • your parameters seems to be the names of some variables? I'd write them either in typewriter font or in small caps.


  • left align the columns. Justified text in very narrow columns will never look good


  • you mix if the unit is part of the parameter name of used value. I don't know your program, so no idea what is the correct way, but be consistent


  • make the content of the table and the rules aligned by using @



documentclassarticle

usepackagegeometry
usepackagebooktabs
usepackagearray
usepackagemultirow
usepackagetabularx
usepackagesiunitx


newcolumntypeL[1]>centeringraggedrightm#1

begindocument


begintable[htbp]
renewcommandarraystretch1.5
begintabularxlinewidth@L2.5cmL2.5cmL1.5cmX@
toprule
multicolumn2ctextbfParametershspace1em & & \
textbfOriginal & textbfEnglish translation & textbfUsed value & textbfDefinition \

cmidrule(r)1-2 cmidrule(lr)3-3 cmidrule(l)4-4

Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file textttHYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \

Simulationszeit & Simulation time & SI86400s & It defines the simulation time in seconds \

Zeitintervall textttSMS & Time interval textttSMS & SI8640s & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the textttSMS program following the calculations. \

Zeitintervall textttQ_Strg & Time interval textttQ_Strg & SI900s & It defines the time interval (in seconds) for which the data of the node strings are written to the textttQ_Strg.dat. \

Hmin & multirow5* & SI0.01m & Minimum water depth \

textttVELMAX & & SI15m/s & Maximum velocity allowed \

Amin & & SIe-15metersquare & Minimum element size allowed for calculating the internal calculation time step \

textttCMUVISC & & 0.60 & Coefficient cm in the viscosity formula \

textttSCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
bottomrule
endtabularx
endtable

enddocument


enter image description here






share|improve this answer




















  • 3





    Personally I would put also a cmidrule to "Parameters".

    – Fran
    Nov 13 '18 at 13:23












  • Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

    – Bobolo
    Nov 27 '18 at 23:29












  • @Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

    – samcarter
    Nov 28 '18 at 9:29












  • It did not work, that is why I asked. I thought you might know better as this table is created by you.

    – Bobolo
    Nov 28 '18 at 14:41







  • 1





    @Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

    – samcarter
    Nov 28 '18 at 14:50


















5














Here's a solution that's very similar to the one posted by @samcarter. E.g., it uses a tabularx environment, doesn't fully justify the cell contents, and uses the macros num, si, and SI of the siunitx package to display numbers, scientific units, and combinations of numbers and associated units.



Some differences:



  • No line breaks allowed in column 3

  • Automatic hanging indentation of cell contents in columns 1 and 2

  • No bold-facing of header cells

  • Terser language in column 4

  • Use path macro (provided by url package) to typeset file names

  • Use of , (comma) as thousands-separator for numbers with 4 or more digits

enter image description here



documentclassarticle
usepackage[a4paper]geometry % set page parameters suitably
usepackage[hyphens,spaces,obeyspaces]url % for 'path' macro
usepackageragged2e,tabularx,booktabs,siunitx
newcolumntypeL>RaggedRightarraybackslashX
newcolumntypeP[2]>RaggedRighthangafter=1hangindent=1emp#1
begindocument
begintable[htbp]
sisetupper-mode=symbol,
tight-spacing,
group-minimum-digits=4,
group-separator=,
begintabularxtextwidth@ *2P2.2cmlL @
toprule
multicolumn2cParameters & Used value & Definition \
cmidrule(r)1-2
Original & English translation \
midrule
Rechenlauf fortsetzen & Continue calculation & No & Determines whether a calculation run is to be continued. If yes, result data from the file pathHYDRO_AS 2D.CPR is transferred to program and used as initial boundary condition \
Simulations-zeit [sisecond] & Simulation time [sisecond] & num86400 & Simulation time, in seconds \
Zeitintervall SMS [sisecond]& Time interval SMS [sisecond] & num8640 & Time interval (in seconds) for storage of area-based result data which can be visualized with the SMS program following the calculations \
Zeitintervall Q_Strg [sisecond] & Time interval Q_Strg [sisecond] & num900 & Time interval (in seconds) for which the data of the node strings are written to pathQ_Strg.dat \
Hmin & & SI0.01meter & Minimum water depth \
VELMAX & & SI15meterpersecond & Maximum velocity allowed \
Amin & & SIe-15metersquared & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & num0.60 & Coefficient cm in viscosity formula \
SCF & & num1.00 & Coefficient for additional acceleration of calculation process \
bottomrule
endtabularx
endtable
enddocument





share|improve this answer




















  • 1





    Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

    – samcarter
    Nov 13 '18 at 13:51







  • 1





    @samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

    – Mico
    Nov 13 '18 at 13:57



















3














This is a slightly off-topic answer, in that others have covered the TeX aspects better than I could and I concentrate on the writing.



You can tighten up the wording of many of the entries in the last column. The "It" at the start of many entries is definitely superfluous. I'd also drop "determines" or "defines" and the "the". You can lose some other articles as well and generally copy-edit your text into a shorter form. I've had a go for you, see below. I may have overdone it in some cases but I still think the first entry is a little wordy. This saves a line on each of all but one of your multiline items, making the whole lot easier to read. Also you've got full stops on some entries but not others.



I'd also add a little vertical space between rows (the total height can still be less within the copy-editing), to make the last column easier to read . Use raggedright to split lines between words rather than hyphenating I've used raggedright for "Continue Calculation", but not for the teo cells starting "Time interval", to demonstrate the effect. These points are covered in other answers, as is the use of texttt which I've inconsistently demonstrated.



In particular line breaks in variable names and the like should really be avoided



defarraystretch1.5%
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & raggedright Continue calculation & No & Whether calculation run is to be continued. If yes, results from file textttHYDRO_AS 2D.CPR are transferred to the program and used as initial condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & Simulation time (in seconds) \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & Time interval (in seconds) for storage of area-based results which can subsequently be visualized with the SMS program. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & Time interval (in seconds) for which data of the node strings are written to textttQ_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size for calculating internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in viscosity formula \
SCF & & 1.00 & Coefficient for additional acceleration of calculation process \
hline
endtabular
endtable


Output






share|improve this answer




















  • 1





    Can you think of a method for reducing the sizable inter-word gaps in the second column?

    – Mico
    Nov 13 '18 at 15:38







  • 1





    @Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

    – Chris H
    Nov 13 '18 at 15:45










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f459767%2fany-ideas-on-how-this-table-could-be-made-better-looking%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









13














A few points:



  • use booktabs package for better spacing


  • use siunitx package to get the space between values and units right


  • use a tabularx to keep the table within the available textwidth, yours was much wider


  • subdivide the middle rule


  • your parameters seems to be the names of some variables? I'd write them either in typewriter font or in small caps.


  • left align the columns. Justified text in very narrow columns will never look good


  • you mix if the unit is part of the parameter name of used value. I don't know your program, so no idea what is the correct way, but be consistent


  • make the content of the table and the rules aligned by using @



documentclassarticle

usepackagegeometry
usepackagebooktabs
usepackagearray
usepackagemultirow
usepackagetabularx
usepackagesiunitx


newcolumntypeL[1]>centeringraggedrightm#1

begindocument


begintable[htbp]
renewcommandarraystretch1.5
begintabularxlinewidth@L2.5cmL2.5cmL1.5cmX@
toprule
multicolumn2ctextbfParametershspace1em & & \
textbfOriginal & textbfEnglish translation & textbfUsed value & textbfDefinition \

cmidrule(r)1-2 cmidrule(lr)3-3 cmidrule(l)4-4

Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file textttHYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \

Simulationszeit & Simulation time & SI86400s & It defines the simulation time in seconds \

Zeitintervall textttSMS & Time interval textttSMS & SI8640s & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the textttSMS program following the calculations. \

Zeitintervall textttQ_Strg & Time interval textttQ_Strg & SI900s & It defines the time interval (in seconds) for which the data of the node strings are written to the textttQ_Strg.dat. \

Hmin & multirow5* & SI0.01m & Minimum water depth \

textttVELMAX & & SI15m/s & Maximum velocity allowed \

Amin & & SIe-15metersquare & Minimum element size allowed for calculating the internal calculation time step \

textttCMUVISC & & 0.60 & Coefficient cm in the viscosity formula \

textttSCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
bottomrule
endtabularx
endtable

enddocument


enter image description here






share|improve this answer




















  • 3





    Personally I would put also a cmidrule to "Parameters".

    – Fran
    Nov 13 '18 at 13:23












  • Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

    – Bobolo
    Nov 27 '18 at 23:29












  • @Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

    – samcarter
    Nov 28 '18 at 9:29












  • It did not work, that is why I asked. I thought you might know better as this table is created by you.

    – Bobolo
    Nov 28 '18 at 14:41







  • 1





    @Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

    – samcarter
    Nov 28 '18 at 14:50















13














A few points:



  • use booktabs package for better spacing


  • use siunitx package to get the space between values and units right


  • use a tabularx to keep the table within the available textwidth, yours was much wider


  • subdivide the middle rule


  • your parameters seems to be the names of some variables? I'd write them either in typewriter font or in small caps.


  • left align the columns. Justified text in very narrow columns will never look good


  • you mix if the unit is part of the parameter name of used value. I don't know your program, so no idea what is the correct way, but be consistent


  • make the content of the table and the rules aligned by using @



documentclassarticle

usepackagegeometry
usepackagebooktabs
usepackagearray
usepackagemultirow
usepackagetabularx
usepackagesiunitx


newcolumntypeL[1]>centeringraggedrightm#1

begindocument


begintable[htbp]
renewcommandarraystretch1.5
begintabularxlinewidth@L2.5cmL2.5cmL1.5cmX@
toprule
multicolumn2ctextbfParametershspace1em & & \
textbfOriginal & textbfEnglish translation & textbfUsed value & textbfDefinition \

cmidrule(r)1-2 cmidrule(lr)3-3 cmidrule(l)4-4

Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file textttHYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \

Simulationszeit & Simulation time & SI86400s & It defines the simulation time in seconds \

Zeitintervall textttSMS & Time interval textttSMS & SI8640s & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the textttSMS program following the calculations. \

Zeitintervall textttQ_Strg & Time interval textttQ_Strg & SI900s & It defines the time interval (in seconds) for which the data of the node strings are written to the textttQ_Strg.dat. \

Hmin & multirow5* & SI0.01m & Minimum water depth \

textttVELMAX & & SI15m/s & Maximum velocity allowed \

Amin & & SIe-15metersquare & Minimum element size allowed for calculating the internal calculation time step \

textttCMUVISC & & 0.60 & Coefficient cm in the viscosity formula \

textttSCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
bottomrule
endtabularx
endtable

enddocument


enter image description here






share|improve this answer




















  • 3





    Personally I would put also a cmidrule to "Parameters".

    – Fran
    Nov 13 '18 at 13:23












  • Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

    – Bobolo
    Nov 27 '18 at 23:29












  • @Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

    – samcarter
    Nov 28 '18 at 9:29












  • It did not work, that is why I asked. I thought you might know better as this table is created by you.

    – Bobolo
    Nov 28 '18 at 14:41







  • 1





    @Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

    – samcarter
    Nov 28 '18 at 14:50













13












13








13







A few points:



  • use booktabs package for better spacing


  • use siunitx package to get the space between values and units right


  • use a tabularx to keep the table within the available textwidth, yours was much wider


  • subdivide the middle rule


  • your parameters seems to be the names of some variables? I'd write them either in typewriter font or in small caps.


  • left align the columns. Justified text in very narrow columns will never look good


  • you mix if the unit is part of the parameter name of used value. I don't know your program, so no idea what is the correct way, but be consistent


  • make the content of the table and the rules aligned by using @



documentclassarticle

usepackagegeometry
usepackagebooktabs
usepackagearray
usepackagemultirow
usepackagetabularx
usepackagesiunitx


newcolumntypeL[1]>centeringraggedrightm#1

begindocument


begintable[htbp]
renewcommandarraystretch1.5
begintabularxlinewidth@L2.5cmL2.5cmL1.5cmX@
toprule
multicolumn2ctextbfParametershspace1em & & \
textbfOriginal & textbfEnglish translation & textbfUsed value & textbfDefinition \

cmidrule(r)1-2 cmidrule(lr)3-3 cmidrule(l)4-4

Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file textttHYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \

Simulationszeit & Simulation time & SI86400s & It defines the simulation time in seconds \

Zeitintervall textttSMS & Time interval textttSMS & SI8640s & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the textttSMS program following the calculations. \

Zeitintervall textttQ_Strg & Time interval textttQ_Strg & SI900s & It defines the time interval (in seconds) for which the data of the node strings are written to the textttQ_Strg.dat. \

Hmin & multirow5* & SI0.01m & Minimum water depth \

textttVELMAX & & SI15m/s & Maximum velocity allowed \

Amin & & SIe-15metersquare & Minimum element size allowed for calculating the internal calculation time step \

textttCMUVISC & & 0.60 & Coefficient cm in the viscosity formula \

textttSCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
bottomrule
endtabularx
endtable

enddocument


enter image description here






share|improve this answer















A few points:



  • use booktabs package for better spacing


  • use siunitx package to get the space between values and units right


  • use a tabularx to keep the table within the available textwidth, yours was much wider


  • subdivide the middle rule


  • your parameters seems to be the names of some variables? I'd write them either in typewriter font or in small caps.


  • left align the columns. Justified text in very narrow columns will never look good


  • you mix if the unit is part of the parameter name of used value. I don't know your program, so no idea what is the correct way, but be consistent


  • make the content of the table and the rules aligned by using @



documentclassarticle

usepackagegeometry
usepackagebooktabs
usepackagearray
usepackagemultirow
usepackagetabularx
usepackagesiunitx


newcolumntypeL[1]>centeringraggedrightm#1

begindocument


begintable[htbp]
renewcommandarraystretch1.5
begintabularxlinewidth@L2.5cmL2.5cmL1.5cmX@
toprule
multicolumn2ctextbfParametershspace1em & & \
textbfOriginal & textbfEnglish translation & textbfUsed value & textbfDefinition \

cmidrule(r)1-2 cmidrule(lr)3-3 cmidrule(l)4-4

Rechenlauf fortsetzen & Continue calculation & No & It determines whether a calculation run is to be continued. If yes, the result data from the file textttHYDRO_AS 2D.CPR is transferred to the program and used as initial boundary condition. \

Simulationszeit & Simulation time & SI86400s & It defines the simulation time in seconds \

Zeitintervall textttSMS & Time interval textttSMS & SI8640s & It defines the time interval (in seconds) for the storage of area-based result data which can be visualized with the textttSMS program following the calculations. \

Zeitintervall textttQ_Strg & Time interval textttQ_Strg & SI900s & It defines the time interval (in seconds) for which the data of the node strings are written to the textttQ_Strg.dat. \

Hmin & multirow5* & SI0.01m & Minimum water depth \

textttVELMAX & & SI15m/s & Maximum velocity allowed \

Amin & & SIe-15metersquare & Minimum element size allowed for calculating the internal calculation time step \

textttCMUVISC & & 0.60 & Coefficient cm in the viscosity formula \

textttSCF & & 1.00 & Coefficient for the additional acceleration of the calculation process \
bottomrule
endtabularx
endtable

enddocument


enter image description here







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 13 '18 at 13:17

























answered Nov 13 '18 at 13:03









samcartersamcarter

86.9k795279




86.9k795279







  • 3





    Personally I would put also a cmidrule to "Parameters".

    – Fran
    Nov 13 '18 at 13:23












  • Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

    – Bobolo
    Nov 27 '18 at 23:29












  • @Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

    – samcarter
    Nov 28 '18 at 9:29












  • It did not work, that is why I asked. I thought you might know better as this table is created by you.

    – Bobolo
    Nov 28 '18 at 14:41







  • 1





    @Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

    – samcarter
    Nov 28 '18 at 14:50












  • 3





    Personally I would put also a cmidrule to "Parameters".

    – Fran
    Nov 13 '18 at 13:23












  • Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

    – Bobolo
    Nov 27 '18 at 23:29












  • @Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

    – samcarter
    Nov 28 '18 at 9:29












  • It did not work, that is why I asked. I thought you might know better as this table is created by you.

    – Bobolo
    Nov 28 '18 at 14:41







  • 1





    @Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

    – samcarter
    Nov 28 '18 at 14:50







3




3





Personally I would put also a cmidrule to "Parameters".

– Fran
Nov 13 '18 at 13:23






Personally I would put also a cmidrule to "Parameters".

– Fran
Nov 13 '18 at 13:23














Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

– Bobolo
Nov 27 '18 at 23:29






Could longtable be also used for this table? Could it be split in case it's too long using longtable and pagebreak?

– Bobolo
Nov 27 '18 at 23:29














@Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

– samcarter
Nov 28 '18 at 9:29






@Bobolo Sure, just like the answer you got in tex.stackexchange.com/a/461892/36296

– samcarter
Nov 28 '18 at 9:29














It did not work, that is why I asked. I thought you might know better as this table is created by you.

– Bobolo
Nov 28 '18 at 14:41






It did not work, that is why I asked. I thought you might know better as this table is created by you.

– Bobolo
Nov 28 '18 at 14:41





1




1





@Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

– samcarter
Nov 28 '18 at 14:50





@Bobolo If I fix the error about the missing definition of textdegree tex.stackexchange.com/a/461892/36296 works fine. (but I strongly suggest to use siunitx for numbers/units, otherwise the spacing will be wrong)

– samcarter
Nov 28 '18 at 14:50











5














Here's a solution that's very similar to the one posted by @samcarter. E.g., it uses a tabularx environment, doesn't fully justify the cell contents, and uses the macros num, si, and SI of the siunitx package to display numbers, scientific units, and combinations of numbers and associated units.



Some differences:



  • No line breaks allowed in column 3

  • Automatic hanging indentation of cell contents in columns 1 and 2

  • No bold-facing of header cells

  • Terser language in column 4

  • Use path macro (provided by url package) to typeset file names

  • Use of , (comma) as thousands-separator for numbers with 4 or more digits

enter image description here



documentclassarticle
usepackage[a4paper]geometry % set page parameters suitably
usepackage[hyphens,spaces,obeyspaces]url % for 'path' macro
usepackageragged2e,tabularx,booktabs,siunitx
newcolumntypeL>RaggedRightarraybackslashX
newcolumntypeP[2]>RaggedRighthangafter=1hangindent=1emp#1
begindocument
begintable[htbp]
sisetupper-mode=symbol,
tight-spacing,
group-minimum-digits=4,
group-separator=,
begintabularxtextwidth@ *2P2.2cmlL @
toprule
multicolumn2cParameters & Used value & Definition \
cmidrule(r)1-2
Original & English translation \
midrule
Rechenlauf fortsetzen & Continue calculation & No & Determines whether a calculation run is to be continued. If yes, result data from the file pathHYDRO_AS 2D.CPR is transferred to program and used as initial boundary condition \
Simulations-zeit [sisecond] & Simulation time [sisecond] & num86400 & Simulation time, in seconds \
Zeitintervall SMS [sisecond]& Time interval SMS [sisecond] & num8640 & Time interval (in seconds) for storage of area-based result data which can be visualized with the SMS program following the calculations \
Zeitintervall Q_Strg [sisecond] & Time interval Q_Strg [sisecond] & num900 & Time interval (in seconds) for which the data of the node strings are written to pathQ_Strg.dat \
Hmin & & SI0.01meter & Minimum water depth \
VELMAX & & SI15meterpersecond & Maximum velocity allowed \
Amin & & SIe-15metersquared & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & num0.60 & Coefficient cm in viscosity formula \
SCF & & num1.00 & Coefficient for additional acceleration of calculation process \
bottomrule
endtabularx
endtable
enddocument





share|improve this answer




















  • 1





    Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

    – samcarter
    Nov 13 '18 at 13:51







  • 1





    @samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

    – Mico
    Nov 13 '18 at 13:57
















5














Here's a solution that's very similar to the one posted by @samcarter. E.g., it uses a tabularx environment, doesn't fully justify the cell contents, and uses the macros num, si, and SI of the siunitx package to display numbers, scientific units, and combinations of numbers and associated units.



Some differences:



  • No line breaks allowed in column 3

  • Automatic hanging indentation of cell contents in columns 1 and 2

  • No bold-facing of header cells

  • Terser language in column 4

  • Use path macro (provided by url package) to typeset file names

  • Use of , (comma) as thousands-separator for numbers with 4 or more digits

enter image description here



documentclassarticle
usepackage[a4paper]geometry % set page parameters suitably
usepackage[hyphens,spaces,obeyspaces]url % for 'path' macro
usepackageragged2e,tabularx,booktabs,siunitx
newcolumntypeL>RaggedRightarraybackslashX
newcolumntypeP[2]>RaggedRighthangafter=1hangindent=1emp#1
begindocument
begintable[htbp]
sisetupper-mode=symbol,
tight-spacing,
group-minimum-digits=4,
group-separator=,
begintabularxtextwidth@ *2P2.2cmlL @
toprule
multicolumn2cParameters & Used value & Definition \
cmidrule(r)1-2
Original & English translation \
midrule
Rechenlauf fortsetzen & Continue calculation & No & Determines whether a calculation run is to be continued. If yes, result data from the file pathHYDRO_AS 2D.CPR is transferred to program and used as initial boundary condition \
Simulations-zeit [sisecond] & Simulation time [sisecond] & num86400 & Simulation time, in seconds \
Zeitintervall SMS [sisecond]& Time interval SMS [sisecond] & num8640 & Time interval (in seconds) for storage of area-based result data which can be visualized with the SMS program following the calculations \
Zeitintervall Q_Strg [sisecond] & Time interval Q_Strg [sisecond] & num900 & Time interval (in seconds) for which the data of the node strings are written to pathQ_Strg.dat \
Hmin & & SI0.01meter & Minimum water depth \
VELMAX & & SI15meterpersecond & Maximum velocity allowed \
Amin & & SIe-15metersquared & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & num0.60 & Coefficient cm in viscosity formula \
SCF & & num1.00 & Coefficient for additional acceleration of calculation process \
bottomrule
endtabularx
endtable
enddocument





share|improve this answer




















  • 1





    Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

    – samcarter
    Nov 13 '18 at 13:51







  • 1





    @samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

    – Mico
    Nov 13 '18 at 13:57














5












5








5







Here's a solution that's very similar to the one posted by @samcarter. E.g., it uses a tabularx environment, doesn't fully justify the cell contents, and uses the macros num, si, and SI of the siunitx package to display numbers, scientific units, and combinations of numbers and associated units.



Some differences:



  • No line breaks allowed in column 3

  • Automatic hanging indentation of cell contents in columns 1 and 2

  • No bold-facing of header cells

  • Terser language in column 4

  • Use path macro (provided by url package) to typeset file names

  • Use of , (comma) as thousands-separator for numbers with 4 or more digits

enter image description here



documentclassarticle
usepackage[a4paper]geometry % set page parameters suitably
usepackage[hyphens,spaces,obeyspaces]url % for 'path' macro
usepackageragged2e,tabularx,booktabs,siunitx
newcolumntypeL>RaggedRightarraybackslashX
newcolumntypeP[2]>RaggedRighthangafter=1hangindent=1emp#1
begindocument
begintable[htbp]
sisetupper-mode=symbol,
tight-spacing,
group-minimum-digits=4,
group-separator=,
begintabularxtextwidth@ *2P2.2cmlL @
toprule
multicolumn2cParameters & Used value & Definition \
cmidrule(r)1-2
Original & English translation \
midrule
Rechenlauf fortsetzen & Continue calculation & No & Determines whether a calculation run is to be continued. If yes, result data from the file pathHYDRO_AS 2D.CPR is transferred to program and used as initial boundary condition \
Simulations-zeit [sisecond] & Simulation time [sisecond] & num86400 & Simulation time, in seconds \
Zeitintervall SMS [sisecond]& Time interval SMS [sisecond] & num8640 & Time interval (in seconds) for storage of area-based result data which can be visualized with the SMS program following the calculations \
Zeitintervall Q_Strg [sisecond] & Time interval Q_Strg [sisecond] & num900 & Time interval (in seconds) for which the data of the node strings are written to pathQ_Strg.dat \
Hmin & & SI0.01meter & Minimum water depth \
VELMAX & & SI15meterpersecond & Maximum velocity allowed \
Amin & & SIe-15metersquared & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & num0.60 & Coefficient cm in viscosity formula \
SCF & & num1.00 & Coefficient for additional acceleration of calculation process \
bottomrule
endtabularx
endtable
enddocument





share|improve this answer















Here's a solution that's very similar to the one posted by @samcarter. E.g., it uses a tabularx environment, doesn't fully justify the cell contents, and uses the macros num, si, and SI of the siunitx package to display numbers, scientific units, and combinations of numbers and associated units.



Some differences:



  • No line breaks allowed in column 3

  • Automatic hanging indentation of cell contents in columns 1 and 2

  • No bold-facing of header cells

  • Terser language in column 4

  • Use path macro (provided by url package) to typeset file names

  • Use of , (comma) as thousands-separator for numbers with 4 or more digits

enter image description here



documentclassarticle
usepackage[a4paper]geometry % set page parameters suitably
usepackage[hyphens,spaces,obeyspaces]url % for 'path' macro
usepackageragged2e,tabularx,booktabs,siunitx
newcolumntypeL>RaggedRightarraybackslashX
newcolumntypeP[2]>RaggedRighthangafter=1hangindent=1emp#1
begindocument
begintable[htbp]
sisetupper-mode=symbol,
tight-spacing,
group-minimum-digits=4,
group-separator=,
begintabularxtextwidth@ *2P2.2cmlL @
toprule
multicolumn2cParameters & Used value & Definition \
cmidrule(r)1-2
Original & English translation \
midrule
Rechenlauf fortsetzen & Continue calculation & No & Determines whether a calculation run is to be continued. If yes, result data from the file pathHYDRO_AS 2D.CPR is transferred to program and used as initial boundary condition \
Simulations-zeit [sisecond] & Simulation time [sisecond] & num86400 & Simulation time, in seconds \
Zeitintervall SMS [sisecond]& Time interval SMS [sisecond] & num8640 & Time interval (in seconds) for storage of area-based result data which can be visualized with the SMS program following the calculations \
Zeitintervall Q_Strg [sisecond] & Time interval Q_Strg [sisecond] & num900 & Time interval (in seconds) for which the data of the node strings are written to pathQ_Strg.dat \
Hmin & & SI0.01meter & Minimum water depth \
VELMAX & & SI15meterpersecond & Maximum velocity allowed \
Amin & & SIe-15metersquared & Minimum element size allowed for calculating the internal calculation time step \
CMUVISC & & num0.60 & Coefficient cm in viscosity formula \
SCF & & num1.00 & Coefficient for additional acceleration of calculation process \
bottomrule
endtabularx
endtable
enddocument






share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 13 '18 at 14:00

























answered Nov 13 '18 at 13:48









MicoMico

275k30372760




275k30372760







  • 1





    Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

    – samcarter
    Nov 13 '18 at 13:51







  • 1





    @samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

    – Mico
    Nov 13 '18 at 13:57













  • 1





    Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

    – samcarter
    Nov 13 '18 at 13:51







  • 1





    @samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

    – Mico
    Nov 13 '18 at 13:57








1




1





Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

– samcarter
Nov 13 '18 at 13:51






Nice answer! The indention looks nice. Tiny problem: path does not preserve the space within the file name (ok, file names should not have spaces, but ...)

– samcarter
Nov 13 '18 at 13:51





1




1





@samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

– Mico
Nov 13 '18 at 13:57






@samcarter - Good catch about the space inside the file name! This issue can be remedied easily by adding the option obeyspaces when loading the url package. I'll update the answer accordingly.

– Mico
Nov 13 '18 at 13:57












3














This is a slightly off-topic answer, in that others have covered the TeX aspects better than I could and I concentrate on the writing.



You can tighten up the wording of many of the entries in the last column. The "It" at the start of many entries is definitely superfluous. I'd also drop "determines" or "defines" and the "the". You can lose some other articles as well and generally copy-edit your text into a shorter form. I've had a go for you, see below. I may have overdone it in some cases but I still think the first entry is a little wordy. This saves a line on each of all but one of your multiline items, making the whole lot easier to read. Also you've got full stops on some entries but not others.



I'd also add a little vertical space between rows (the total height can still be less within the copy-editing), to make the last column easier to read . Use raggedright to split lines between words rather than hyphenating I've used raggedright for "Continue Calculation", but not for the teo cells starting "Time interval", to demonstrate the effect. These points are covered in other answers, as is the use of texttt which I've inconsistently demonstrated.



In particular line breaks in variable names and the like should really be avoided



defarraystretch1.5%
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & raggedright Continue calculation & No & Whether calculation run is to be continued. If yes, results from file textttHYDRO_AS 2D.CPR are transferred to the program and used as initial condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & Simulation time (in seconds) \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & Time interval (in seconds) for storage of area-based results which can subsequently be visualized with the SMS program. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & Time interval (in seconds) for which data of the node strings are written to textttQ_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size for calculating internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in viscosity formula \
SCF & & 1.00 & Coefficient for additional acceleration of calculation process \
hline
endtabular
endtable


Output






share|improve this answer




















  • 1





    Can you think of a method for reducing the sizable inter-word gaps in the second column?

    – Mico
    Nov 13 '18 at 15:38







  • 1





    @Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

    – Chris H
    Nov 13 '18 at 15:45















3














This is a slightly off-topic answer, in that others have covered the TeX aspects better than I could and I concentrate on the writing.



You can tighten up the wording of many of the entries in the last column. The "It" at the start of many entries is definitely superfluous. I'd also drop "determines" or "defines" and the "the". You can lose some other articles as well and generally copy-edit your text into a shorter form. I've had a go for you, see below. I may have overdone it in some cases but I still think the first entry is a little wordy. This saves a line on each of all but one of your multiline items, making the whole lot easier to read. Also you've got full stops on some entries but not others.



I'd also add a little vertical space between rows (the total height can still be less within the copy-editing), to make the last column easier to read . Use raggedright to split lines between words rather than hyphenating I've used raggedright for "Continue Calculation", but not for the teo cells starting "Time interval", to demonstrate the effect. These points are covered in other answers, as is the use of texttt which I've inconsistently demonstrated.



In particular line breaks in variable names and the like should really be avoided



defarraystretch1.5%
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & raggedright Continue calculation & No & Whether calculation run is to be continued. If yes, results from file textttHYDRO_AS 2D.CPR are transferred to the program and used as initial condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & Simulation time (in seconds) \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & Time interval (in seconds) for storage of area-based results which can subsequently be visualized with the SMS program. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & Time interval (in seconds) for which data of the node strings are written to textttQ_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size for calculating internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in viscosity formula \
SCF & & 1.00 & Coefficient for additional acceleration of calculation process \
hline
endtabular
endtable


Output






share|improve this answer




















  • 1





    Can you think of a method for reducing the sizable inter-word gaps in the second column?

    – Mico
    Nov 13 '18 at 15:38







  • 1





    @Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

    – Chris H
    Nov 13 '18 at 15:45













3












3








3







This is a slightly off-topic answer, in that others have covered the TeX aspects better than I could and I concentrate on the writing.



You can tighten up the wording of many of the entries in the last column. The "It" at the start of many entries is definitely superfluous. I'd also drop "determines" or "defines" and the "the". You can lose some other articles as well and generally copy-edit your text into a shorter form. I've had a go for you, see below. I may have overdone it in some cases but I still think the first entry is a little wordy. This saves a line on each of all but one of your multiline items, making the whole lot easier to read. Also you've got full stops on some entries but not others.



I'd also add a little vertical space between rows (the total height can still be less within the copy-editing), to make the last column easier to read . Use raggedright to split lines between words rather than hyphenating I've used raggedright for "Continue Calculation", but not for the teo cells starting "Time interval", to demonstrate the effect. These points are covered in other answers, as is the use of texttt which I've inconsistently demonstrated.



In particular line breaks in variable names and the like should really be avoided



defarraystretch1.5%
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & raggedright Continue calculation & No & Whether calculation run is to be continued. If yes, results from file textttHYDRO_AS 2D.CPR are transferred to the program and used as initial condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & Simulation time (in seconds) \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & Time interval (in seconds) for storage of area-based results which can subsequently be visualized with the SMS program. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & Time interval (in seconds) for which data of the node strings are written to textttQ_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size for calculating internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in viscosity formula \
SCF & & 1.00 & Coefficient for additional acceleration of calculation process \
hline
endtabular
endtable


Output






share|improve this answer















This is a slightly off-topic answer, in that others have covered the TeX aspects better than I could and I concentrate on the writing.



You can tighten up the wording of many of the entries in the last column. The "It" at the start of many entries is definitely superfluous. I'd also drop "determines" or "defines" and the "the". You can lose some other articles as well and generally copy-edit your text into a shorter form. I've had a go for you, see below. I may have overdone it in some cases but I still think the first entry is a little wordy. This saves a line on each of all but one of your multiline items, making the whole lot easier to read. Also you've got full stops on some entries but not others.



I'd also add a little vertical space between rows (the total height can still be less within the copy-editing), to make the last column easier to read . Use raggedright to split lines between words rather than hyphenating I've used raggedright for "Continue Calculation", but not for the teo cells starting "Time interval", to demonstrate the effect. These points are covered in other answers, as is the use of texttt which I've inconsistently demonstrated.



In particular line breaks in variable names and the like should really be avoided



defarraystretch1.5%
begintable[htbp]
begintabularp2.5cmp2.5cmp1.5cmp6.5cm
hline
multicolumn2ctextbfParameters & multirow2*textbfUsed value & multicolumn1cmultirow2*textbfDefinition \
textbfOriginal & textbfEnglish translation & & multicolumn1c \
hline
Rechenlauf fortsetzen & raggedright Continue calculation & No & Whether calculation run is to be continued. If yes, results from file textttHYDRO_AS 2D.CPR are transferred to the program and used as initial condition. \
Simulationszeit [s] & Simulation time [s] & 86400 & Simulation time (in seconds) \
Zeitintervall SMS [s] & Time interval SMS [s] & 8640 & Time interval (in seconds) for storage of area-based results which can subsequently be visualized with the SMS program. \
Zeitintervall Q_Strg [s] & Time interval Q_Strg [s] & 900 & Time interval (in seconds) for which data of the node strings are written to textttQ_Strg.dat. \
Hmin & multirow5* & 0.01 m & Minimum water depth \
VELMAX & & 15 m/s & Maximum velocity \
Amin & & 1.e-15 mtextsuperscript2 & Minimum element size for calculating internal calculation time step \
CMUVISC & & 0.60 & Coefficient cm in viscosity formula \
SCF & & 1.00 & Coefficient for additional acceleration of calculation process \
hline
endtabular
endtable


Output







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 13 '18 at 15:46

























answered Nov 13 '18 at 15:10









Chris HChris H

6,31622051




6,31622051







  • 1





    Can you think of a method for reducing the sizable inter-word gaps in the second column?

    – Mico
    Nov 13 '18 at 15:38







  • 1





    @Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

    – Chris H
    Nov 13 '18 at 15:45












  • 1





    Can you think of a method for reducing the sizable inter-word gaps in the second column?

    – Mico
    Nov 13 '18 at 15:38







  • 1





    @Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

    – Chris H
    Nov 13 '18 at 15:45







1




1





Can you think of a method for reducing the sizable inter-word gaps in the second column?

– Mico
Nov 13 '18 at 15:38






Can you think of a method for reducing the sizable inter-word gaps in the second column?

– Mico
Nov 13 '18 at 15:38





1




1





@Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

– Chris H
Nov 13 '18 at 15:45





@Mico more raggedrights will do it -- I'll expand the answer. I prefer to use it locally so I can apply my own judgement as to which cells need it (rather than figuring out a way of making a column ragged -- another question)

– Chris H
Nov 13 '18 at 15:45

















draft saved

draft discarded
















































Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f459767%2fany-ideas-on-how-this-table-could-be-made-better-looking%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Top Tejano songwriter Luis Silva dead of heart attack at 64

ReactJS Fetched API data displays live - need Data displayed static

Evgeni Malkin