From 517152276506f3c62bba8d5b647a3c05e9f51cfc Mon Sep 17 00:00:00 2001 From: Titouan Vervack Date: Wed, 4 Dec 2024 11:01:10 +0100 Subject: [PATCH 2/4] Cleanup internal HTML --- pages/FAQ/FAQ-Is-SWT-platform-specific?.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/FAQ/FAQ-Is-SWT-platform-specific?.md b/pages/FAQ/FAQ-Is-SWT-platform-specific?.md index 715a5ee..cc8f669 100644 --- a/pages/FAQ/FAQ-Is-SWT-platform-specific?.md +++ b/pages/FAQ/FAQ-Is-SWT-platform-specific?.md @@ -6,7 +6,7 @@ Eclipse to a new platform consists of porting SWT to the new platform. The SWT APIs, on the other hand, are largely platform independent. To be more specific, all classes in the SWT packages not marked -internal are guaranteed to be binary compatible across all +_internal_ are guaranteed to be binary compatible across all platforms supported by SWT. Thus, if you write a Java application on SWT, you can compile it into JARs on one platform to run on all platforms supported by SWT without linkage errors. Thus, applications @@ -18,7 +18,7 @@ names end with the windowing system name. For example, the package Yet another angle on the platform-specific question is to ask whether the behavior of SWT is platform specific. You may have noticed the careful wording of the binary-compatibility promise, which guarantees -only that you will have no linkage errors when changing to +only that you will have no _linkage_ errors when changing to another platform. SWT does not promise consistent behavior across platforms. On each platform, SWT instead strives for behavior that is consistent with other applications on that platform. Thus, an SWT -- 2.47.0