September 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Which Character Encodings do you want/need in Pharo ?

by kilon alios

Ok this is strange the ISO 8857-7 is available with Chrome as an encoding , I tried it and it turns Greek to weird signs. Actually I tried also several others available for Greek by Chrome and none works apart from the default which is UTF-8 .... Also you can ignore my request as I tried Pharo with True Type fonts with Arial and it can display Greeks just fine. Well done Pharoers , once again Pharo surprises me in a good way :) On Fri, Sep 12, 2014 at 5:16 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 12 Sep 2014, at 16:05, kilon alios <kilon.alios(a)gmail.com> wrote: > > > I am not in any urgent need as I rarely use (like almost never) my > native language in reading or writing when it comes to anything related to > computers, apart from facebook friends. But I would like to see it added to > pharo , its ÎÎ»Î»Î·Î½Î¹ÎºÎ¬ or as you know it "Greek". > > So that would be ISO 8857-9 (http://en.wikipedia.org/wiki/ISO/IEC_8859-7 > - http://unicode.org/Public/MAPPINGS/ISO8859/8859-7.TXT) then, right ? > > Is this nice to have or really necessary (as in used by everybody using > the Greek language) ? > > > I assume the most popular encondings to have would be Chinese and Hindu ? > > I think this something that (native) speakers should help with ;-) > > Remember we have full Unicode Character/String capable classes, as well as > good UTF-8. Those cover all languages, in theory. > > The question comes down to which older encodings are still really > used/necessary today. > > > On Fri, Sep 12, 2014 at 4:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > > Hi, > > > > ZnCharacterEncoder and its subclasses in the package > Zinc-Character-Encoding-Core (a standard part of Pharo) have the following > features: > > > > - proper Unicode Character/String to/from byte(s) encoding/decoding > > - calculation of encoding size per Character/String > > - proper handling of holes in tables with exceptions (strict/lenient) > > - properly backing up one character on a binary stream > > - simple, efficient, documented > > - convenience API > > - optimisations for some encodings > > > > Together, they support the following encodings: > > > > - utf-8 > > - utf-16 (big/little endian, bom detection) > > - null > > - iso-8859-1 (latin-1) > > - iso-8859-2 (latin-2) > > - mac-roman > > - cp1250 > > - cp1252 > > - cp1253 > > - koi8r > > - iso-8859-7 > > - iso-8859-15 > > > > The question is, what other encodings do you want/need ? > > > > There is already a request to add CP1251. > > > > New byte encoders are easy to add, based on the official Unicode > mappings that can be found here: http://unicode.org/Public/MAPPINGS > (these are automagically parsed). > > > > Please help us make Pharo more international friendly. > > > > Sven > > > > > > > > > > >

Sept. 12, 2014

Re: [Pharo-dev] Which Character Encodings do you want/need in Pharo ?

by Sven Van Caekenberghe

On 12 Sep 2014, at 16:05, kilon alios <kilon.alios(a)gmail.com> wrote: > I am not in any urgent need as I rarely use (like almost never) my native language in reading or writing when it comes to anything related to computers, apart from facebook friends. But I would like to see it added to pharo , its ÎÎ»Î»Î·Î½Î¹ÎºÎ¬ or as you know it "Greek". So that would be ISO 8857-9 (http://en.wikipedia.org/wiki/ISO/IEC_8859-7 - http://unicode.org/Public/MAPPINGS/ISO8859/8859-7.TXT) then, right ? Is this nice to have or really necessary (as in used by everybody using the Greek language) ? > I assume the most popular encondings to have would be Chinese and Hindu ? I think this something that (native) speakers should help with ;-) Remember we have full Unicode Character/String capable classes, as well as good UTF-8. Those cover all languages, in theory. The question comes down to which older encodings are still really used/necessary today. > On Fri, Sep 12, 2014 at 4:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > ZnCharacterEncoder and its subclasses in the package Zinc-Character-Encoding-Core (a standard part of Pharo) have the following features: > > - proper Unicode Character/String to/from byte(s) encoding/decoding > - calculation of encoding size per Character/String > - proper handling of holes in tables with exceptions (strict/lenient) > - properly backing up one character on a binary stream > - simple, efficient, documented > - convenience API > - optimisations for some encodings > > Together, they support the following encodings: > > - utf-8 > - utf-16 (big/little endian, bom detection) > - null > - iso-8859-1 (latin-1) > - iso-8859-2 (latin-2) > - mac-roman > - cp1250 > - cp1252 > - cp1253 > - koi8r > - iso-8859-7 > - iso-8859-15 > > The question is, what other encodings do you want/need ? > > There is already a request to add CP1251. > > New byte encoders are easy to add, based on the official Unicode mappings that can be found here: http://unicode.org/Public/MAPPINGS (these are automagically parsed). > > Please help us make Pharo more international friendly. > > Sven > > > >

Sept. 12, 2014

Re: [Pharo-dev] Which Character Encodings do you want/need in Pharo ?

by kilon alios

I am not in any urgent need as I rarely use (like almost never) my native language in reading or writing when it comes to anything related to computers, apart from facebook friends. But I would like to see it added to pharo , its ÎÎ»Î»Î·Î½Î¹ÎºÎ¬ or as you know it "Greek". I assume the most popular encondings to have would be Chinese and Hindu ? On Fri, Sep 12, 2014 at 4:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > ZnCharacterEncoder and its subclasses in the package > Zinc-Character-Encoding-Core (a standard part of Pharo) have the following > features: > > - proper Unicode Character/String to/from byte(s) encoding/decoding > - calculation of encoding size per Character/String > - proper handling of holes in tables with exceptions (strict/lenient) > - properly backing up one character on a binary stream > - simple, efficient, documented > - convenience API > - optimisations for some encodings > > Together, they support the following encodings: > > - utf-8 > - utf-16 (big/little endian, bom detection) > - null > - iso-8859-1 (latin-1) > - iso-8859-2 (latin-2) > - mac-roman > - cp1250 > - cp1252 > - cp1253 > - koi8r > - iso-8859-7 > - iso-8859-15 > > The question is, what other encodings do you want/need ? > > There is already a request to add CP1251. > > New byte encoders are easy to add, based on the official Unicode mappings > that can be found here: http://unicode.org/Public/MAPPINGS (these are > automagically parsed). > > Please help us make Pharo more international friendly. > > Sven > > > >

Sept. 12, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40222 Home: https://github.com/pharo-project/pharo-core

Sept. 12, 2014

[pharo-project/pharo-core] ffde2a: 40222

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ffde2ab569aa9227b81ea1ed2b180099aad86594 https://github.com/pharo-project/pharo-core/commit/ffde2ab569aa9227b81ea1ed… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-12 (Fri, 12 Sep 2014) Changed paths: M NewValueHolder.package/extension/Object/instance/asReactiveVariable.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script222.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40222.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/AbstractWidgetModel.class/instance/initialization/initialize.st M Spec-Core.package/ButtonModel.class/instance/initialization/initialize.st M Spec-Core.package/CheckBoxModel.class/instance/initialization/initialize.st M Spec-Core.package/ComposableModel.class/instance/initialization/initialize.st M Spec-Core.package/DialogWindowModel.class/instance/initialize/initialize.st M Spec-Core.package/DiffModel.class/instance/initialize/initialize.st M Spec-Core.package/DropListModel.class/instance/initialization/initialize.st M Spec-Core.package/DynamicComposableModel.class/instance/initialization/initialize.st M Spec-Core.package/IconListModel.class/instance/initialization/initialize.st M Spec-Core.package/ImageModel.class/instance/initialization/initialize.st M Spec-Core.package/LabelModel.class/instance/initialization/initialize.st M Spec-Core.package/ListModel.class/instance/initialization/initialize.st M Spec-Core.package/MenuGroupModel.class/instance/initialize/initialize.st M Spec-Core.package/MenuItemModel.class/instance/initialize/initialize.st M Spec-Core.package/MenuModel.class/instance/initialize/initialize.st M Spec-Core.package/NewListModel.class/instance/initialize/initialize.st M Spec-Core.package/OkCancelToolbar.class/instance/initialization/initialize.st M Spec-Core.package/OkToolbar.class/instance/initialization/initialize.st M Spec-Core.package/RadioButtonModel.class/instance/initialization/initialize.st M Spec-Core.package/SliderModel.class/instance/initialization/initialize.st M Spec-Core.package/TabManagerModel.class/instance/initialize/initialize.st M Spec-Core.package/TabModel.class/instance/initialize/initialize.st M Spec-Core.package/TextInputFieldModel.class/instance/initialization/initialize.st M Spec-Core.package/TextModel.class/instance/initialization/initialize.st M Spec-Core.package/TreeColumnModel.class/instance/initialization/initialize.st M Spec-Core.package/TreeModel.class/instance/initialization/initialize.st M Spec-Core.package/TreeNodeModel.class/instance/initialize/initialize.st M Spec-Core.package/WindowModel.class/instance/initialization/initialize.st M Spec-Debugger.package/SpecDebugActionButton.class/instance/initialization/initialize.st M Spec-Debugger.package/SpecDebugger.class/instance/initialization/initialize.st M Spec-Debugger.package/SpecDebuggerDynamicToolbar.class/instance/initialization/initialize.st M Spec-Debugger.package/SpecDebuggerStack.class/instance/initialization/initialize.st M Spec-Debugger.package/SpecPreDebugWindow.class/instance/initialization/initialize.st M Spec-Examples.package/DynamicSpecExample.class/instance/initialization/initialize.st M Spec-Inspector.package/EyeAbstractInspector.class/instance/initialization/initialize.st M Spec-Inspector.package/InspectorNavigator.class/instance/initialization/initialize.st M Spec-MorphicAdapters.package/MorphicWindowAdapter.class/instance/initialize/initialize.st M Spec-PolyWidgets.package/DateModel.class/instance/initialization/initialize.st M Spec-PolyWidgets.package/EditableList.class/instance/initialization/initialize.st M Spec-PolyWidgets.package/InputWidget.class/instance/initialization/initialize.st M Spec-PolyWidgets.package/MethodToolbar.class/instance/initialization/initialize.st M Spec-PolyWidgets.package/PickListModel.class/instance/initialization/initialize.st M Spec-PolyWidgets.package/SearchableTree.class/instance/initialization/initialize.st M Spec-Tools.package/AbstractApiSetter.class/instance/initialization/initialize.st M Spec-Tools.package/BlockEditor.class/instance/initialization/initialize.st M Spec-Tools.package/ColorEditor.class/instance/initialization/initialize.st M Spec-Tools.package/IntegerEditor.class/instance/initialization/initialize.st M Spec-Tools.package/MessageBrowser.class/instance/initialization/initialize.st M Spec-Tools.package/MessageBrowser.class/instance/initialization/initializeWidgets.st M Spec-Tools.package/STEditor.class/instance/initialization/initialize.st M Spec-Tools.package/SubwidgetItem.class/instance/initialization/initialize.st M Spec-Tools.package/WidgetSetter.class/instance/initialization/initialize.st M Spec-Tools.package/WorkingCopyToolBar.class/instance/initialization/initialize.st Log Message: ----------- 40222 13971 clean asReactiveVariable -> asValueHolder https://pharo.fogbugz.com/f/cases/13971 http://files.pharo.org/image/40/40222.zip

Sept. 12, 2014

Which Character Encodings do you want/need in Pharo ?

by Sven Van Caekenberghe

Hi, ZnCharacterEncoder and its subclasses in the package Zinc-Character-Encoding-Core (a standard part of Pharo) have the following features: - proper Unicode Character/String to/from byte(s) encoding/decoding - calculation of encoding size per Character/String - proper handling of holes in tables with exceptions (strict/lenient) - properly backing up one character on a binary stream - simple, efficient, documented - convenience API - optimisations for some encodings Together, they support the following encodings: - utf-8 - utf-16 (big/little endian, bom detection) - null - iso-8859-1 (latin-1) - iso-8859-2 (latin-2) - mac-roman - cp1250 - cp1252 - cp1253 - koi8r - iso-8859-7 - iso-8859-15 The question is, what other encodings do you want/need ? There is already a request to add CP1251. New byte encoders are easy to add, based on the official Unicode mappings that can be found here: http://unicode.org/Public/MAPPINGS (these are automagically parsed). Please help us make Pharo more international friendly. Sven

Sept. 12, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40221 Home: https://github.com/pharo-project/pharo-core

Sept. 12, 2014

[pharo-project/pharo-core] b2889c: 40221

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: b2889c176180755954e866ceca6380fd90577271 https://github.com/pharo-project/pharo-core/commit/b2889c176180755954e866ce… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-12 (Fri, 12 Sep 2014) Changed paths: R AsmJit-Tests.package/AJx86AssemblerTests.class/instance/tests/testRegistersOf_.st A Collections-Streams.package/LimitedWriteStream.class/instance/accessing/nextPutAll_.st R Collections-Streams.package/LimitedWriteStream.class/instance/as yet unclassified/nextPutAll_.st R Collections-Streams.package/LimitedWriteStream.class/instance/as yet unclassified/pastEndPut_.st A Collections-Streams.package/LimitedWriteStream.class/instance/private/pastEndPut_.st M Collections-Streams.package/LimitingLineStreamWrapper.class/class/examples/example1.st M Collections-Streams.package/LimitingLineStreamWrapper.class/class/examples/example2.st M Collections-Streams.package/MultiByteBinaryOrTextStream.class/instance/private basic/basicNextInto_.st M Collections-Streams.package/MultiByteBinaryOrTextStream.class/instance/private basic/basicNext_into_.st M Collections-Streams.package/MultiByteBinaryOrTextStream.class/instance/private basic/basicPosition.st M Collections-Streams.package/MultiByteBinaryOrTextStream.class/instance/private basic/basicPosition_.st M Collections-Streams.package/PositionableStream.class/instance/data get%2Fput/int16_.st M Collections-Streams.package/PositionableStream.class/instance/data get%2Fput/int32_.st M Collections-Streams.package/PositionableStream.class/instance/positioning/untilEndWithFork_displayingProgress_.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/binary.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/contents.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/isBinary.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/next.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/nextPut_.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/next_.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/next_into_startingAt_.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/readInto_startingAt_count_.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/text.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/accessing/upToEnd.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/asBinaryOrTextStream.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/ascii.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/binary.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/contents.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/isBinary.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/next.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/nextPut_.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/next_.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/next_into_startingAt_.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/padToEndWith_.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/readInto_startingAt_count_.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/reset.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/setFileTypeToObject.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/text.st R Collections-Streams.package/RWBinaryOrTextStream.class/instance/as yet unclassified/upToEnd.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/converting/asBinaryOrTextStream.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/converting/ascii.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/positioning/reset.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/properties-setting/setFileTypeToObject.st A Collections-Streams.package/RWBinaryOrTextStream.class/instance/public/padToEndWith_.st A Collections-Streams.package/TextStream.class/instance/accessing/nextPutAll_.st R Collections-Streams.package/TextStream.class/instance/as yet unclassified/nextPutAll_.st R Collections-Streams.package/TextStream.class/instance/as yet unclassified/withAttribute_do_.st R Collections-Streams.package/TextStream.class/instance/as yet unclassified/withAttributes_do_.st A Collections-Streams.package/TextStream.class/instance/private/withAttribute_do_.st A Collections-Streams.package/TextStream.class/instance/private/withAttributes_do_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-method/privateDeprecateMethodFor_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script221.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40221.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40221 13997 Small code critic clean of Collections-Streams https://pharo.fogbugz.com/f/cases/13997 13992 NautilusRefactoring stores into method argument https://pharo.fogbugz.com/f/cases/13992 13994 AJx86AssemblerTests>>testRegistersOf:(asm is shadowed) https://pharo.fogbugz.com/f/cases/13994 http://files.pharo.org/image/40/40221.zip

Sept. 12, 2014

Re: [Pharo-dev] fosdem 2015

by phil＠highoctane.be

I am living close to the venue, tell me if I can help. Phil On Fri, Sep 12, 2014 at 1:05 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Santiage wrote: > >Hi people!, Will we have room in next FOSDEM? > > I will put out a proposal for a devroom, yes. That is no guarantee > that we will get one, the amount of space is limited. > > Stephan > >

Sept. 12, 2014

Re: [Pharo-dev] fosdem 2015

by Santiago Bragagnolo

Great, keep us updated :) If i can help, tell me. 2014-09-12 13:05 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > Santiage wrote: > >Hi people!, Will we have room in next FOSDEM? > > I will put out a proposal for a devroom, yes. That is no guarantee > that we will get one, the amount of space is limited. > > Stephan > >

Sept. 12, 2014