Fix trailing whitespace in .cpp, .h, and .idl files (ex. Source/core)

Source/wtf/text/TextEncoding.cpp

Index: Source/wtf/text/TextEncoding.cpp
diff --git a/Source/wtf/text/TextEncoding.cpp b/Source/wtf/text/TextEncoding.cpp
index eb5ded6bc3dcf4775b09f843621f215997c0cf52..6ee67c71bd2a1e6cdb60c2fa626cd2098b75265e 100644
--- a/Source/wtf/text/TextEncoding.cpp
+++ b/Source/wtf/text/TextEncoding.cpp
@@ -22,7 +22,7 @@
  * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
  * OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
  * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
- * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 
+ * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */
 
 #include "config.h"
@@ -125,10 +125,10 @@ const char* TextEncoding::domName() const
     if (noExtendedTextEncodingNameUsed())
         return m_name;
 
-    // We treat EUC-KR as windows-949 (its superset), but need to expose 
+    // We treat EUC-KR as windows-949 (its superset), but need to expose
     // the name 'EUC-KR' because the name 'windows-949' is not recognized by
     // most Korean web servers even though they do use the encoding
-    // 'windows-949' with the name 'EUC-KR'. 
+    // 'windows-949' with the name 'EUC-KR'.
     // FIXME: This is not thread-safe. At the moment, this function is
     // only accessed in a single thread, but eventually has to be made
     // thread-safe along with usesVisualOrdering().
@@ -182,11 +182,11 @@ const TextEncoding& TextEncoding::closestByteBasedEquivalent() const
 {
     if (isNonByteBasedEncoding())
         return UTF8Encoding();
-    return *this; 
+    return *this;
 }
 
-// HTML5 specifies that UTF-8 be used in form submission when a form is 
-// is a part of a document in UTF-16 probably because UTF-16 is not a 
+// HTML5 specifies that UTF-8 be used in form submission when a form is
+// is a part of a document in UTF-16 probably because UTF-16 is not a
 // byte-based encoding and can contain 0x00. By extension, the same
 // should be done for UTF-32. In case of UTF-7, it is a byte-based encoding,
 // but it's fraught with problems and we'd rather steer clear of it.