From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/88328 Path: news.gmane.org!not-for-mail From: Otared Kavian Newsgroups: gmane.comp.tex.context Subject: Re: Leave out reference to page if on the same page? Date: Sat, 2 Aug 2014 18:58:21 +0200 Message-ID: References: <9B2F0029-A808-473D-99C1-D3CC9AAE5A7C@rna.nl> <53D05484.3040803@panix.com> <7A5A73AF-CB29-45CC-A070-A83FA3DFE41D@gmail.com> <53D23A47.9030200@wxs.nl> <53D36A35.3070901@wxs.nl> <7A9000F5-B8BD-4165-8C16-5E49D7D12134@rna.nl> <875F0024-82BF-4D4A-9F2E-3858A5A173F3@gmail.com> <353BFB63-2442-421B-8402-EDA5D3D275B0@rna.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: multipart/mixed; boundary="===============1566148576==" X-Trace: ger.gmane.org 1406998735 19165 80.91.229.3 (2 Aug 2014 16:58:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 2 Aug 2014 16:58:55 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Sat Aug 02 18:58:51 2014 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([5.39.185.229]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XDcdq-0007YS-3w for gctc-ntg-context-518@m.gmane.org; Sat, 02 Aug 2014 18:58:46 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id C75F510279 for ; Sat, 2 Aug 2014 18:58:45 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QKA6WpsIsJ1E for ; Sat, 2 Aug 2014 18:58:45 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [IPv6:::1]) by balder.ntg.nl (Postfix) with ESMTP id 8C8F010221 for ; Sat, 2 Aug 2014 18:58:37 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id 92D1B101E6 for ; Sat, 2 Aug 2014 18:58:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MR-VVwvGHLfu for ; Sat, 2 Aug 2014 18:58:28 +0200 (CEST) Original-Received: from filter3-ams.mf.surf.net (filter3-ams.mf.surf.net [192.87.102.71]) by balder.ntg.nl (Postfix) with ESMTP id 65BE6101E2 for ; Sat, 2 Aug 2014 18:58:25 +0200 (CEST) Original-Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by filter3-ams.mf.surf.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id s72GwO3W029520 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Sat, 2 Aug 2014 18:58:24 +0200 Original-Received: by mail-we0-f178.google.com with SMTP id w61so5763035wes.37 for ; Sat, 02 Aug 2014 09:58:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=lHdrepGfJnR0b0dGQr46kp/xHolTARhmCi0ZhsVGwcc=; b=AQxuDz10lylGE2l/cYP+qrvEihHWZvSAV9dGB3pVanc+OJrSefnRd9baNedxM0j53x sTWEpKHO6nI7mWqhyiQ0UeNSjXBOsJDm2SgK5e9wyvOkfzKpWZl7hOon2DmMOpiRu6g1 qfBi5m3AAVa/75EqHj2JYo1z0WAJt6AMI+Xb7/tNeqDxbnKCN14iYuYSfB6MOE+0ZbH6 jufS+/WuM+FgXarD2B4xto7JIdyeBw8Lg8y2z6HtkRGs2fi3ebA1P8J9+2zm5gubNPky N4+qR41s/7KD/uFoONKcmQJjZGkB+N6/eHPq5Djcwi/bIOZcMC9DXC6q7KLUcmEw/2e0 siNA== X-Received: by 10.180.72.234 with SMTP id g10mr320837wiv.52.1406998704136; Sat, 02 Aug 2014 09:58:24 -0700 (PDT) Original-Received: from [192.168.0.101] (lns-bzn-45-82-65-130-218.adsl.proxad.net. [82.65.130.218]) by mx.google.com with ESMTPSA id n2sm29434765wjf.40.2014.08.02.09.58.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 02 Aug 2014 09:58:23 -0700 (PDT) In-Reply-To: X-Mailer: Apple Mail (2.1878.6) X-Bayes-Prob: 0.0001 (Score 0, tokens from: ntg-context@ntg.nl, base:default, @@RPTN) X-CanIt-Geo: ip=2a00:1450:400c:c03::232; country=IE X-CanItPRO-Stream: uu:ntg-context@ntg.nl (inherits from uu:default, base:default) X-Canit-Stats-ID: 03MxQWobp - 98cbcb149745 - 20140802 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.14 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:88328 Archived-At: --===============1566148576== Content-Type: multipart/alternative; boundary="Apple-Mail=_DA51C41E-BC6B-466C-878A-5B56B72C3329" --Apple-Mail=_DA51C41E-BC6B-466C-878A-5B56B72C3329 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi Gerben, Regarding the text encodings understood by mkii and mkiv, one can always = use UTF-8 in both. Unless you have some very uncommon characters in your ascii file, the = migration from ascii to utf-8 is quite easy, at least on a Mac (I don=92t = know what OS you are using): for instance you can open the file in an = application such as Smultron or Fraise http://www.macupdate.com/app/mac/33751/fraise and then in the =AB Text =BB menu choose =AB Text encoding =BB and then = =AB UTF-8 =BB. After that you save your file: now it is in UTF-8 = encoding and can be typeset in mkiv, as far as the commands you use in = your TeX file is compatible with mkiv. Best regards: OK On 02 Aug 2014, at 15:24, Gerben Wierda wrote: > On 02 Aug 2014, at 15:12, Gerben Wierda wrote: >=20 >> I suspected as such. I=92m afraid to move to mkiv at this stage of my = project. Is mkiv downwards compatible with mkii? What must I do to see = if my project compiles with mkiv? I=92m running currently commands like >=20 > Later for me. I read: >=20 > Mark IV needs your input to be in UTF-8. Legacy documents using 8bit = encodings have to be converted to utf-8 before they are usable. >=20 > that enough is a show stopper for me at this point. All my input is in = ascii code edited with a simple emacs-like editor. Moving to UTF8 at = this stage is out of the question unless I get my editor to do that. >=20 > G > = __________________________________________________________________________= _________ > If your question is of interest to others as well, please add an entry = to the Wiki! >=20 > maillist : ntg-context@ntg.nl / = http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > = __________________________________________________________________________= _________ --Apple-Mail=_DA51C41E-BC6B-466C-878A-5B56B72C3329 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Hi Gerben,

Regarding the = text encodings understood by mkii and mkiv, one can always use UTF-8 in = both.
Unless you have some very uncommon characters in your ascii = file, the migration from ascii to utf-8 is quite easy, at least on a Mac = (I don=92t know what OS you are using): for instance you can open = the file in an application such as Smultron or = Fraise
and then in the =AB Text =BB = menu choose =AB Text encoding =BB and then =AB UTF-8 =BB. After that you = save your file: now it is in UTF-8 encoding and can be typeset in mkiv, = as far as the commands you use in your TeX file is compatible with = mkiv.

Best regards: = OK

On 02 Aug 2014, at 15:24, Gerben Wierda = <gerben.wierda@rna.nl> = wrote:

On 02 = Aug 2014, at 15:12, Gerben Wierda <gerben.wierda@rna.nl> = wrote:

I = suspected as such. I=92m afraid to move to mkiv at this stage of my = project. Is mkiv downwards compatible with mkii? What must I do to see = if my project compiles with mkiv? I=92m running currently commands = like

Later for me. I = read:

Mark IV needs = your input to be in UTF-8. Legacy documents using 8bit encodings have to = be converted to utf-8 before they are = usable.

that enough is a show stopper for = me at this point. All my input is in ascii code edited with a simple = emacs-like editor. Moving to UTF8 at this stage is out of the question = unless I get my editor to do = that.

G
______________________________= _____________________________________________________
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 =  : http://foundry.sup= elec.fr/projects/contextrev/
wiki     : http://contextgarden.net
________= __________________________________________________________________________= _

= --Apple-Mail=_DA51C41E-BC6B-466C-878A-5B56B72C3329-- --===============1566148576== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ --===============1566148576==--