Ok - great. But I will remember that for future reference. I noticed a number of small textual/grammatical things in the Pharo 5 UI as well, so I will dust of the cobwebs on how to create some some slices and see if I can help in a small way.
Tim > On 29 Nov 2016, at 08:41, Esteban Lorenzano <esteba...@gmail.com> wrote: > > yes, but no need… I already fixed it :) > >> On 29 Nov 2016, at 09:29, p...@highoctane.be <mailto:p...@highoctane.be> >> wrote: >> >> Report them on pharo.fogbugz.com <http://pharo.fogbugz.com/> >> >> http://pharo.org/contribute-report-bug >> <http://pharo.org/contribute-report-bug> >> >> Use Project: Websites as the reference. >> >> Phil >> >> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <tim@testit.works >> <mailto:tim@testit.works>> wrote: >> Hi Guys - how is the best way to report website and text bugs? >> >> As I know the English is not always a first language (and you guys are busy >> writing code anyway) - its up to us native English speakers to chip in where >> we can. >> >> I was pleased to get the notice that on OSX Sierra I need to do something >> extra to get Pharo to work, however the text could be slightly corrected eg. >> (Bolded words changed) >> >> Are you using macOS Sierra? >> Due to changes in security policies of macOS, you will need to put the VM in >> the /Applications folder. >> We are working to fix this temporary inconvenience. >> >> >> Also - the Hello world command line example on the front page doesn’t work >> on a standard Terminal on a Mac (you get an error: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'" >> -bash: !'": event not found >> >> The culprit is of course the “!” Character so a better example might be: >> >> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'" >> Hello WorldStdioStream: 'stdout' >> >> Although, in this case, is it expected that the return string is merged with >> some other output text (e.g. the StdioStream:….?). I think its an impressive >> example, but it just doesn’t quite look right? >> >> >> Tim >> >
