Thank you Damien for reposting my question here and for guiding me here.
Following the Stef's reccomendations, converter is now published as separate
package here: http://ss3.gemstone.com/ss/CP1251TextConverter.html
But I do not get an answer I'm seeking for yet.
I want/seeking the way for this converter to be included in standard Pharo
distribution. Smalltalk has small but consistent Russian community, so it'
looks reasonable, especially taking into account that we have
RussianEnvironment anyway.
Yuri we would prefer to have a strong package maintained outside of Pharo.
Why because we are trying to reduce and remove code from Pharo.
What we can do is to offer you an account to our automatic build server.
Based on it you could load a configuration (ConfigurationOfRussianPharo)
and provide
this image to the people requiring russian support.
It would be good that you evaluate the solution proposed by Sven to
avoid duplication of effort.
Plus, I want to use this simple and small example to understand a process of
including my code in "mainstream" and get understand the possible problems.
Here is the process for enhancement to Pharo
- signing the license agreement (see www.pharo.org)
- opening a bug or enhancement request on fogbugz
https://pharo.fogbugz.com
- proposing changes with tests that get reviewed by the community
For magritte and Glorp you should contact the package maintainer.
Each project on SmalltalkHub has now a public inbox. So I would publish
my changes there
Working on SmallPOS I made a lot of adjusments in "Pharo Core", Magritte and
GLORP, which probably may be useful outside the SmallPOS. So I started a
process of separating this code from SmallPOS package and want to know how
to share it.
Currently it does CP1250, CP1252 and CP1253 among others (including
KOI8R), but not (yet) CP1251.
Sven, abstractly, it will be better to include CP1251. After all, it's
little bit strange to have KOI8R implemented without implementing CP1251.
Second one is widely used - much wider then KOI8R. I was forced to use it as
hardware I use (sticker label printer and cash register) was designed to use
CP1251 at hardware level. As far as it takes no or little efforts I propose
you to add the mentioned encoding.
Good. You see when we do not get confronted with a problem it is
difficult to react
adequately :)
Do you see http://www.squeaksource.com/RussianSupport.html
No, I dont. When I implemented mine one - it was several years ago - I tried
to find one, but failed. Repo you pointing me to was made far before mine,
so it was possible to find it. I don't know why I failed to find it. I may
assume that, probably, I found it but it is not working. You see, it looks
like it designed for Squeak, or, at least, the author do not follow the
template other ByteTextConverters follow. Just a speculation, I do not tried
to load it now.
This is why I suggest:
- publish on SmalltalkHub
- create a configuration with meta data.
- publish it to MetaRepoForPharo30
- your package will be available on
https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/?
soon we will have a public web site catalog.Pharo.org
