<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I would say that both Grev Corbett and
Dan Everett are right:<br>
<br>
Dan is right that similar categories across languages are often
not "the same". The Tagalog ang-Nominal is similar to a Subject in
English, but it's not the same, and the German Future tense is
similar to the French Future tense, but they are not "the same".<br>
<br>
Grev is right that different terms can obscure the similarities,
and since we want to understand the similarities, we should see
beyond the accidents of local traditions.<br>
<br>
Dan has in mind the level of descriptive categories (which are
different across languages), and Grev has the in mind level of
comparative concepts (which are a prerequisite for
cross-linguistic generalizations).<br>
<br>
An interesting question is whether comparative concepts can/should
be "standardized" (perhaps so), and whether one should urge
grammar writers to use these standard comparative terms for the
language-specific counterparts. I'm less sure about the latter,
because I wouldn't want to send the message that there are only as
many possible categories as typologists have set up comparative
concepts.<br>
<br>
Regards,<br>
Martin<br>
<br>
P.S. And of course Bernhard Hurch is right as well: In a diverse
world, different styles should be acceptable. But to be honest,
globalized science is not a diverse world – it's supposed to be
ruthlessly efficient, like globalized business. (In this way, and
quite ironically, globalized language typology is part of the kind
of process that is drastically reducing linguistic diversity.)<br>
<br>
On 06.07.15 08:29, Everett, Daniel wrote:<br>
</div>
<blockquote
cite="mid:80A28093-C5E9-45AF-BEF0-682E2290B132@bentley.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Wrt the larger issue, Grev, about things being "the same" I
am not so sanguine. Many people think there is a passive
construction that is universal but I think that is mistaken. I
am more concerned about over homogenization of
typological/descriptive terms than LaTeX. But I am sure you are
too. The problem is when people begin thinking that there are
"same contructions" - this can become self-fulfilling. Not
always perhaps. </div>
<div><br>
</div>
<div>Dan<br>
<br>
Sent from my iPhone</div>
<div><br>
On Jul 6, 2015, at 09:23, "<a moz-do-not-send="true"
href="mailto:g.corbett@surrey.ac.uk">g.corbett@surrey.ac.uk</a>"
<<a moz-do-not-send="true"
href="mailto:g.corbett@surrey.ac.uk">g.corbett@surrey.ac.uk</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>I guess there is a small answer and a larger answer.
<div class=""><br class="">
<div class="">small: changing commas to full stops for
journal A, and then back to commas for journal B isn’t a
great use of people’s time. Better we diversify our
thinking rather than our reference formatting. Share the
tools but diversify the products.</div>
<div class=""><br class="">
</div>
<div class="">larger: we don’t always realise which things
are the same and which are different, and that’s a waste
too. For instance, there are Africanists who believe that
‘pluractionals' are special to the languages of Africa.
But they are what others call ‘verbal number’ and you can
find that all over.</div>
<div class=""><br class="">
</div>
<div class="">And then there’s the worst case scenario:</div>
<div class=""><a moz-do-not-send="true"
href="http://www.cse.lehigh.edu/%7Egtan/bug/localCopies/marsOrbiter"
class="">http://www.cse.lehigh.edu/~gtan/bug/localCopies/marsOrbiter</a></div>
<div class=""><br class="">
</div>
<div class="">Very best, Grev</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 6 Jul 2015, at 13:30, Hurch, Bernhard
(<a moz-do-not-send="true"
href="mailto:bernhard.hurch@uni-graz.at" class="">bernhard.hurch@uni-graz.at</a>)
<<a moz-do-not-send="true"
href="mailto:bernhard.hurch@uni-graz.at" class="">bernhard.hurch@uni-graz.at</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div class="">Can anybody tell me why everything
must be standardized, unified, vereinheitlicht?</div>
<div class=""><br class="">
</div>
<div class="">Can’t people live with
diversification / in a diversified world? </div>
<div class=""><br class="">
</div>
<div class="">Aren’t different styles the
(necessary) result of different traditions,
different discourse types and different views of
the world?</div>
<div class=""><br class="">
</div>
<div class="">I seem not to know what modern
typology is about. Traditional typology
presumably wasn’t like that. </div>
<div class=""><br class="">
</div>
<div class="">Best wishes,</div>
<div class=""><br class="">
</div>
<div class="">Bernhard</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<br class="">
<div class="">
<div class="">Am 06.07.2015 um 12:38 schrieb
Martin Haspelmath <<a
moz-do-not-send="true"
href="mailto:haspelmath@eva.mpg.de" class="">haspelmath@eva.mpg.de</a>>:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<div class="moz-cite-prefix">On 04.07.15
08:37, Kilu von Prince wrote:<br class="">
</div>
<blockquote
cite="mid:CAK3VzUnZ_vKfhcqP4UZASwjGyH8-oJeQw-TO1dRt56rrzVP6zA@mail.gmail.com"
type="cite" class="">
<div dir="ltr" class="">Dear all,
<div class=""><br class="">
</div>
<div class="">I agree that acceptance of
articles in LaTeX format should be
more widespread than it is at the
moment. I may add that the style
guides of many linguistics journals
could be significantly improved if
they incorporated more of the
established best-practices in
typesetting that are automatically
implemented by default LaTeX styles.</div>
</div>
</blockquote>
<br class="">
Moreover, it would be better if linguistics
journals agreed on a single style guide, see
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.frank-m-richter.de/freescienceblog/2015/03/18/how-to-make-linguistics-publication-more-efficient-use-discipline-wide-style-rules/">http://www.frank-m-richter.de/freescienceblog/2015/03/18/how-to-make-linguistics-publication-more-efficient-use-discipline-wide-style-rules/</a><br
class="">
<br class="">
These issues should ideally be discussed by
a committee of linguistics editors, such as
the LSA's CeLxJ (<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://celxj.org/">http://celxj.org/</a>).<br
class="">
<br class="">
There will be a meeting of European
linguistics editors just before the next SLE
meeting in Leiden (see
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://sle2015.eu/programme">http://sle2015.eu/programme</a>,
"pre-conference mini-workshop"), which will
primarily discuss other issues, but where we
may decide to found such a committee of the
SLE.<br class="">
<br class="">
Regards,<br class="">
Martin<br class="">
<br class="">
<blockquote
cite="mid:CAK3VzUnZ_vKfhcqP4UZASwjGyH8-oJeQw-TO1dRt56rrzVP6zA@mail.gmail.com"
type="cite" class="">
<div dir="ltr" class="">
<div class=""><br class="">
</div>
<div class="">Also, to share a related
anecdote, it is sometimes in fact the
editors rather than the publisher who
insist on a submission in .doc format.
I once submitted an articles to a
Benjamins journal. When the editors
requested a .doc version, I asked them
to speak with their publisher if they
couldn't work with a LaTeX or PDF
file. Then I learned that it was the
editors themselves who needed the .doc
file for their workflow during the
revisions process. I'd like to appeal
to editors to have mercy on their
LaTeX-using authors and try to develop
a workflow that is compatible with
PDFs. Converting LaTeX to .doc is
time-consuming and depressing.</div>
<div class=""><br class="">
</div>
<div class="">Kind regards,</div>
<div class="">Kilu</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Sat, Jul 4,
2015 at 1:35 PM, Guillaume Jacques <span
dir="ltr" class="">
<<a moz-do-not-send="true"
href="mailto:rgyalrongskad@gmail.com"
target="_blank" class="">rgyalrongskad@gmail.com</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr" class="">Dear Don,
<div class=""><br class="">
</div>
<div class="">It is obvious to
anyone who has learned LaTeX
that word-processors like "word"
or "open office" are completely
inadapted to the typesetting of
linguistics dissertations or
articles. LaTeX is superior in
particular for handling aligned
glossed examples (package gb4e),
complex figures (tikz),
Stammbäume, cross-references,
bibliography, complex scripts
and of course math formulas. I
actually now require from all my
new MA and PhD students to write
their dissertations in LaTeX (in
general, three days are enough
to master the most important
commands).</div>
<div class=""><br class="">
</div>
<div class="">Fortunately, the
number of linguistics journal
and of publishers accepting
LaTeX is now growing year after
year. At the present moment,
most if not all linguistics
journals published by the
following major publishers
accept LaTeX submissions (only
those I have personnally tested;
the list is not exhaustive):<br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">Mouton de Gruyter</div>
<div class="">Benjamins</div>
<div class="">Brill</div>
<div class="">Elsevier</div>
<div class="">MIT Press</div>
<div class=""><br class="">
</div>
<div class="">I rarely have to
convert my articles into word
format anymore.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Publishers that are
still lagging behind with LaTeX
include (we should collectively
give them some pressure to catch
up with the rest of the world):</div>
<div class="">Cambridge University
Press (for instance, Journal of
the IPA)</div>
<div class="">Chicago University
Press (IJAL)</div>
<div class="">(perhaps also Wiley)</div>
<div class=""><br class="">
</div>
<div class="">Some journasl do not
use LaTeX files, but will
convert them for you (from my
personal experience,
Anthropological Linguistics and
Journal of Chinese Linguistics)</div>
<div class=""><br class="">
</div>
<div class="">If you submit to a
collective volume for Mouton de
Gruyter or Benjamins, they
should be able to handle a LaTeX
submission even if most of the
volume is in word, but the
editors of the volume may have
to insist a little bit.</div>
<div class=""><br class="">
</div>
<div class="">Best wishes,</div>
<div class=""><br class="">
</div>
<div class="">Guillaume</div>
<div class="gmail_extra">
<div class="">
<div class="h5"><br class="">
<div class="gmail_quote">2015-07-04
11:22 GMT+02:00 Don
Killian <span dir="ltr"
class="">
<<a
moz-do-not-send="true"
href="mailto:donald.killian@helsinki.fi" target="_blank" class="">donald.killian@helsinki.fi</a>></span>:<br
class="">
<blockquote
class="gmail_quote"
style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Dear all,<br class="">
<br class="">
After fighting with
Microsoft Word for the
past few weeks, I was
wondering if there is
any way we can find
additional standards for
article and chapter
submission?<br class="">
<br class="">
It seems that a majority
of editors still have a
fairly strict
requirement of Microsoft
Word and Times New
Roman, even if the
publisher itself is more
open to other formats.
Times New Roman is more
flexible, but I have not
had very much luck with
alternatives to Word
(such as Open Office or
pdfs made from LaTeX).<br
class="">
<br class="">
This is a problem for
more than one reason.
The biggest problem I
can see (in addition to
the fact that both Word
as well as Times New
Roman are proprietary!)
is that the
technological
requirements do not
actually support the
formatting requirements
we suggest. Neither Word
nor Times New Roman
support the IPA in its
entirety.<br class="">
<br class="">
While these problems do
not affect all linguists
(such as those who do
not have certain sounds
in their languages they
work on), it definitely
affects plenty of
others.<br class="">
<br class="">
For instance, there is
no way to change glyph
selection in Word, and
<a> changes to
<ɑ> when
italicized. It is
relatively common to
italicize words when you
mix languages in text.
But if you are
discussing a language
which has both a and ɑ,
this is problematic.
Furthermore, Word has no
way of rendering the MH
or HM tonal contours
properly, in any font.
Those symbols are only
supported in Charis SIL
and Doulos SIL fonts,
and Word renders them
incorrectly.<br class="">
<br class="">
There are plenty of
other difficulties (e.g.
making a vowel chart),
so these are just some
examples.<br class="">
<br class="">
I realize the main
reason for using
Word/TNR is simplicity
and what people are used
to, but I do find it
problematic that our
technology requirements
do not support or make
it easy to deal with
common problems in our
field.<br class="">
<br class="">
Is there any way to
change this? LaTeX does
support almost
everything I have ever
needed, but I admit it
is not always very easy
to learn or use. I would
be happy to hear
alternative views or
suggestions.<br class="">
<br class="">
Best,<br class="">
<br class="">
Don<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">
Lingtyp mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Lingtyp@listserv.linguistlist.org"
class="">Lingtyp@listserv.linguistlist.org</a><br
class="">
<a moz-do-not-send="true"
href="http://listserv.linguistlist.org/mailman/listinfo/lingtyp"
class="">http://listserv.linguistlist.org/mailman/listinfo/lingtyp</a><br
class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br
class="">
Lingtyp mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Lingtyp@listserv.linguistlist.org"
class="">Lingtyp@listserv.linguistlist.org</a><br
class="">
<a moz-do-not-send="true"
href="http://listserv.linguistlist.org/mailman/listinfo/lingtyp">http://listserv.linguistlist.org/mailman/listinfo/lingtyp</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Lingtyp mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:Lingtyp@listserv.linguistlist.org">Lingtyp@listserv.linguistlist.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://listserv.linguistlist.org/mailman/listinfo/lingtyp">http://listserv.linguistlist.org/mailman/listinfo/lingtyp</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Lingtyp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lingtyp@listserv.linguistlist.org">Lingtyp@listserv.linguistlist.org</a>
<a class="moz-txt-link-freetext" href="http://listserv.linguistlist.org/mailman/listinfo/lingtyp">http://listserv.linguistlist.org/mailman/listinfo/lingtyp</a>
</pre>
</blockquote>
<br>
</body>
</html>