From owner-svn-doc-all@freebsd.org Mon Mar 30 18:24:41 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AB5C1262B9C; Mon, 30 Mar 2020 18:24:41 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48rgpw4gxbz44kT; Mon, 30 Mar 2020 18:24:40 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1F81021197; Mon, 30 Mar 2020 18:24:34 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02UIOXOW007330; Mon, 30 Mar 2020 18:24:33 GMT (envelope-from jhb@FreeBSD.org) Received: (from jhb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02UIOXtq007329; Mon, 30 Mar 2020 18:24:33 GMT (envelope-from jhb@FreeBSD.org) Message-Id: <202003301824.02UIOXtq007329@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jhb set sender to jhb@FreeBSD.org using -f From: John Baldwin Date: Mon, 30 Mar 2020 18:24:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54023 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: jhb X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 54023 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2020 18:24:41 -0000 Author: jhb Date: Mon Mar 30 18:24:33 2020 New Revision: 54023 URL: https://svnweb.freebsd.org/changeset/doc/54023 Log: Document 1300087 for OCF refactoring. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Sat Mar 28 15:57:17 2020 (r54022) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Mon Mar 30 18:24:33 2020 (r54023) @@ -793,6 +793,14 @@ is spelled &, < is < and > is >. 13.0-CURRENT after switching powerpc and powerpcspe to the lld linker. + + + 1300087 + 359374 + March 27, 2020 + 13.0-CURRENT after refactoring the driver and + consumer interfaces for in-kernel cryptography. + From owner-svn-doc-all@freebsd.org Mon Mar 30 20:35:43 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1C9A6266BAF; Mon, 30 Mar 2020 20:35:43 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48rkk52N1lz3x2Q; Mon, 30 Mar 2020 20:35:41 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 80E87231E1; Mon, 30 Mar 2020 20:29:05 +0000 (UTC) (envelope-from salvadore@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02UKT4E1083062; Mon, 30 Mar 2020 20:29:04 GMT (envelope-from salvadore@FreeBSD.org) Received: (from salvadore@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02UKT4UL083061; Mon, 30 Mar 2020 20:29:04 GMT (envelope-from salvadore@FreeBSD.org) Message-Id: <202003302029.02UKT4UL083061@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: salvadore set sender to salvadore@FreeBSD.org using -f From: Lorenzo Salvadore Date: Mon, 30 Mar 2020 20:29:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54024 - head/it_IT.ISO8859-15/articles X-SVN-Group: doc-head X-SVN-Commit-Author: salvadore X-SVN-Commit-Paths: head/it_IT.ISO8859-15/articles X-SVN-Commit-Revision: 54024 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2020 20:35:43 -0000 Author: salvadore (ports committer) Date: Mon Mar 30 20:29:04 2020 New Revision: 54024 URL: https://svnweb.freebsd.org/changeset/doc/54024 Log: it_IT/articles/Makefile.inc: Fix mistake Italian uses it_IT.ISO8859-15. Reported by: dbaio Approved by: bcr (docs), tcberner (co-mentor) Differential Revision: https://reviews.freebsd.org/D24223 Modified: head/it_IT.ISO8859-15/articles/Makefile.inc Modified: head/it_IT.ISO8859-15/articles/Makefile.inc ============================================================================== --- head/it_IT.ISO8859-15/articles/Makefile.inc Mon Mar 30 18:24:33 2020 (r54023) +++ head/it_IT.ISO8859-15/articles/Makefile.inc Mon Mar 30 20:29:04 2020 (r54024) @@ -2,4 +2,4 @@ # $FreeBSD$ # -DESTDIR?= ${DOCDIR}/it_IT.ISO8859-1/articles/${.CURDIR:T} +DESTDIR?= ${DOCDIR}/it_IT.ISO8859-15/articles/${.CURDIR:T} From owner-svn-doc-all@freebsd.org Tue Mar 31 01:15:01 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 516B426E610; Tue, 31 Mar 2020 01:15:01 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48rrwN56Bpz4VH0; Tue, 31 Mar 2020 01:15:00 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C50E727D73; Tue, 31 Mar 2020 01:14:54 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02V1Esv5060027; Tue, 31 Mar 2020 01:14:54 GMT (envelope-from allanjude@FreeBSD.org) Received: (from allanjude@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02V1EsaQ060026; Tue, 31 Mar 2020 01:14:54 GMT (envelope-from allanjude@FreeBSD.org) Message-Id: <202003310114.02V1EsaQ060026@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: allanjude set sender to allanjude@FreeBSD.org using -f From: Allan Jude Date: Tue, 31 Mar 2020 01:14:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54025 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: allanjude X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 54025 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2020 01:15:01 -0000 Author: allanjude Date: Tue Mar 31 01:14:54 2020 New Revision: 54025 URL: https://svnweb.freebsd.org/changeset/doc/54025 Log: Add Wednesday's "FreeBSD Office Hours" event to the front page Modified: head/share/xml/events2020.xml Modified: head/share/xml/events2020.xml ============================================================================== --- head/share/xml/events2020.xml Mon Mar 30 20:29:04 2020 (r54024) +++ head/share/xml/events2020.xml Tue Mar 31 01:14:54 2020 (r54025) @@ -92,6 +92,31 @@ audience. + + FreeBSD Office Hours + https://meet.google.com/yak-ydnk-rnc + + 2020 + 04 + 01 + + + 2020 + 04 + 01 + + + Canada + Google Hangout + Online + + On April 1st at 18:00 UTC we will hold the first + "FreeBSD Office Hours", an interactive online event + where users, contributors, and developers can ask questions + and get advice. The event will be recorded and posted to Youtube + after its conclusion. + + BSDCan 2020 https://www.bsdcan.org From owner-svn-doc-all@freebsd.org Tue Mar 31 16:37:58 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C8786262CE9; Tue, 31 Mar 2020 16:37:58 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48sFPL0mH4z4PlP; Tue, 31 Mar 2020 16:37:58 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D5A43CF52; Tue, 31 Mar 2020 16:37:48 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02VGbmpX021174; Tue, 31 Mar 2020 16:37:48 GMT (envelope-from carlavilla@FreeBSD.org) Received: (from carlavilla@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02VGbl2H021170; Tue, 31 Mar 2020 16:37:47 GMT (envelope-from carlavilla@FreeBSD.org) Message-Id: <202003311637.02VGbl2H021170@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: carlavilla set sender to carlavilla@FreeBSD.org using -f From: Sergio Carlavilla Delgado Date: Tue, 31 Mar 2020 16:37:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54026 - in head/es_ES.ISO8859-1/articles: . fonts X-SVN-Group: doc-head X-SVN-Commit-Author: carlavilla X-SVN-Commit-Paths: in head/es_ES.ISO8859-1/articles: . fonts X-SVN-Commit-Revision: 54026 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2020 16:37:59 -0000 Author: carlavilla Date: Tue Mar 31 16:37:47 2020 New Revision: 54026 URL: https://svnweb.freebsd.org/changeset/doc/54026 Log: Add spanish translation of font article Submitted by: carlavilla@ Reviewed by: carvay@ Approved by: gabor@(mentor, implicit) Obtained from: https://translate-dev.freebsd.org Added: head/es_ES.ISO8859-1/articles/fonts/ head/es_ES.ISO8859-1/articles/fonts/Makefile (contents, props changed) head/es_ES.ISO8859-1/articles/fonts/article.xml (contents, props changed) head/es_ES.ISO8859-1/articles/fonts/es_ES.po (contents, props changed) Modified: head/es_ES.ISO8859-1/articles/Makefile Modified: head/es_ES.ISO8859-1/articles/Makefile ============================================================================== --- head/es_ES.ISO8859-1/articles/Makefile Tue Mar 31 01:14:54 2020 (r54025) +++ head/es_ES.ISO8859-1/articles/Makefile Tue Mar 31 16:37:47 2020 (r54026) @@ -9,6 +9,7 @@ SUBDIR+= contributing SUBDIR+= cups SUBDIR+= explaining-bsd SUBDIR+= filtering-bridges +SUBDIR+= fonts SUBDIR+= fdp-es SUBDIR+= freebsd-questions SUBDIR+= ipsec-must Added: head/es_ES.ISO8859-1/articles/fonts/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/es_ES.ISO8859-1/articles/fonts/Makefile Tue Mar 31 16:37:47 2020 (r54026) @@ -0,0 +1,24 @@ +# +# The FreeBSD Documentation Project +# The FreeBSD Spanish Documentation Project +# +# $FreeBSD$ +# +# Article: Fonts + +MAINTAINER=carlavilla@FreeBSD.org + +DOC?= article + +FORMATS?= html html-split +WITH_ARTICLE_TOC?= YES + +INSTALL_COMPRESSED?= gz +INSTALL_ONLY_COMPRESSED?= + +SRCS= article.xml + +URL_RELPREFIX?= ../../../.. +DOC_PREFIX?= ${.CURDIR}/../../.. + +.include "${DOC_PREFIX}/share/mk/doc.project.mk" Added: head/es_ES.ISO8859-1/articles/fonts/article.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/es_ES.ISO8859-1/articles/fonts/article.xml Tue Mar 31 16:37:47 2020 (r54026) @@ -0,0 +1,684 @@ + + + + + + +
+ + Tipos de letra y FreeBSD + + Un tutorial + + + Dave Bodenstab
+ imdave@synet.net +
+ + + Wed Aug 7, 1996 + + $FreeBSD$ + + + FreeBSD is a registered trademark of the FreeBSD Foundation. + Adobe, Acrobat, Acrobat Reader, Flash and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. + Apple, AirPort, FireWire, iMac, iPhone, iPad, Mac, Macintosh, Mac OS, Quicktime, and TrueType are trademarks of Apple Inc., registered in the U.S. and other countries. + Linux is a registered trademark of Linus Torvalds. + Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. + Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the United States and other countries. + Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the ™ or the ® symbol. + + + + Este documento contiene una descripción de los diversos archivos de tipos de letra que pueden utilizarse con FreeBSD y el controlador syscons, X11, Ghostscript y Groff. También incluye manuales paso a paso para cambiar la pantalla de syscons al modo 80x60 y para usar tipos de letra de Tipo 1 con los programas anteriores. + + + + + Introducción + + Hay muchos orígenes (sources) de tipos disponibles y a veces no es fácil discernir cómo usarlos en FreeBSD. La respuesta puede estar en la documentación del componente que desea utilizar, aunque puede llevar su tiempo dar con ella; este tutorial intenta proporcionar una solución a quienes puedan estar en esas circunstancias. + + + + Terminología básica + + Hay muchos formatos de tipos diferentes y sufijos de archivos de tipos asociados. En este artículo abordaremos unos cuantos: + + + + .pfa, .pfb + + + Tipos Tipo 1 PostScript . .pfa es el formato Ascii y el .pfb es el formato Binario. + + + + + .afm + + + Métricas del tipo asociadas al tipo Tipo 1. + + + + + .pfm + + + Métricas de impresión del tipo asociadas al tipo Tipo 1. + + + + + .ttf + + + Tipo TrueType + + + + + .fot + + + Una referencia indirecta a un tipo TrueType (no es un tipo real) + + + + + .fon, .fnt + + + Tipos de pantalla de mapa de bits + + + + + El archivo .fot se usan en Windows como una especie de enlace simbólico al archivo de tipo TrueType (.ttf). Los archivos de tipo .fon también se usan en Windows. No conozco ninguna manera de usar este formato de tipo en FreeBSD. + + + + ¿Qué formatos de tipo puedo usar? + + Qué tipo se puede usar depende de la aplicación. FreeBSD por sí mismo no utiliza tipos. Las aplicaciones y/o los controladores pueden utilizar archivos de tipo. A continuación se muestra una pequeña referencia cruzada de la aplicación/controlador para los sufijos de tipo: + + + + Controlador + + + + + vt + + .hex + + + + + syscons + + + .fnt + + + + + + + + Aplicación + + + + + Ghostscript + + + .pfa, .pfb, .ttf + + + + + X11 + + + .pfa, .pfb + + + + + Groff + + + .pfa, .afm + + + + + Povray + + + .ttf + + + + + + + + La extensión .fnt es bastante común. Sospecho que la mayoría de las veces en las que alguien quería crear un archivo de tipo especializado para su aplicación elegían esta extensión. Por lo tanto es probable que no todos los archivos que incluyen esta extensión tengan el mismo formato; en concreto los archivos .fnt que usa syscons en FreeBSD pueden no tener el mismo formato que un archivo .fnt en MS-DOS/Windows. No he intentado utilizar otros archivos .fnt que no sean los suministrados con FreeBSD. + + + + Configuración de una consola virtual en modo de línea 80x60 + + En primer lugar se debe cargar un tipo 8x8. El archivo /etc/rc.conf debe tener la línea (cambie el nombre del tipo por el que sea más apropiado en su región): + + + font8x8="iso-8x8" # tipo 8x8 de /usr/share/syscons/fonts/* (o NO para cargar el tipo por defecto). + + + El comando para cambiar el modo es vidcontrol1: + + + % vidcontrol VGA_80x60 + + + Varios programas screen-oriented como vi1 pueden determinar el tamaño de la pantalla mediante una llamada de ioctl al controlador de la consola (por ejemplo syscons4) que determinará correctamente las nuevas dimensiones de la pantalla. + + Para hacerlo más sencillo puede añadir estos comandos a los scripts de inicio del sistema para que se ejecuten en el inicio. Agregue esta línea en el archivo /etc/rc.conf. + + + allscreens_flags="VGA_80x60" # Establecer el modo vidcontrol para todas las pantallas virtuales + + + Referencias: rc.conf5, vidcontrol1. + + + + Uso de tipos Type 1 con <application>X11</application> + + X11 puede utilizar tanto el formato .pfa como el formato .pfb. Los tipos para X11 se encuentran en varios subdirectorios bajo /usr/X11R6/lib/X11/fonts. Cada tipo es una referencia cruzada entre su nombre X11 y el contenido del archivo fonts.dir en cada directorio. + + Ya existe un directorio llamado Type1. La forma más sencilla de añadir un nuevo tipo es ponerla en ese directorio. Una forma aun mejor sería colocar todos los tipos que quiera añadir en un directorio separado y utilizar un enlace simbólico a los tipos adicionales. Esto permite identificar los tipos sin mezclarlos con los originales. Por ejemplo: + + + Crear un directorio para alojar los archivos de tipos. +% mkdir -p /usr/local/share/fonts/type1 +% cd /usr/local/share/fonts/type1 + +Coloque los archivos .pfa, .pfb y .afm aquí +Puede incluir también los archivos README, así como la documentación +de los tipos +% cp /cdrom/fonts/atm/showboat/showboat.pfb . +% cp /cdrom/fonts/atm/showboat/showboat.afm . + +Así se mantiene el índice para la referencia cruzada de los tipos +% echo showboat - InfoMagic CICA, Dec 1994, /fonts/atm/showboat >>INDEX + + + Para poder usar el nuevo tipo en X11 debe hacer que el archivo de tipo esté disponible y actualizar el nombre del tipo. Los nombres de los tipos de X11 tienen este aspecto: + + + -bitstream-charter-medium-r-normal-xxx-0-0-0-0-p-0-iso8859-1 + | | | | | | | | | | | | \ \ + | | | | | \ \ \ \ \ \ \ +----+- juego de caracteres + | | | | \ \ \ \ \ \ \ +- ancho promedio + | | | | \ \ \ \ \ \ +- espaciado + | | | \ \ \ \ \ \ +- resolución vertical. + | | | \ \ \ \ \ +- resolución horizontal. + | | | \ \ \ \ +- puntos + | | | \ \ \ +- píxeles + | | | \ \ \ + tipo familia densidad inclinación anchura estilo adicional + + + Cada nuevo tipo necesita tener un nombre específico. Si en la documentación que acompaña al tipo encuentra la información requerida puede usarla como base para crear el nombre. Si no hay información puede hacerse una idea utilizando el comando strings1 en el tipo. Por ejemplo: + + + % strings showboat.pfb | more +%!FontType1-1.0: Showboat 001.001 +%%CreationDate: 1/15/91 5:16:03 PM +%%VMusage: 1024 45747 +% Generated by Fontographer 3.1 +% Showboat + 1991 by David Rakowski. Alle Rechte Vorbehalten. +FontDirectory/Showboat known{/Showboat findfont dup/UniqueID known{dup +/UniqueID get 4962377 eq exch/FontType get 1 eq and}{pop false}ifelse +{save true}{false}ifelse}{false}ifelse +12 dict begin +/FontInfo 9 dict dup begin + /version (001.001) readonly def + /FullName (Showboat) readonly def + /FamilyName (Showboat) readonly def + /Weight (Medium) readonly def + /ItalicAngle 0 def + /isFixedPitch false def + /UnderlinePosition -106 def + /UnderlineThickness 16 def + /Notice (Showboat + 1991 by David Rakowski. Alle Rechte Vorbehalten.) readonly def +end readonly def +/FontName /Showboat def +--stdin-- + + + Basándonos esta información podríamos usar un nombre como este: + + + -type1-Showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 + + + Los componentes de nuestro nombre son: + + + + Tipo + + + Vamos a nombrar todos los tipos nuevos como type1. + + + + + Familia + + + El nombre del tipo. + + + + + Densidad + + + Normal, negrita, media, seminegrita, etc. En la salida del comando strings1 que acabamos de mostrar vemos que este tipo tiene una densidad media. + + + + + Inclinación + + + roman, cursiva, oblicua, etc. Dado que ItalicAngle es cero, se utilizará roman. + + + + + Anchura + + + Normal, ancha, condensada, extendida, etc. Hasta que pueda ser examinada, suponemos que será normal. + + + + + Estilo adicional + + + Generalmente se omite, pero esto indicará que el tipo contiene mayúsculas decorativas. + + + + + Espaciado + + + proporcional o monoespaciado. La opción Proportional se usa cuando isFixedPitch es false. + + + + + Todos estos nombres son arbitrarios, pero uno debe tratar de ser compatible con las convenciones existentes. El nombre hace referencia al tipo con posibles comodines del programa X11, por lo que el nombre elegido debe tener algún sentido. Simplemente puede comenzar a usar + …-normal-r-normal-…-p-… + como nombre, y luego usar xfontsel1 para examinarla y ajustar el nombre en función de la apariencia del tipo. + + Para completar nuestro ejemplo: + + + Haga que el tipo esté accesible para X11 +% cd /usr/X11R6/lib/X11/fonts/Type1 +% ln -s /usr/local/share/fonts/type1/showboat.pfb . + +Edite fonts.dir y fonts.scale, agregando la línea que describe el tipo +e incrementando el número de tipos que se encuentran en la primera línea. +% ex fonts.dir +:1p +25 +:1c +26 +. +:$a +showboat.pfb -type1-showboat-medium-r-normal-decorative-0-0-0-0-p-0-iso8859-1 +. +:wq + +fonts.scale parece ser idéntico a fonts.dir… +% cp fonts.dir fonts.scale + +Indique a X11 que las cosas han cambiado +% xset fp rehash + +Examine el nuevo tipo +% xfontsel -pattern -type1-* + + + Referencias: xfontsel1, xset1, The X Windows System in a Nutshell, O'Reilly & Associates. + + + + Uso de tipos Type 1 con Ghostscript + + Ghostscript hace referencia a un tipo a través de su archivo Fontmap. Para modificarlo hay que proceder de forma parecida a cuando mofidicamos el archivo fonts.dir de X11. Ghostscript puede usar los formatos .pfa y .pfb. A continuación ofrecemos una guía paso a paso en la que usaremos el tipo anterior para mostrar cómo usarla con Ghostscript: + + + Coloque el tipo en el directorio de tipos de Ghostscript +% cd /usr/local/share/ghostscript/fonts +% ln -s /usr/local/share/fonts/type1/showboat.pfb . + +Edite el archivo Fontmap para que Ghostscript esté al corriente del tipo +% cd /usr/local/share/ghostscript/4.01 +% ex Fontmap +:$a +/Showboat (showboat.pfb) ; % From CICA /fonts/atm/showboat +. +:wq + +Use Ghostscript para examinar el tipo +% gs prfont.ps +Aladdin Ghostscript 4.01 (1996-7-10) +Copyright (C) 1996 Aladdin Enterprises, Menlo Park, CA. All rights +reserved. +This software comes with NO WARRANTY: see the file PUBLIC for details. +Loading Times-Roman font from /usr/local/share/ghostscript/fonts/tir_____.pfb... + /1899520 581354 1300084 13826 0 done. +GS>Showboat DoFont +Loading Showboat font from /usr/local/share/ghostscript/fonts/showboat.pfb... + 1939688 565415 1300084 16901 0 done. +>>showpage, press <return> to continue<< +>>showpage, press <return> to continue<< +>>showpage, press <return> to continue<< +GS>quit + + + Referencias: consulte el archivo fonts.txt en la distribución 4.01 de Ghostscript + + + + Uso de tipos Type 1 con Groff + + Ahora que el nuevo tipo puede ser utilizada tanto por X11 como por Ghostscript ¿cómo se puede usar el nuevo tipo con groff? En primer lugar y dado que estamos utilizando tipos PostScript type 1, el dispositivo groff que vamos a usar es ps. Se debe crear un archivo de tipo para cada tipo que queramos usar con groff. Un nombre de tipo para groff es simplemente un archivo en el directorio /usr/share/groff_font/devps. Siguiendo con nuestro ejemplo, el archivo del tipo sería /usr/share/groff_font/devps/SHOWBOAT. El archivo debe crearse utilizando las herramientas proporcionadas por groff. + + La primera herramienta es afmtodit. No está instalada por defecto, pero puede encontrarla en la distribución original. Descubrí que tenía que cambiar la primera línea del archivo, así que procedí del siguiente modo: + + + % cp /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.pl /tmp +% ex /tmp/afmtodit.pl +:1c +#!/usr/bin/perl -P- +. +:wq + + + Esta herramienta creará el archivo de tipo groff a partir del archivo de métricas (sufijo .afm). Siguiendo con nuestro ejemplo: + + + Muchos archivos .afm están en formato Mac, con ^M delimitando las líneas +Tenemos que convertirlos al estilo UNIX que delimita las líneas con ^J +% cd /tmp +% cat /usr/local/share/fonts/type1/showboat.afm | + tr '\015' '\012' >showboat.afm + +Ahora cree el archivo de tipo groff +% cd /usr/share/groff_font/devps +% /tmp/afmtodit.pl -d DESC -e text.enc /tmp/showboat.afm generate/textmap SHOWBOAT + + + Ahora se puede hacer referencia al tipo con el nombre SHOWBOAT. + + Si se usa Ghostscript con las impresoras del sistema no es necesario hacer nada más. Sin embargo si las impresoras usan PostScript el tipo se debe descargar a la impresora para poder usarse (a menos que la impresora tenga el tipo showboat incorporado o pueda acceder a una unidad en la que esté .) El último paso es crear un tipo descargable. La herramienta pfbtops se utiliza para crear el formato de tipo .pfa y el archivo download se modifica para hacer referencia al nuevo tipo. El archivo download debe hacer referencia al nombre interno del tipo. Esto se puede determinar fácilmente a partir del archivo de tipo de groff como vemos a continuación: + + + Cree el archivo de tipo .pfa +% pfbtops /usr/local/share/fonts/type1/showboat.pfb >showboat.pfa + + + Por supuesto, si el archivo .pfa ya existe, simplemente cree un enlace simbólico para referenciarlo. + + + Obtener el nombre interno del tipo +% fgrep internalname SHOWBOAT +internalname Showboat + +Indique a groff que el tipo debe ser descargado +% ex download +:$a +Showboat showboat.pfa +. +:wq + + + Para probar el tipo: + + + % cd /tmp +% cat >example.t <<EOF +.sp 5 +.ps 16 +This is an example of the Showboat font: +.br +.ps 48 +.vs (\n(.s+2)p +.sp +.ft SHOWBOAT +ABCDEFGHI +.br +JKLMNOPQR +.br +STUVWXYZ +.sp +.ps 16 +.vs (\n(.s+2)p +.fp 5 SHOWBOAT +.ft R +To use it for the first letter of a paragraph, it will look like: +.sp 50p +\s(48\f5H\s0\fRere is the first sentence of a paragraph that uses the +showboat font as its first letter. +Additional vertical space must be used to allow room for the larger +letter. +EOF +% groff -Tps example.t >example.ps + +Para utilizar ghostscript/ghostview +% ghostview example.ps + +Para imprimir +% lpr -Ppostscript example.ps + + + Referencias: /usr/src/gnu/usr.bin/groff/afmtodit/afmtodit.man, groff_font5, groff_char7, pfbtops1. + + + + Conversión de tipos TrueType a un formato groff/PostScript para groff + + Esto puede llevar un poco de trabajo por la sencilla razón de que depende de algunas herramientas que no se instalan como parte del sistema base: + + + + ttf2pf + + + Herramientas de conversión de TrueType a PostScript. Esto permite la conversión de tipos TrueType a archivos de métrica de tipo ascii (.afm). + + Disponible en http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/. Nota: Estos ficheros son programas PostScript y deben descargarse manteniendo la tecla Shift cuando haga clic en el enlace. De lo contrario su navegador puede intentar arrancar ghostview para verlos. + + Los archivos importantes para esta tarea son: + + + + GS_TTF.PS + + + + PF2AFM.PS + + + + ttf2pf.ps + + + + Todo este lío de mayúsculas y minúsculas en los nombres es porque se tiene en cuenta las shells de DOS. ttf2pf.ps utiliza el resto como mayúsculas, por lo que cualquier cambio de nombre debe tener esto en cuenta. (En realidad, GS_TTF.PS y PFS2AFM.PS son parte de la distribución de Ghostscript, pero se pueden usar como herramientas independientes. FreeBSD no incluye esta última.) También puede ser que las instale (usted) en /usr/local/share/groff_font/devps(?). + + + + + afmtodit + + + Crea archivos de tipos para usar con groff desde el archivo de métricas de tipo ascii. Por lo general se encuentra en el directorio /usr/src/contrib/groff/afmtodit, pero hay unas cuantas cosas que hacer antes de poder usarlas. + + + Si cree que trabajar en /usr/src no es muy buena idea puede copiar el contenido del directorio anterior en otra ubicación. + + + En el directorio, necesitará compilar la utilidad. Escriba: + + # make -f Makefile.sub afmtodit + + Es posible que tenga que copiar también /usr/contrib/groff/devps/generate/textmap a /usr/share/groff_font/devps/generate si no existe. + + + + + Una vez que todas estas utilidades estén en su sitio, estará listo para comenzar: + + + + Cree el archivo .afm escribiendo: + + % gs -dNODISPLAY -q -- ttf2pf.ps nombre_TTF nombre_tipo_PS nombre_AFM + + Donde, TTF_name es su archivo de tipo TrueType, PS_font_name es el nombre del archivo .pfa, AFM_name es el nombre que quiere que tenga el archivo .afm. Si no especifica los nombres de los archivos de salida para los archivos .pfa o .afm, los nombres predeterminados se generan a partir del nombre de archivo de la tipo TrueType. + + Esto también produce un archivo .pfa, el archivo ascii de las métricas del tipo PostScript (.pfb es para el formato binario). Esto no será necesario, pero podría (creo) ser útil para un servidor de tipos. + + Por ejemplo, para convertir el tipo para código de barras 30f9 usando los nombres de archivo predeterminados use el siguiente comando: + + % gs -dNODISPLAY -- ttf2pf.ps 3of9.ttf +Aladdin Ghostscript 5.10 (1997-11-23) +Copyright (C) 1997 Aladdin Enterprises, Menlo Park, CA. All rights reserved. +This software comes with NO WARRANTY: see the file PUBLIC for details. +Converting 3of9.ttf to 3of9.pfa and 3of9.afm. + + Si desea que los tipos convertidos se almacenen en A.pfa y B.afm use este comando: + + % gs -dNODISPLAY -- ttf2pf.ps 3of9.ttf A B +Aladdin Ghostscript 5.10 (1997-11-23) +Copyright (C) 1997 Aladdin Enterprises, Menlo Park, CA. All rights reserved. +This software comes with NO WARRANTY: see the file PUBLIC for details. +Converting 3of9.ttf to A.pfa and B.afm. + + + + Crear el archivo PostScript groff: + + Vaya al directorio /usr/share/groff_font/devps para que sea más fácil de ejecutar el siguiente comando. Probablemente necesitará privilegios de root. (O bien, si no se siente confortable del todo trabajando en ese directorio, asegúrese de hacer referencia a los archivos DESC, text.enc y generate/textmap que están en el directorio). + + % afmtodit -d DESC -e text.enc file.afm generate/textmap nombre_tipo_PS + + Donde, file.afm es el AFM_name creado anteriormente por ttf2pf.ps y PS_font_name es el nombre del tipo utilizado para ese comando, así como el nombre que groff1 utilizará para las referencias a este tipo. Por ejemplo, suponiendo que haya utilizado el comando tiff2pf.ps anterior, el tipo para código de barras 3of9 se puede crear usando el comando: + + % afmtodit -d DESC -e text.enc 3of9.afm generate/textmap 3of9 + + Asegúrese de que el archivo PS_font_name resultante (por ejemplo, 3of9 en el ejemplo anterior) se encuentra en el directorio /usr/share/groff_font/devps al copiarlo o moverlo allí. + + Tenga en cuenta que si ttf2pf.ps asigna un nombre de tipo con el nombre que se encuentra en el archivo de tipos TrueType y quiere usar un nombre diferente antes de ejecutar afmtodit tiene que editar el archivo .afm. Este nombre también debe coincidir con el que se usa en el archivo Fontmap si desea redirigir groff1 a gs1. + + + + + + ¿Se pueden usar los tipos TrueType con otros programas? + + Windows, Windows 95 y Mac utilizan el formato de tipo TrueType. Es bastante popular y hay una gran cantidad de tipos disponibles en este formato. + + Por desgracia conozco pocas aplicaciones que puedan usar este formato: me vienen a la mente Ghostscript y Povray. Según la documentación el soporte de Ghostscript es rudimentario y es probable que los resultados sean pobres comparados con los tipos Type 1. La versión 3 de Povray también tiene la capacidad de usar tipos TrueType, pero dudo que muchas personas creen documentos como una serie de páginas con trazado de rayos :-). + + Esta situación, un tanto triste, puede cambiar pronto. El proyecto FreeType está desarrollando actualmente un conjunto útil de herramientas FreeType: + + + + + El servidor de tipos para X11, xfsft, ofrece tanto tipos TrueType como tipos normales. Actualmente está en versión beta, pero dicen que es bastante útil. Consulte la página de Juliusz Chroboczek para más información. Las instrucciones para portarlo a FreeBSD se pueden encontrar en la página de software de Stephen Montgomery. + + + + xfstt es otro servidor de tipos para X11 y está disponible en ftp://sunsite.unc.edu/pub/Linux/X11/fonts/. + + + + Un programa llamado ttf2bdf puede producir archivos BDF adecuados para su uso en un entorno X a partir de archivos TrueType. Los binarios para Linux están disponibles en ftp://crl.nmsu.edu/CLR/multiling/General/. + + + + y muchas más. + + + + + + ¿Dónde se pueden obtener tipos adicionales? + + Hay muchos tipos disponibles en Internet. Son totalmente gratuitos o shareware. Además, muchos de esos tipos están disponibles en la categoría de ports x11-fonts/ + + + + Preguntas adicionales + + + + ¿Para qué sirven los archivos .pfm? + + + + ¿Se puede generar el archivo .afm desde un archivo .pfa o .pfb? + + + + ¿Cómo generar los archivos de mapeo de caracteres groff para tipos PostScript con nombres de caracteres no estándar? + + + + ¿Se pueden configurar los dispositivos xditview y devX para acceder a todos los tipos nuevos? + + + + Sería bueno tener ejemplos del uso de tipos TrueType con Povray y Ghostscript. + + + +
Added: head/es_ES.ISO8859-1/articles/fonts/es_ES.po ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/es_ES.ISO8859-1/articles/fonts/es_ES.po Tue Mar 31 16:37:47 2020 (r54026) @@ -0,0 +1,1701 @@ +# Sergio Carlavilla , 2019. #zanata +# Sergio Carlavilla , 2020. +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2020-03-31 17:33+0200\n" +"PO-Revision-Date: 2020-03-31 15:33+0000\n" +"Last-Translator: Sergio Carlavilla \n" +"Language-Team: Spanish \n" +"Language: es_ES\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n != 1;\n" +"X-Generator: Weblate 3.11.3\n" + +#. Put one translator per line, in the form NAME , YEAR1, YEAR2 +msgctxt "_" +msgid "translator-credits" +msgstr "Sergio Carlavilla carlavilla@FreeBSD.org, 2019, 2020" + +#. (itstool) path: info/title +#: article.translate.xml:27 +msgid "Fonts and FreeBSD" +msgstr "Tipos de letra y FreeBSD" + +#. (itstool) path: info/subtitle +#: article.translate.xml:29 +msgid "A Tutorial" +msgstr "Un tutorial" + +#. (itstool) path: affiliation/address +#: article.translate.xml:38 +#, no-wrap +msgid "" +"\n" +"\t imdave@synet.net\n" +"\t " +msgstr "" +"\n" +"\t imdave@synet.net\n" +"\t " + +#. (itstool) path: authorgroup/author +#: article.translate.xml:32 +msgid "" +" Dave Bodenstab <_:address-1/> " +msgstr "" +" Dave Bodenstab <_:address-1/> " + +#. (itstool) path: info/pubdate +#: article.translate.xml:44 +msgid "Wed Aug 7, 1996" +msgstr "Wed Aug 7, 1996" + +#. (itstool) path: info/releaseinfo +#: article.translate.xml:46 +msgid "" +"$FreeBSD: head/en_US.ISO8859-1/articles/fonts/article.xml 52891 2019-03-23 " +"04:50:01Z bcr $" +msgstr "$FreeBSD$" + +#. (itstool) path: legalnotice/para +#: article.translate.xml:49 +msgid "FreeBSD is a registered trademark of the FreeBSD Foundation." +msgstr "FreeBSD is a registered trademark of the FreeBSD Foundation." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:51 +msgid "" +"Adobe, Acrobat, Acrobat Reader, Flash and PostScript are either registered " +"trademarks or trademarks of Adobe Systems Incorporated in the United States " +"and/or other countries." +msgstr "" +"Adobe, Acrobat, Acrobat Reader, Flash and PostScript are either registered " +"trademarks or trademarks of Adobe Systems Incorporated in the United States " +"and/or other countries." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:55 +msgid "" +"Apple, AirPort, FireWire, iMac, iPhone, iPad, Mac, Macintosh, Mac OS, " +"Quicktime, and TrueType are trademarks of Apple Inc., registered in the U.S. " +"and other countries." +msgstr "" +"Apple, AirPort, FireWire, iMac, iPhone, iPad, Mac, Macintosh, Mac OS, " +"Quicktime, and TrueType are trademarks of Apple Inc., registered in the U.S. " +"and other countries." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:60 +msgid "Linux is a registered trademark of Linus Torvalds." +msgstr "Linux is a registered trademark of Linus Torvalds." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:62 +msgid "" +"Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media and Windows " +"NT are either registered trademarks or trademarks of Microsoft Corporation " +"in the United States and/or other countries." +msgstr "" +"Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media and Windows " +"NT are either registered trademarks or trademarks of Microsoft Corporation " +"in the United States and/or other countries." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:66 +msgid "" +"Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The " +"Open Group are trademarks of The Open Group in the United States and other " +"countries." +msgstr "" +"Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The " +"Open Group are trademarks of The Open Group in the United States and other " +"countries." + +#. (itstool) path: legalnotice/para +#: article.translate.xml:70 +msgid "" +"Many of the designations used by manufacturers and sellers to distinguish " +"their products are claimed as trademarks. Where those designations appear in " +"this document, and the FreeBSD Project was aware of the trademark claim, the " +"designations have been followed by the â„¢ or the ® symbol." +msgstr "" +"Many of the designations used by manufacturers and sellers to distinguish " +"their products are claimed as trademarks. Where those designations appear in " +"this document, and the FreeBSD Project was aware of the trademark claim, the " +"designations have been followed by the â„¢ or the ® symbol." + +#. (itstool) path: abstract/para +#: article.translate.xml:79 +msgid "" +"This document contains a description of the various font files that may be " +"used with FreeBSD and the syscons driver, X11, " +"Ghostscript and Groff. " +"Cookbook examples are provided for switching the syscons display to 80x60 " +"mode, and for using type 1 fonts with the above application programs." +msgstr "" +"Este documento contiene una descripción de los diversos archivos de tipos de " +"letra que pueden utilizarse con FreeBSD y el controlador syscons, " +"X11, Ghostscript y " +"Groff. También incluye manuales paso a paso para " +"cambiar la pantalla de syscons al modo 80x60 y para usar tipos de letra de " +"Tipo 1 con los programas anteriores." + +#. (itstool) path: sect1/title +#: article.translate.xml:91 +msgid "Introduction" +msgstr "Introducción" + +#. (itstool) path: sect1/para +#: article.translate.xml:93 +msgid "" +"There are many sources of fonts available, and one might ask how they might " +"be used with FreeBSD. The answer can be found by carefully searching the " +"documentation for the component that one would like to use. This is very " +"time consuming, so this tutorial is an attempt to provide a shortcut for " +"others who might be interested." +msgstr "" +"Hay muchos orígenes (sources) de tipos disponibles y a veces no es fácil " +"discernir cómo usarlos en FreeBSD. La respuesta puede estar en la " +"documentación del componente que desea utilizar, aunque puede llevar su " +"tiempo dar con ella; este tutorial intenta proporcionar una solución a " +"quienes puedan estar en esas circunstancias." + +#. (itstool) path: sect1/title +#: article.translate.xml:102 +msgid "Basic Terminology" +msgstr "Terminología básica" + +#. (itstool) path: sect1/para +#: article.translate.xml:104 +msgid "" +"There are many different font formats and associated font file suffixes. A " +"few that will be addressed here are:" +msgstr "" +"Hay muchos formatos de tipos diferentes y sufijos de archivos de tipos " +"asociados. En este artículo abordaremos unos cuantos:" + +#. (itstool) path: varlistentry/term +#. (itstool) path: listitem/para +#: article.translate.xml:109 article.translate.xml:226 +msgid ".pfa, .pfb" +msgstr ".pfa, .pfb" + +#. (itstool) path: listitem/para +#: article.translate.xml:113 +msgid "" +"PostScript type 1 fonts. The " +".pfa is the Ascii form and " +".pfb the Binary form." +msgstr "" +"Tipos Tipo 1 PostScript . " +".pfa es el formato Ascii y el " +".pfb es el formato Binario." + +#. (itstool) path: varlistentry/term +#: article.translate.xml:122 +msgid ".afm" +msgstr ".afm" + +#. (itstool) path: listitem/para +#: article.translate.xml:125 +msgid "The font metrics associated with a type 1 font." +msgstr "Métricas del tipo asociadas al tipo Tipo 1." + +#. (itstool) path: varlistentry/term +#: article.translate.xml:130 +msgid ".pfm" +msgstr ".pfm" + +#. (itstool) path: listitem/para +#: article.translate.xml:133 +msgid "The printer font metrics associated with a type 1 font." +msgstr "Métricas de impresión del tipo asociadas al tipo Tipo 1." + +#. (itstool) path: varlistentry/term +#. (itstool) path: listitem/para +#: article.translate.xml:139 article.translate.xml:244 +msgid ".ttf" +msgstr ".ttf" + +#. (itstool) path: listitem/para +#: article.translate.xml:142 +msgid "A TrueType font" +msgstr "Tipo TrueType" + +#. (itstool) path: varlistentry/term +#: article.translate.xml:147 +msgid ".fot" +msgstr ".fot" + +#. (itstool) path: listitem/para +#: article.translate.xml:150 +msgid "An indirect reference to a TrueType font (not an actual font)" +msgstr "Una referencia indirecta a un tipo TrueType (no es un tipo real)" + +#. (itstool) path: varlistentry/term +#: article.translate.xml:156 +msgid ".fon, .fnt" +msgstr ".fon, .fnt" + +#. (itstool) path: listitem/para +#: article.translate.xml:162 +msgid "Bitmapped screen fonts" +msgstr "Tipos de pantalla de mapa de bits" + +#. (itstool) path: sect1/para +#: article.translate.xml:167 +msgid "" +"The .fot is used by Windows as sort of a symbolic link to the actual TrueType font (.ttf) " +"file. The .fon font files are also used by Windows. I " +"know of no way to use this font format with FreeBSD." +msgstr "" +"El archivo .fot se usan en Windows como una especie de enlace simbólico al archivo de " +"tipo TrueType (.ttf). Los archivos de tipo .fon también se usan " +"en Windows. No conozco ninguna manera de usar este formato de tipo en " +"FreeBSD." + +#. (itstool) path: sect1/title +#: article.translate.xml:175 +msgid "What Font Formats Can I Use?" +msgstr "¿Qué formatos de tipo puedo usar?" + *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@freebsd.org Tue Mar 31 21:22:34 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3CC0E26CD8F; Tue, 31 Mar 2020 21:22:34 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48sMjh0BfFz4Hrd; Tue, 31 Mar 2020 21:22:31 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DE48E18FB1; Tue, 31 Mar 2020 21:22:23 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02VLMNOf002413; Tue, 31 Mar 2020 21:22:23 GMT (envelope-from brooks@FreeBSD.org) Received: (from brooks@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02VLMNHJ002412; Tue, 31 Mar 2020 21:22:23 GMT (envelope-from brooks@FreeBSD.org) Message-Id: <202003312122.02VLMNHJ002412@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: brooks set sender to brooks@FreeBSD.org using -f From: Brooks Davis Date: Tue, 31 Mar 2020 21:22:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54027 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: brooks X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 54027 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2020 21:22:34 -0000 Author: brooks (src,ports committer) Date: Tue Mar 31 21:22:23 2020 New Revision: 54027 URL: https://svnweb.freebsd.org/changeset/doc/54027 Log: Update my key. Modified: head/share/pgpkeys/brooks.key Modified: head/share/pgpkeys/brooks.key ============================================================================== --- head/share/pgpkeys/brooks.key Tue Mar 31 16:37:47 2020 (r54026) +++ head/share/pgpkeys/brooks.key Tue Mar 31 21:22:23 2020 (r54027) @@ -1,168 +1,54 @@ -uid Brooks Davis -uid Brooks Davis -uid Brooks Davis -sub 2048g/CFDACA7A 2003-01-25 [expires: 2016-04-30] -sub 1024g/42921194 2001-02-10 [expires: 2016-04-30] +pub 2048R/ACD05DB49E6E07C0 2015-04-24 [expires: 2021-04-19] + Key fingerprint = 4AD6 486F D9B2 A7B6 E086 3B1E ACD0 5DB4 9E6E 07C0 +uid Brooks Eugene Davis +uid Brooks Eugene Davis +sub 2048R/4055CD642D33B023 2015-04-24 [expires: 2021-04-19] + ]]> From owner-svn-doc-all@freebsd.org Tue Mar 31 22:45:06 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2CECF26F171; Tue, 31 Mar 2020 22:45:06 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48sPXw6SYkz3LBP; Tue, 31 Mar 2020 22:45:04 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 71F7B19FED; Tue, 31 Mar 2020 22:44:56 +0000 (UTC) (envelope-from brooks@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 02VMitLk051886; Tue, 31 Mar 2020 22:44:55 GMT (envelope-from brooks@FreeBSD.org) Received: (from brooks@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 02VMitnR051885; Tue, 31 Mar 2020 22:44:55 GMT (envelope-from brooks@FreeBSD.org) Message-Id: <202003312244.02VMitnR051885@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: brooks set sender to brooks@FreeBSD.org using -f From: Brooks Davis Date: Tue, 31 Mar 2020 22:44:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54028 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head X-SVN-Commit-Author: brooks X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/committers-guide X-SVN-Commit-Revision: 54028 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2020 22:45:06 -0000 Author: brooks (src,ports committer) Date: Tue Mar 31 22:44:55 2020 New Revision: 54028 URL: https://svnweb.freebsd.org/changeset/doc/54028 Log: Passify igor: use tabs not spaces, wrap one line. It's now feasible to use igor to spellcheck this document. There are still a few reported issues, but I belive they are false positives due to nested s. Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Mar 31 21:22:23 2020 (r54027) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Mar 31 22:44:55 2020 (r54028) @@ -265,7 +265,7 @@ RSA keys may be between 1024 and 4096 bits long. What keysize do you want? (2048) 2048 Requested keysize is 2048 bits Please specify how long the key should be valid. - 0 = key does not expire + 0 = key does not expire <n> = key expires in n days <n>w = key expires in n weeks <n>m = key expires in n months @@ -4007,66 +4007,66 @@ Relnotes: yes cost associated with additional platform support. The &os; Project differentiates platform targets into four - tiers. Each tier includes a list of guarantees consumers may - rely on as well as obligations by the Project and developers - to fulfill those guarantees. These lists define the minimum - guarantees for each tier. The Project and developers may - provide additional levels of support beyond the minimum - guarantees for a given tier, but such additional support is - not guaranteed. Each platform target is assigned to a - specific tier for each stable branch. As a result, a platform - target might be assigned to different tiers on concurrent - stable branches. + tiers. Each tier includes a list of guarantees consumers may + rely on as well as obligations by the Project and developers + to fulfill those guarantees. These lists define the minimum + guarantees for each tier. The Project and developers may + provide additional levels of support beyond the minimum + guarantees for a given tier, but such additional support is + not guaranteed. Each platform target is assigned to a + specific tier for each stable branch. As a result, a platform + target might be assigned to different tiers on concurrent + stable branches. Platform Targets Support for a hardware platform consists of two - components: kernel support and userland Application Binary - Interfaces (ABIs). Kernel platform support includes things - needed to run a &os; kernel on a hardware platform such as - machine-dependent virtual memory management and device - drivers. A userland ABI specifies an interface for user - processes to interact with a &os; kernel and base system - libraries. A userland ABI includes system call interfaces, - the layout and semantics of public data structures, and the - layout and semantics of arguments passed to subroutines. Some - components of an ABI may be defined by specifications such as - the layout of C++ exception objects or calling conventions for - C functions. + components: kernel support and userland Application Binary + Interfaces (ABIs). Kernel platform support includes things + needed to run a &os; kernel on a hardware platform such as + machine-dependent virtual memory management and device + drivers. A userland ABI specifies an interface for user + processes to interact with a &os; kernel and base system + libraries. A userland ABI includes system call interfaces, + the layout and semantics of public data structures, and the + layout and semantics of arguments passed to subroutines. Some + components of an ABI may be defined by specifications such as + the layout of C++ exception objects or calling conventions for + C functions. A &os; kernel also uses an ABI (sometimes referred to as - the Kernel Binary Interface (KBI)) which includes the - semantics and layouts of public data structures and the layout - and semantics of arguments to public functions within the - kernel itself. + the Kernel Binary Interface (KBI)) which includes the + semantics and layouts of public data structures and the layout + and semantics of arguments to public functions within the + kernel itself. A &os; kernel may support multiple userland ABIs. For - example, &os;'s amd64 kernel supports &os; amd64 and i386 - userland ABIs as well as Linux x86_64 and i386 userland ABIs. - A &os; kernel should support a native ABI as - the default ABI. The native ABI generally - shares certain properties with the kernel ABI such as the C - calling convention, sizes of basic types, etc. + example, &os;'s amd64 kernel supports &os; amd64 and i386 + userland ABIs as well as Linux x86_64 and i386 userland ABIs. + A &os; kernel should support a native ABI as + the default ABI. The native ABI generally + shares certain properties with the kernel ABI such as the C + calling convention, sizes of basic types, etc. Tiers are defined for both kernels and userland ABIs. In - the common case, a platform's kernel and &os; ABIs are - assigned to the same tier. + the common case, a platform's kernel and &os; ABIs are + assigned to the same tier. Tier 1: Fully-Supported Architectures Tier 1 platforms are the most mature &os; platforms. - They are supported by the security officer, release - engineering, and port management teams. Tier 1 architectures - are expected to be Production Quality with respect to all - aspects of the &os; operating system, including installation - and development environments. + They are supported by the security officer, release + engineering, and port management teams. Tier 1 architectures + are expected to be Production Quality with respect to all + aspects of the &os; operating system, including installation + and development environments. The &os; Project provides the following guarantees to - consumers of Tier 1 platforms: + consumers of Tier 1 platforms: @@ -4142,8 +4142,8 @@ Relnotes: yes To maintain maturity of Tier 1 platforms, the &os; Project - will maintain the following resources to support - development: + will maintain the following resources to support + development: @@ -4165,7 +4165,7 @@ Relnotes: yes Collectively, developers are required to provide the - following to maintain the Tier 1 status of a platform: + following to maintain the Tier 1 status of a platform: @@ -4203,18 +4203,18 @@ Relnotes: yes Tier 2: Developmental and Niche Architectures Tier 2 platforms are functional, but less mature &os; - platforms. They are not supported by the security officer, - release engineering, and port management teams. + platforms. They are not supported by the security officer, + release engineering, and port management teams. Tier 2 platforms may be Tier 1 platform candidates that - are still under active development. Architectures reaching - end of life may also be moved from Tier 1 status to Tier 2 - status as the availability of resources to continue to - maintain the system in a Production Quality state diminishes. - Well-supported niche architectures may also be Tier 2. + are still under active development. Architectures reaching + end of life may also be moved from Tier 1 status to Tier 2 + status as the availability of resources to continue to + maintain the system in a Production Quality state diminishes. + Well-supported niche architectures may also be Tier 2. The &os; Project provides the following guarantees to - consumers of Tier 2 platforms: + consumers of Tier 2 platforms: @@ -4248,8 +4248,8 @@ Relnotes: yes To maintain maturity of Tier 2 platforms, the &os; Project - will maintain the following resources to support - development: + will maintain the following resources to support + development: @@ -4259,7 +4259,7 @@ Relnotes: yes Collectively, developers are required to provide the - following to maintain the Tier 2 status of a platform: + following to maintain the Tier 2 status of a platform: @@ -4288,22 +4288,22 @@ Relnotes: yes Tier 3: Experimental Architectures Tier 3 platforms have at least partial &os; support. They - are not supported by the security - officer, release engineering, and port management - teams. + are not supported by the security + officer, release engineering, and port management + teams. Tier 3 platforms are architectures in the early stages of - development, for non-mainstream hardware platforms, or which - are considered legacy systems unlikely to see broad future - use. Initial support for Tier 3 platforms may exist in a - separate repository rather than the main source - repository. + development, for non-mainstream hardware platforms, or which + are considered legacy systems unlikely to see broad future + use. Initial support for Tier 3 platforms may exist in a + separate repository rather than the main source + repository. The &os; Project provides no guarantees to consumers of - Tier 3 platforms and is not committed to maintaining resources - to support development. Tier 3 platforms may not always be - buildable, nor are any kernel or userland ABIs considered - stable. + Tier 3 platforms and is not committed to maintaining resources + to support development. Tier 3 platforms may not always be + buildable, nor are any kernel or userland ABIs considered + stable. @@ -4313,21 +4313,21 @@ Relnotes: yes project. All systems not otherwise classified are Tier 4 systems. - When a platform transitions to Tier 4, all support for the - platform is removed from the source and ports trees. Note - that ports support should remain as long as the platform is - supported in a branch supported by ports. + When a platform transitions to Tier 4, all support for the + platform is removed from the source and ports trees. Note + that ports support should remain as long as the platform is + supported in a branch supported by ports. Policy on Changing the Tier of an Architecture Systems may only be moved from one tier to another by - approval of the &os; Core Team, which shall make that decision - in collaboration with the Security Officer, Release - Engineering, and ports management teams. For a platform to be - promoted to a higher tier, any missing support guarantees must - be satisfied before the promotion is completed. + approval of the &os; Core Team, which shall make that decision + in collaboration with the Security Officer, Release + Engineering, and ports management teams. For a platform to be + promoted to a higher tier, any missing support guarantees must + be satisfied before the promotion is completed. @@ -5375,7 +5375,8 @@ Do you want to commit? (no = start a shell) [y/n] - &a.portmgr; will reply with a possible fallout. + &a.portmgr; will reply with a possible + fallout. From owner-svn-doc-all@freebsd.org Wed Apr 1 07:42:05 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 844622B3964; Wed, 1 Apr 2020 07:42:05 +0000 (UTC) (envelope-from bofh@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48sdSS6DvTz4QGn; Wed, 1 Apr 2020 07:42:00 +0000 (UTC) (envelope-from bofh@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 668002168D; Wed, 1 Apr 2020 07:41:55 +0000 (UTC) (envelope-from bofh@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 0317ftS7097376; Wed, 1 Apr 2020 07:41:55 GMT (envelope-from bofh@FreeBSD.org) Received: (from bofh@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 0317ftXW097375; Wed, 1 Apr 2020 07:41:55 GMT (envelope-from bofh@FreeBSD.org) Message-Id: <202004010741.0317ftXW097375@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bofh set sender to bofh@FreeBSD.org using -f From: Muhammad Moinur Rahman Date: Wed, 1 Apr 2020 07:41:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54029 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: bofh X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 54029 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 07:42:06 -0000 Author: bofh (ports committer) Date: Wed Apr 1 07:41:54 2020 New Revision: 54029 URL: https://svnweb.freebsd.org/changeset/doc/54029 Log: Update my(bofh) expired key M pgpkeys/bofh.key Modified: head/share/pgpkeys/bofh.key Modified: head/share/pgpkeys/bofh.key ============================================================================== --- head/share/pgpkeys/bofh.key Tue Mar 31 22:44:55 2020 (r54028) +++ head/share/pgpkeys/bofh.key Wed Apr 1 07:41:54 2020 (r54029) @@ -3,12 +3,14 @@ sh addkey.sh bofh BDB9B5A617C0BC91 ; --> -uid Muhammad Moinur Rahman (Official) -uid Muhammad Moinur Rahman (FreeBSD) -sub rsa4096/3D4FC5F1173A113A 2014-12-17 [expires: 2017-12-17] +uid Muhammad Moinur Rahman +uid Muhammad Moinur Rahman (FreeBSD) +uid Muhammad Moinur Rahman (Official) +uid Muhammad Moinur Rahman +uid Muhammad Moinur Rahman +sub elg4096/41CD79B64360E65D 2020-02-01 [E] [expires: 2024-02-01] ]]> From owner-svn-doc-all@freebsd.org Wed Apr 1 14:25:43 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 577B82BD4C9; Wed, 1 Apr 2020 14:25:43 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48spQG2GLnz3JW2; Wed, 1 Apr 2020 14:25:42 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1060C267B4; Wed, 1 Apr 2020 14:16:19 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 031EGIGN037567; Wed, 1 Apr 2020 14:16:18 GMT (envelope-from blackend@FreeBSD.org) Received: (from blackend@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 031EGIC8037566; Wed, 1 Apr 2020 14:16:18 GMT (envelope-from blackend@FreeBSD.org) Message-Id: <202004011416.031EGIC8037566@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: blackend set sender to blackend@FreeBSD.org using -f From: Marc Fonvieille Date: Wed, 1 Apr 2020 14:16:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54030 - head/fr_FR.ISO8859-1/books/handbook/bsdinstall X-SVN-Group: doc-head X-SVN-Commit-Author: blackend X-SVN-Commit-Paths: head/fr_FR.ISO8859-1/books/handbook/bsdinstall X-SVN-Commit-Revision: 54030 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 14:25:43 -0000 Author: blackend Date: Wed Apr 1 14:16:18 2020 New Revision: 54030 URL: https://svnweb.freebsd.org/changeset/doc/54030 Log: MFen: r53961 --> r53979 Modified: head/fr_FR.ISO8859-1/books/handbook/bsdinstall/chapter.xml Modified: head/fr_FR.ISO8859-1/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/fr_FR.ISO8859-1/books/handbook/bsdinstall/chapter.xml Wed Apr 1 07:41:54 2020 (r54029) +++ head/fr_FR.ISO8859-1/books/handbook/bsdinstall/chapter.xml Wed Apr 1 14:16:18 2020 (r54030) @@ -4,7 +4,7 @@ The FreeBSD French Documentation Project $FreeBSD$ - Original revision: 53961 + Original revision: 53979 --> - Partitionnement guidé + Partitionnement guidé avec utilisation d'UFS Quand cette méthode est sélectionnée, un menu affichera le(s) disque(s) disponible(s). @@ -1432,6 +1432,43 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. + Après la sélection de + [ Entire Disk ], + bsdinstall affiche une boîte de + dialogue indiquant que le disque va être effacé. + +
+ Confirmation + + + + + + +
+ + Le menu suivant montre une liste avec les différents types + d'organisation des partitions. GPT est généralement le choix + le plus adapté pour les ordinateurs de type amd64. Les + ordinateurs plus anciens qui ne sont pas compatibles avec GPT + devraient utiliser un partionnement de type MBR. Les autres + types de partionnement sont généralement utilisés pour les + ordinateurs peu courants ou anciens. Plus d'informations sont + disponibles dans la . + +
+ Sélection du système de partionnement + + + + + + +
+ Une fois l'organisation des partitions créée, vérifiez-la afin de s'assurer qu'elle correspond bien aux besoins de l'installation. La sélection de @@ -1453,9 +1490,35 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. + + Une fois les disques configurés, le menu suivant offre une + dernière chance pour effectuer des modifications avant que les + disques sélectionnés ne soient formatés. Si des + changements doivent être faits, choisir + [ Back ] pour retourner dans le + menu principal de partionnement. + [ Revert & Exit ] + fera quitter le programme d'installation sans qu'aucun + changement n'ait été appliqué au disque dur. Sélectionner + [ Commit ] pour lancer le + processus d'installation. + +
+ Confirmation finale + + + + + + +
+ + Pour poursuivre le processus d'installation, aller à la + . - + Partitionnement manuel La sélection de cette méthode ouvre l'éditeur @@ -1497,7 +1560,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - +
Tables de partitionnement @@ -1581,17 +1644,20 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. + freebsd-zfs - Un système de + fichiers ZFS &os;. Plus d'informations + au sujet de ZFS est disponible dans le . + + + freebsd-swap - Espace de pagination pour &os;. - Un autre type de partition qui vaut la peine d'être - mentionné freebsd-zfs, employé pour des - partitions qui contiendront un système de fichiers &os; - ZFS (Voir ). - Consulter la page de manuel &man.gpart.8; pour la description - d'autres types de partitions disponibles pour + Consulter la page de manuel &man.gpart.8; pour la + description d'autres types de partitions disponibles pour GPT. Des partitions avec plusieurs systèmes de fichiers peuvent @@ -1733,11 +1799,12 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.Après la création des partitions, sélectionnez [ Finish ] pour poursuivre - l'installation. + l'installation et rendez-vous à la + . - Partitionnement automatique avec la racine du système de + <title>Partitionnement guidé avec la racine du système de fichiers sur ZFS Le support pour la création automatique d'installations @@ -1926,34 +1993,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - - Procéder à l'installation + + Récupération des fichiers de distribution - Une fois les disques configurés, le menu suivant offre une - dernière chance pour effectuer des modifications avant que le(s) - disque(s) sélectionné(s) ne soi(en)t formaté(s). Si des - changements doivent être faits, choisir - [ Back ] pour retourner dans le - menu principal de partionnement. - [ Revert & Exit ] - fera quitter le programme d'installation sans qu'aucun - changement n'ait été appliqué au disque dur. - -
- Confirmation finale - - - - - - -
- - Pour lancer véritablement l'installation, sélectionner - [ Commit ] et - appuyer sur Enter. - La durée de l'installation variera en fonction de la distribution choisie, du support d'installation, et de la vitesse de l'ordinateur. Une série de messages @@ -1962,8 +2004,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.En premier lieu, le programme d'installation formatera le(s) disque(s) sélectionné(s) et initialisera les partitions. Ensuite, dans le cas d'une installation à partir d'un support - bootonly, il téléchargera les - composants sélectionnés: + bootonly media ou mini + memstick, il téléchargera les composants + sélectionnés:
Récupération des fichiers de distribution From owner-svn-doc-all@freebsd.org Wed Apr 1 19:26:41 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0C35127EA09; Wed, 1 Apr 2020 19:26:41 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48sx5V4Vv8z3KXS; Wed, 1 Apr 2020 19:26:38 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9D2312D22; Wed, 1 Apr 2020 19:26:30 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 031JQUjL027511; Wed, 1 Apr 2020 19:26:30 GMT (envelope-from jhb@FreeBSD.org) Received: (from jhb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 031JQUdH027510; Wed, 1 Apr 2020 19:26:30 GMT (envelope-from jhb@FreeBSD.org) Message-Id: <202004011926.031JQUdH027510@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jhb set sender to jhb@FreeBSD.org using -f From: John Baldwin Date: Wed, 1 Apr 2020 19:26:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54031 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: jhb X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 54031 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2020 19:26:41 -0000 Author: jhb Date: Wed Apr 1 19:26:30 2020 New Revision: 54031 URL: https://svnweb.freebsd.org/changeset/doc/54031 Log: Document 1300088 for removal of procfs process debugging. Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Apr 1 14:16:18 2020 (r54030) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Apr 1 19:26:30 2020 (r54031) @@ -801,6 +801,14 @@ is spelled &, < is < and > is >. 13.0-CURRENT after refactoring the driver and consumer interfaces for in-kernel cryptography. + + + 1300088 + 359530 + April 1, 2020 + 13.0-CURRENT after removing support for procfs + process debugging. +
From owner-svn-doc-all@freebsd.org Fri Apr 3 03:49:14 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 838F52729B8; Fri, 3 Apr 2020 03:49:14 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48tmBw5LzNz4LBw; Fri, 3 Apr 2020 03:49:12 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9643225578; Fri, 3 Apr 2020 03:49:02 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 0333n2MA028662; Fri, 3 Apr 2020 03:49:02 GMT (envelope-from allanjude@FreeBSD.org) Received: (from allanjude@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 0333n2pa028661; Fri, 3 Apr 2020 03:49:02 GMT (envelope-from allanjude@FreeBSD.org) Message-Id: <202004030349.0333n2pa028661@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: allanjude set sender to allanjude@FreeBSD.org using -f From: Allan Jude Date: Fri, 3 Apr 2020 03:49:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54032 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: allanjude X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 54032 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2020 03:49:14 -0000 Author: allanjude Date: Fri Apr 3 03:49:02 2020 New Revision: 54032 URL: https://svnweb.freebsd.org/changeset/doc/54032 Log: Add the second FreeBSD Office Hours Update the link to the previous office hours to point to the recording Sponsored by: Klara Inc. Modified: head/share/xml/events2020.xml Modified: head/share/xml/events2020.xml ============================================================================== --- head/share/xml/events2020.xml Wed Apr 1 19:26:30 2020 (r54031) +++ head/share/xml/events2020.xml Fri Apr 3 03:49:02 2020 (r54032) @@ -94,7 +94,7 @@ FreeBSD Office Hours - https://meet.google.com/yak-ydnk-rnc + https://www.youtube.com/watch?v=6qBm5NM3zTQ 2020 04 @@ -115,6 +115,31 @@ where users, contributors, and developers can ask questions and get advice. The event will be recorded and posted to Youtube after its conclusion. + + + + FreeBSD Office Hours + https://live.freebsd.org/FreeBSD/officehours/ + + 2020 + 04 + 15 + + + 2020 + 04 + 16 + + + Canada + Online + live.FreeBSD.org + + On April 16th at 02:00 UTC (April 15th in North America) + we will hold the second "FreeBSD Office Hours", an + interactive online event where users, contributors, and developers + can ask questions and get advice. The event will be recorded and + posted to Youtube after its conclusion.