From nobody Sat Jan 29 14:21:51 2022 X-Original-To: dev-commits-doc-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 37C8F198CB0F for ; Sat, 29 Jan 2022 14:21:52 +0000 (UTC) (envelope-from git@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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JmGjX18K6z55M3; Sat, 29 Jan 2022 14:21:52 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643466112; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Qm6X8Lo/ImyLYQQLcpIRdl+w2iUf7lplgPkR1mI6YyM=; b=kkI6Q7fIHD1FGhS1NP0Ytkol8lNC74H1vrOOfJNdbDi5+onAaizKdhlEotWVneQrNaIQ2b PcPz7Nto/E+tAQQTLIjI5mf8T6BReajS65PPfyE5fq5ocnzsT3GvWZ8UPDoBjsL8q44Gow baUsieJYvW0LMIIojWJlefaoR4lGJ/c7LeGJ71USP0mm3Cr8ryJL7QCGm26NBPmaHrD7bJ r+B1i42zj+JOP4O4CTkKoXRKdBX73IlX1c23YlEG/fk2dQdT7Iz+dvWCXfDH7UFsKg6CqZ vK0II+yD7IX7qY+3xBBGbsHq05BLrbc0jAiaB6NBGOTNOpNNn+t0h6hGPQAQhw== Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 07ABA17610; Sat, 29 Jan 2022 14:21:52 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 20TELpti098575; Sat, 29 Jan 2022 14:21:51 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 20TELpTg098574; Sat, 29 Jan 2022 14:21:51 GMT (envelope-from git) Date: Sat, 29 Jan 2022 14:21:51 GMT Message-Id: <202201291421.20TELpTg098574@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Benedict Reuschling Subject: git: 1f9b2d8130 - main - Fix some typos in the Wine chapter and remove trailing whitespaces. List-Id: Commit messages for all branches of the doc repository List-Archive: https://lists.freebsd.org/archives/dev-commits-doc-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-doc-all@freebsd.org X-BeenThere: dev-commits-doc-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: bcr X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 1f9b2d8130303df35e48207632ccbf10ef3a9f5d Auto-Submitted: auto-generated ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643466112; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=Qm6X8Lo/ImyLYQQLcpIRdl+w2iUf7lplgPkR1mI6YyM=; b=Hc6Pst02TQBVRTc/THb0yRXlW+9NmNbCjEO5fwz8HjfOSvXLoTCEv2IRk3u/3wTP/D3sJM L7faQqyNiK0Ryh1BzePE47byLLUmOCvQcpY4/04lNISstRmeyfB/IQ4rBCQPGFX4z5TM+B 5+Tw+Mmn/+Zwk2tpNby/l3aq+/dU52p8BDwTGi/mXxG9TASttN9dEQQFZQ+YUzwbxAMYja PEif0SmxxANOuPvL4i/P/ot3CZcbq7ju22RzcKm1NaACit4J1mcK56yUxTeZsNq28eIthw BNPKaud1AajGJPVOLHWutpBE7eUVM9XUXpmGCZiYZHVnTMVIhaX2dxSDLKgYPw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643466112; a=rsa-sha256; cv=none; b=vfoMF8zhizV7ea0xr4o3U59cQvw4WqsUZeRNN4+dHibz92A2MOIaVANxRiqJaCvtnQxBJN x31fxJPnS9PiuFRYC9NTJFfU5OE1y4M9vqyx11epSrkodwfUmfDLt6g0NmWSGOQjBmWe5S 8scdwFE6ZkySExoSDjyuwjNUS2yFylHaUNzaLWv93p8yZRabEFljYvK5GY0sX8ltpHtx8S VBxtAQBhbKpSh06u0pvs0JSozY2ZRwAzxwO5Kh1HKDnQG7YwUygzk2P6gsuLnvIK0nSRye umEE1+L4Rdk04s+VniGRR1RC5SOEm5iBjVazWDJ0nSLJZuuK3eKgq77WRg4aeg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by bcr: URL: https://cgit.FreeBSD.org/doc/commit/?id=1f9b2d8130303df35e48207632ccbf10ef3a9f5d commit 1f9b2d8130303df35e48207632ccbf10ef3a9f5d Author: Benedict Reuschling AuthorDate: 2022-01-29 14:20:59 +0000 Commit: Benedict Reuschling CommitDate: 2022-01-29 14:20:59 +0000 Fix some typos in the Wine chapter and remove trailing whitespaces. --- .../content/en/books/handbook/wine/_index.adoc | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/documentation/content/en/books/handbook/wine/_index.adoc b/documentation/content/en/books/handbook/wine/_index.adoc index 1dd20c0c35..45c8f88e26 100644 --- a/documentation/content/en/books/handbook/wine/_index.adoc +++ b/documentation/content/en/books/handbook/wine/_index.adoc @@ -158,7 +158,7 @@ While Steam does not offer a native FreeBSD client,there are several options for [[wine-companion-programs]] ==== WINE Companion Programs -In addition to proprietary offerings, other projects have released applications designed to work in tandem with the standard, open source version of WINE. +In addition to proprietary offerings, other projects have released applications designed to work in tandem with the standard, open source version of WINE. The goals for these can range from making installation easier to offering easy ways to get popular software installed. These solutions are covered in greater detail in the later section on <>, and include the following: @@ -256,7 +256,7 @@ Alternately compile the WINE sub-system from source with the following: === Concerns of 32- Versus 64-Bit in WINE Installations Like most software, Windows(R) applications made the upgrade from the older 32-bit architecture to 64 bits. -And most recent software is written for 64-bit operating systems, although modern OSes can sometimes continue to run older 32-bit programs as well. +And most recent software is written for 64-bit operating systems, although modern OSes can sometimes continue to run older 32-bit programs as well. FreeBSD is no different, having had support for 64-bit since the 5.x series. However, using old software no longer supported by default is a common use for emulators, and users commonly turn to WINE to play games and use other programs that do not run properly on modern hardware. @@ -320,7 +320,7 @@ Alternately, supply the full path to the executable to use it in a script, for e After installation graphical shells should be updated with new associations for Windows executable ([.filename]#.EXE#) files. It will now be possible to browse the system using a file manager, and launch the Windows application in the same way as other files and programs (either a single- or double-click, depending on the desktop's settings). -On most desktops, check to make sure this association is correct by right-clicking on the file, and looking for an entry in the context menu to open the file. +On most desktops, check to make sure this association is correct by right-clicking on the file, and looking for an entry in the context menu to open the file. One of the options (hopefully the default one) will be with the *Wine Windows Program Loader*, as shown in the below screenshot: image::wine-run-np++-1.png[] @@ -490,7 +490,7 @@ It also allows entry of (entirely optional) user information, although this is n [[wine-management-guis]] == WINE Management GUIs -While the base install of WINE comes with a GUI configuration tool in winecfg, it is main purpose is just that: strictly configuring an existing WINE prefix. +While the base install of WINE comes with a GUI configuration tool in winecfg, it is main purpose is just that: strictly configuring an existing WINE prefix. There are, however, more advanced applications that will assist in the initial installation of applications as well as optimizing their WINE environments. The below sections include a selection of the most popular. @@ -685,13 +685,13 @@ But the expectation is that only one will be using the physical machine (a deskt More recent consumer versions of Windows(R) have taken some steps to improve the OS in multi-user scenarios. But it is still largely structured around a single-user experience. -Furthermore, the measures the WINE project has taken to create acompatible environment means, unlike FreeBSD applications (including WINE itself), it will resemble this single-user environment. +Furthermore, the measures the WINE project has taken to create a compatible environment means, unlike FreeBSD applications (including WINE itself), it will resemble this single-user environment. So it follows that each user will have to maintain their own set of configurations, which is potentially good. Yet it is advantageous to install applications, particularly large ones like office suites or games, only once. Two examples of reasons to do this are maintenance (software updates need only be applied once) and efficiency in storage (no duplicated files). -There are two strategies to minimze the impact of multiple WINE users in the system. +There are two strategies to minimize the impact of multiple WINE users in the system. [[installing-applications-to-a-common-drivesettings]] === Installing Applications to a Common Drive @@ -727,7 +727,7 @@ Create a new user with the following command (as root), which will step through .... Enter the username (e.g., _windows_) and Full name ("Microsoft Windows"). -Then accept the defaults for the remainder of the questions. Next, install the sudo utlity using binary packages with the following: +Then accept the defaults for the remainder of the questions. Next, install the sudo utility using binary packages with the following: [source,shell] .... @@ -803,7 +803,7 @@ However, multiple installs can be achieved using mechanisms like chroots/jails, [[can-dos-programs-be-run-on-wine]] ==== Can DOS Programs Be Run on WINE? -They can, as "Console User Interface" applications as mentioned eariler in this section. +They can, as "Console User Interface" applications as mentioned earlier in this section. However, there is an arguably better method for running DOS software: DOSBox. On the other hand, there's little reason not to at least try it. Simply create a new prefix, install the software, and if it does not work delete the prefix. @@ -858,7 +858,7 @@ According to https://forums.freebsd.org/threads/make-wine-ui-fonts-look-good.682 ==== Does Having Windows(R) Installed Elsewhere on a System Help WINE Operate? It may, depending on the application being run. -As mentioned in the section describing winecfg, some built-in WINE DLLs and other libraries can be overridden by providing a path to an alternate version. +As mentioned in the section describing winecfg, some built-in WINE DLLs and other libraries can be overridden by providing a path to an alternate version. Provided the Windows(R) partition or drive is mounted to the FreeBSD system and accessible to the user, configuring some of these overrides will use native Windows(R) libraries and may decrease the chance of unexpected behavior. [[application-specific]] @@ -867,7 +867,7 @@ Provided the Windows(R) partition or drive is mounted to the FreeBSD system and [[where-is-the-best-place-to-see-if-application-x-works-on-wine]] ==== Where is the Best Place to see if Application X Works on WINE? -The first stop in determining compatibiliy should be the https://appdb.winehq.org/[WINE AppDB]. +The first stop in determining compatibility should be the https://appdb.winehq.org/[WINE AppDB]. This is a compilation of reports of programs working (or not) on all supported platforms, although (as previously mentioned), solutions for one platform are often applicable to others. [[is-there-anything-that-will-help-games-run-better]]