Jump to content

Standard Compression Scheme for Unicode: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)

14 November 2023

11 November 2023

9 November 2023

6 March 2023

30 August 2022

17 April 2022

29 March 2022

13 March 2022

11 December 2021

8 December 2021

26 October 2021

23 August 2021

16 May 2021

  • curprev 17:2217:22, 16 May 202177.61.180.106 talk 6,045 bytes +1,331 sources for Reuters + ‘Reuters is believed to use SCSU internally’ makes no sense as a thing to state: they'll use the same technology as everybody else; if an employee is consulting a web page most likely UTF-8, if sending mail maybe even ASCII and if they're running an SQL Server instance it'll use its mix of UTF16LE and SCSU + character encoding or not? the zig-zag + Czyborra's decompressor + MSDN page moved + why compress in the first place + source for general purpose compression undo
  • curprev 13:5613:56, 16 May 202177.61.180.106 talk 4,714 bytes −102 security issues aren't in the compression scheme as such and addressed elsewhere in the article + ‘better’ depends very much on what you measure and in what circumstances (e.g. if you store the file as is, rather than in e.g. a .7z archive, and your metric is file size, SCSU will almost always be ‘better’ than UTF-8) undo

15 May 2021

11 April 2021

28 January 2021

12 January 2021

25 August 2020

23 March 2018

4 August 2017

21 October 2015

22 March 2014

28 February 2014

8 August 2013

23 March 2013

31 January 2013

25 November 2012

20 February 2012

11 November 2010

4 October 2010

20 September 2010

11 May 2010

(newest | oldest) View (newer 50 | ) (20 | 50 | 100 | 250 | 500)