Neither is correct in a mathematics context. Use \bar.
On 05/10/2017 05:54 PM, Jeong Dal wrote:
> Dear all,
>
> In the following sample, the outputs of \overline and of \overbar are
> slightly different.
> I used \overline in LaTeX.
> But it takes more vertical space that cause the alignment trouble while
> using \overbar has no problem at all.
> Is it normal behavior?
>
> Thank you.
>
> Best regards,
>
> Dalyoung
>
> %%%%%%%%
> \starttext
> \startitemize[n]
> \item Which is true?
>
> \startitemize[n, packed, columns, two][stopper=,left=(, right=)]
> \item $\overline{A} = A \cup A^\circ$
> \item $\overline{A\cup B} = \overline{A} \cup \overline{B}$
> \item If $A \subset B$ then $\overline{B} \subset \overline{A}$
> \item $A\cup A'$ is an open set.
> \stopitemize
>
> \item Which is true?
>
> \startitemize[n, packed, columns, two][stopper=,left=(, right=)]
> \item $\overbar{A} = A \cup A^\circ$
> \item If $A \subset B$ then $\overbar{B} \subset \overbar{A}$
> \item $\overbar{A\cup B} = \overbar{A} \cup \overbar{B}$
> \item $A\cup A'$ is an open set.
> \stopitemize
>
> \stopitemize
>
> \stoptext
>
>
>> 2017. 5. 9. 오후 7:00, ntg-context-requ...@ntg.nl 작성:
>>
>> Send ntg-context mailing list submissions to
>> ntg-context@ntg.nl
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mailman.ntg.nl/mailman/listinfo/ntg-context
>> or, via email, send a message with subject or body 'help' to
>> ntg-context-requ...@ntg.nl
>>
>> You can reach the person managing the list at
>> ntg-context-ow...@ntg.nl
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ntg-context digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: BUG: % is comment in btx fields (Henri Menke)
>> 2. Re: BUG: % is comment in btx fields (Rik Kabel)
>> 3. Re: BUG: % is comment in btx fields (Ulrike Fischer)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 09 May 2017 13:40:55 +1200
>> From: Henri Menke <henrime...@gmail.com>
>> To: ntg-context@ntg.nl
>> Subject: Re: [NTG-context] BUG: % is comment in btx fields
>> Message-ID: <1494294055.19890.36.ca...@gmail.com>
>> Content-Type: text/plain; charset="UTF-8"
>>
>> On Mon, 2017-05-08 at 20:15 -0400, Rik Kabel wrote:
>>> On 2017-05-08 17:44, Henri Menke wrote:
>>>> Dear list,
>>>>
>>>> The percent character in btx field is taken as a comment characters
>>>> which leads to the rest of the field being discarded. In the MWE
>>>> below, the URL is cut off at the % sign and everything after it is
>>>> lost.
>>>>
>>>> Cheers, Henri
>>>>
>>>>
>>>> ---
>>>>
>>>>
>>>> \startbuffer[references]
>>>> @misc{kraft,
>>>> author = "Kraft, Nathan",
>>>> title = "Mr Kraft's Virtual Filing Cabinet",
>>>> year = "2015",
>>>> url = "http://mrkraft.wikispaces.com/Mr+Kraft%27s+Virtual+Filing+
>>>> Cabi
>>>> net"
>>>> }
>>>> \stopbuffer
>>>>
>>>> \usebtxdataset[references.buffer]
>>>> \usebtxdefinitions[apa]
>>>>
>>>> \starttext
>>>>
>>>> \nocite[kraft]
>>>> \placelistofpublications
>>>>
>>>> \stoptext
>>> The bibtex entry in this example is provided in a buffer. The buffer
>>> mechanism does not handle characters any differently than other text
>>> in the file, and % in a ConTeXt buffer has to be escaped if it does
>>> not signify a comment.
>>
>> That is simply not true! Content inside ConTeXt buffers is as verbatim
>> as reading an external file. Try \typebuffer instead of \getbuffer
>> your example below and observe that the comment sign is perfectly
>> preserved.
>>
>>> If you specify an external (.bib or .bibtex) file to supply the
>>> data, % does not need to be escaped. So, this part is simple user
>>> error.
>>> (With
>>> \starttext
>>> \startbuffer
>>> abc%def
>>>
>>> ghi\%jkl
>>> \stopbuffer
>>> \getbuffer
>>> \stoptext
>>> you do not get %def in the output. Why do you expect different
>>> behavior if the buffer holds a bibtex entry?)
>>>
>>> The way hyphenatedurl handles things may well be worthy of
>>> improvement.
>>>
>>> --
>>> Rik
>>> _____________________________________________________________________
>>> ______________
>>> If your question is of interest to others as well, please add an
>>> entry to the Wiki!
>>>
>>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/nt
>>> g-context
>>> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
>>> archive : https://bitbucket.org/phg/context-mirror/commits/
>>> wiki : http://contextgarden.net
>>> _____________________________________________________________________
>>> ______________
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 8 May 2017 21:48:58 -0400
>> From: Rik Kabel <cont...@rik.users.panix.com>
>> To: ntg-context@ntg.nl
>> Subject: Re: [NTG-context] BUG: % is comment in btx fields
>> Message-ID: <7afe4404-fd96-e7b6-7188-deb8d778e...@rik.users.panix.com>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> On 2017-05-08 21:40, Henri Menke wrote:
>>>
>>> That is simply not true! Content inside ConTeXt buffers is as verbatim
>>> as reading an external file. Try \typebuffer instead of \getbuffer
>>> your example below and observe that the comment sign is perfectly
>>> preserved.
>>>
>> I am sorry. You are, of course, correct, and I use both, so should know
>> better.
>>
>>
>> --
>> Rik
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Tue, 9 May 2017 11:19:46 +0200
>> From: Ulrike Fischer <ne...@nililand.de>
>> To: ntg-context@ntg.nl
>> Subject: Re: [NTG-context] BUG: % is comment in btx fields
>> Message-ID: <19so48cp6cn6u....@nililand.de>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Am Mon, 8 May 2017 17:56:08 -0600 schrieb Alan Braslau:
>>
>>> So bibtex has a funny way of dealing with comments, and do we really
>>> care about Scribe?
>>
>> biber handles comments differently than bibtex, see e.g.
>> https://tex.stackexchange.com/questions/261261/are-comments-discouraged-in-a-bibtex-file
>>
>> As a thumbrule one can sum the rule up that *inside* field text
>> comment chars should be input according the tex rule for the field
>> *type*. That means that normal textfields should use \%, while url's
>> and other verbatim-like field can use %.
>>
>>
>>
>>> We made the choice NOT to remain *strictly* bibtex
>>> compatible, after all bibtex is limited to ASCII 7-bit!
>>
>> That's not true bibtex has no real problem with 8-bit-encodings, and
>> works even quite often quite good with utf8 (when you don't try to
>> use at places where it can be broken into parts.
>>
>>
>>
>>
>> --
>> Ulrike Fischer
>> http://www.troubleshooting-tex.de/
>>
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to
>> the Wiki!
>>
>> maillist : ntg-context@ntg.nl /
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>> archive : https://foundry.supelec.fr/projects/contextrev/
>> wiki : http://contextgarden.net
>> ___________________________________________________________________________________
>>
>> ------------------------------
>>
>> End of ntg-context Digest, Vol 155, Issue 16
>> ********************************************
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
