git: 1f9b2d8130 - main - Fix some typos in the Wine chapter and remove trailing whitespaces.
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 29 Jan 2022 14:21:51 UTC
The branch main has been updated by bcr:
URL: https://cgit.FreeBSD.org/doc/commit/?id=1f9b2d8130303df35e48207632ccbf10ef3a9f5d
commit 1f9b2d8130303df35e48207632ccbf10ef3a9f5d
Author: Benedict Reuschling <bcr@FreeBSD.org>
AuthorDate: 2022-01-29 14:20:59 +0000
Commit: Benedict Reuschling <bcr@FreeBSD.org>
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 <<wine-management-guis,GUI frontends>>, 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]]