From owner-p4-projects@FreeBSD.ORG Tue Dec 23 13:40:39 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 6E7F4106567F; Tue, 23 Dec 2008 13:40:39 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32B3E1065675 for ; Tue, 23 Dec 2008 13:40:39 +0000 (UTC) (envelope-from ed@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 215038FC22 for ; Tue, 23 Dec 2008 13:40:39 +0000 (UTC) (envelope-from ed@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id mBNDed0n080639 for ; Tue, 23 Dec 2008 13:40:39 GMT (envelope-from ed@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id mBNDecYT080637 for perforce@freebsd.org; Tue, 23 Dec 2008 13:40:38 GMT (envelope-from ed@FreeBSD.org) Date: Tue, 23 Dec 2008 13:40:38 GMT Message-Id: <200812231340.mBNDecYT080637@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to ed@FreeBSD.org using -f From: Ed Schouten To: Perforce Change Reviews Cc: Subject: PERFORCE change 155168 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2008 13:40:39 -0000 http://perforce.freebsd.org/chv.cgi?CH=155168 Change 155168 by ed@ed_flippo on 2008/12/23 13:39:50 - Add $FreeBSD$ tags to new files. - Also add Makefile and demo application to the tree. Affected files ... .. //depot/projects/mpsafetty/sys/dev/syscons/teken/Makefile#1 add .. //depot/projects/mpsafetty/sys/dev/syscons/teken/gensequences#3 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/sequences#6 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken.c#9 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken.h#11 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_demo.c#1 add .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_subr.h#14 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_subr_compat.h#2 edit .. //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_wcwidth.h#2 edit Differences ... ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/gensequences#3 (text+ko) ==== @@ -24,6 +24,8 @@ # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. +# +# $FreeBSD$ function die(msg) { print msg; ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/sequences#6 (text+ko) ==== @@ -22,6 +22,8 @@ # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. +# +# $FreeBSD$ # File format is as follows: # Abbr Abbreviation of sequence name ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/teken.c#9 (text+ko) ==== @@ -22,6 +22,8 @@ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. + * + * $FreeBSD$ */ #if defined(__FreeBSD__) && defined(_KERNEL) ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/teken.h#11 (text+ko) ==== @@ -22,6 +22,8 @@ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. + * + * $FreeBSD$ */ #ifndef _TEKEN_H_ ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_subr.h#14 (text+ko) ==== @@ -22,6 +22,8 @@ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. + * + * $FreeBSD$ */ static void teken_subr_cursor_up(teken_t *, unsigned int); ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_subr_compat.h#2 (text+ko) ==== @@ -22,6 +22,8 @@ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. + * + * $FreeBSD$ */ static void ==== //depot/projects/mpsafetty/sys/dev/syscons/teken/teken_wcwidth.h#2 (text+ko) ==== @@ -1,55 +1,4 @@ /* - * This is an implementation of wcwidth() and wcswidth() (defined in - * IEEE Std 1002.1-2001) for Unicode. - * - * http://www.opengroup.org/onlinepubs/007904975/functions/wcwidth.html - * http://www.opengroup.org/onlinepubs/007904975/functions/wcswidth.html - * - * In fixed-width output devices, Latin characters all occupy a single - * "cell" position of equal width, whereas ideographic CJK characters - * occupy two such cells. Interoperability between terminal-line - * applications and (teletype-style) character terminals using the - * UTF-8 encoding requires agreement on which character should advance - * the cursor by how many cell positions. No established formal - * standards exist at present on which Unicode character shall occupy - * how many cell positions on character terminals. These routines are - * a first attempt of defining such behavior based on simple rules - * applied to data provided by the Unicode Consortium. - * - * For some graphical characters, the Unicode standard explicitly - * defines a character-cell width via the definition of the East Asian - * FullWidth (F), Wide (W), Half-width (H), and Narrow (Na) classes. - * In all these cases, there is no ambiguity about which width a - * terminal shall use. For characters in the East Asian Ambiguous (A) - * class, the width choice depends purely on a preference of backward - * compatibility with either historic CJK or Western practice. - * Choosing single-width for these characters is easy to justify as - * the appropriate long-term solution, as the CJK practice of - * displaying these characters as double-width comes from historic - * implementation simplicity (8-bit encoded characters were displayed - * single-width and 16-bit ones double-width, even for Greek, - * Cyrillic, etc.) and not any typographic considerations. - * - * Much less clear is the choice of width for the Not East Asian - * (Neutral) class. Existing practice does not dictate a width for any - * of these characters. It would nevertheless make sense - * typographically to allocate two character cells to characters such - * as for instance EM SPACE or VOLUME INTEGRAL, which cannot be - * represented adequately with a single-width glyph. The following - * routines at present merely assign a single-cell width to all - * neutral characters, in the interest of simplicity. This is not - * entirely satisfactory and should be reconsidered before - * establishing a formal standard in this area. At the moment, the - * decision which Not East Asian (Neutral) characters should be - * represented by double-width glyphs cannot yet be answered by - * applying a simple rule from the Unicode database content. Setting - * up a proper standard for the behavior of UTF-8 character terminals - * will require a careful analysis not only of each Unicode character, - * but also of each presentation form, something the author of these - * routines has avoided to do so far. - * - * http://www.unicode.org/unicode/reports/tr11/ - * * Markus Kuhn -- 2007-05-26 (Unicode 5.0) * * Permission to use, copy, modify, and distribute this software @@ -57,6 +6,8 @@ * disclaims all warranties with regard to this software. * * Latest version: http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c + * + * $FreeBSD$ */ struct interval {