#foswiki 2017-03-30,Thu

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***ChanServ sets mode: +o Lynnwood__ [01:33]
................................................. (idle for 4h1mn)
ChanServ sets mode: +o cdot [05:34]
.......... (idle for 47mn)
ChanServ sets mode: +o MichaelDaum [06:21]
.... (idle for 19mn)
ChanServ sets mode: +o cdot [06:40]
GithubBot[DBIQueryPlugin] cdot pushed 1 new commit to master: https://git.io/vSGbi
DBIQueryPlugin/master 2cdf69c cdot: Item14362: escape curly braces, as required by modern perl
[06:49]
***GithubBot has left [06:49]
FoswikiBothttps://foswiki.org/Tasks/Item14362 [ Item14362: Update perl source to escape curly braces ] [06:49]
.... (idle for 18mn)
GithubBot[DBIQueryPlugin] cdot pushed 1 new commit to master: https://git.io/vSGNQ
DBIQueryPlugin/master 8ca31bb cdot: Item14362: escape curly braces, as required by modern perl
[07:07]
***GithubBot has left [07:07]
GithubBot[ForEachPlugin] cdot pushed 1 new commit to master: https://git.io/vSGAW
ForEachPlugin/master 99c66d1 cdot: Item14362: escape curly braces, as required by modern perl
[07:13]
***GithubBot has left [07:13]
.... (idle for 18mn)
ChanServ sets mode: +o Lynnwood [07:31]
................................................................... (idle for 5h34mn)
ChanServ sets mode: +o gac410 [13:05]
......................................................................... (idle for 6h4mn)
Lynnwoodhey all - I'm working on upgrading an older site and am going through the character conversion process and would appreciate some feedback on what I'm finding. The site encoding was set to iso-8859-1 but, as typical, there were lot of user copy-and-pasting windows charaters into topics. So I ran the convert_charset to generate a report and have lots of entries along these lines: "WARNING: Encoding iso-8859-1 overridden by detected
encoding windows-1252
WARNING: Inconsistent windows-1252 encoding detected in content of..."
so it correctly detected windows-1252 charecters... but then noted that there was inconsistent encording...
[19:09]
gac410Probably the best approach for old sites is to not use detection, but to just set the characterset on the old site to cp-1252.
The detection code is very unreliable due to the complexity of all this.
[19:10]
Lynnwoodright... that was I was going to ask. :-)
Sounds good
[19:10]
gac410If you still get conflicts, then you probably have to investigate and resolve each by hand. [19:11]
Lynnwoodwould it be worthwhile to generate the report again using that setting? [19:11]
gac410Y, you can still use inspect. just force the source charset to be 1252, not 8859 [19:11]
Lynnwood(perhaps it would clean out some of those warning so I could see other issues)
ok
thanks!
[19:11]
gac410yw. [19:12]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)