[website 4/4] wwn: Use https for wiki.winehq.org
André Hentschel
nerv at dawncrow.de
Wed Jan 20 13:12:46 CST 2016
---
wwn/en/wn20050506_273.xml | 8 ++++----
wwn/en/wn20050513_274.xml | 6 +++---
wwn/en/wn20050520_275.xml | 12 ++++++------
wwn/en/wn20050527_276.xml | 2 +-
wwn/en/wn20050603_277.xml | 6 +++---
wwn/en/wn20050610_278.xml | 4 ++--
wwn/en/wn20050617_279.xml | 2 +-
wwn/en/wn20050624_280.xml | 2 +-
wwn/en/wn20050715_283.xml | 2 +-
wwn/en/wn20050722_284.xml | 2 +-
wwn/en/wn20050729_285.xml | 6 +++---
wwn/en/wn20050805_286.xml | 2 +-
wwn/en/wn20050812_287.xml | 6 +++---
wwn/en/wn20051007_293.xml | 8 ++++----
wwn/en/wn20051025_296.xml | 2 +-
wwn/en/wn20051202_300.xml | 4 ++--
wwn/en/wn20060122_303.xml | 8 ++++----
wwn/en/wn20060210_305.xml | 2 +-
wwn/en/wn20060305_307.xml | 4 ++--
wwn/en/wn20060428_312.xml | 10 +++++-----
wwn/en/wn20060515_313.xml | 4 ++--
wwn/en/wn20060605_315.xml | 14 +++++++-------
wwn/en/wn20060611_316.xml | 4 ++--
wwn/en/wn20060810_319.xml | 4 ++--
wwn/en/wn20070216_321.xml | 4 ++--
wwn/en/wn20070219_322.xml | 6 +++---
wwn/en/wn20070319_326.xml | 8 ++++----
wwn/en/wn20070330_327.xml | 16 ++++++++--------
wwn/en/wn20070410_328.xml | 4 ++--
wwn/en/wn20070416_329.xml | 14 +++++++-------
wwn/en/wn20071203_333.xml | 2 +-
wwn/en/wn20071210_334.xml | 4 ++--
wwn/en/wn20080114_339.xml | 2 +-
wwn/en/wn20080121_340.xml | 2 +-
wwn/en/wn20080224_341.xml | 20 ++++++++++----------
wwn/en/wn20080304_342.xml | 6 +++---
wwn/en/wn20080317_343.xml | 6 +++---
wwn/en/wn20080331_344.xml | 4 ++--
wwn/en/wn20080415_345.xml | 2 +-
wwn/en/wn20080428_346.xml | 2 +-
wwn/en/wn20080527_347.xml | 6 +++---
wwn/en/wn20080714_349.xml | 2 +-
wwn/en/wn20080922_352.xml | 4 ++--
wwn/en/wn20090109_355.xml | 4 ++--
wwn/en/wn20090204_356.xml | 4 ++--
wwn/en/wn20090603_358.xml | 2 +-
wwn/en/wn20090913_359.xml | 2 +-
wwn/en/wn20090921_360.xml | 6 +++---
wwn/en/wn20140214_363.xml | 4 ++--
wwn/en/wn20140303_364.xml | 10 +++++-----
wwn/en/wn20140314_365.xml | 10 +++++-----
wwn/en/wn20140328_366.xml | 14 +++++++-------
wwn/en/wn20150607_392.xml | 2 +-
wwn/en/wn20150914_398.xml | 4 ++--
wwn/en/wn20150924_399.xml | 4 ++--
wwn/en/wn20151004_400.xml | 4 ++--
56 files changed, 154 insertions(+), 154 deletions(-)
diff --git a/wwn/en/wn20050506_273.xml b/wwn/en/wn20050506_273.xml
index 16814ce..66b635a 100644
--- a/wwn/en/wn20050506_273.xml
+++ b/wwn/en/wn20050506_273.xml
@@ -220,8 +220,8 @@ enjoy.
I set up a page with various video and presentation sites at
<ul>
-<a href="http://wiki.winehq.org/WineConf">
-http://wiki.winehq.org/WineConf</a></ul></p><p>
+<a href="https://wiki.winehq.org/WineConf">
+https://wiki.winehq.org/WineConf</a></ul></p><p>
Feel free to add further stuff there!</p></quote>
@@ -253,7 +253,7 @@ this might help:</p>
>
<topic>WineHQ</topic>
<p>Wine has it's own wiki now! The
-<a href="http://wiki.winehq.org">Wine Wiki</a> was put together by
+<a href="https://wiki.winehq.org">Wine Wiki</a> was put together by
Dimi Paun and announced at WineConf. We've discussed for a while
it would be nice to have one, but for various reasons we haven't
wanted to maintain it on WineHQ. (By "we" I mean Newman.) However,
@@ -290,7 +290,7 @@ are most welcome.
</p></quote>
<p>Mike Hearn told everyone he wrote up a page about the
-<a href="http://wiki.winehq.org/InstallShield">inner
+<a href="https://wiki.winehq.org/InstallShield">inner
workings of InstallShield</a> and put it on the wiki.</p>
</section>
diff --git a/wwn/en/wn20050513_274.xml b/wwn/en/wn20050513_274.xml
index 8f9fb2e..1c01a49 100644
--- a/wwn/en/wn20050513_274.xml
+++ b/wwn/en/wn20050513_274.xml
@@ -291,7 +291,7 @@ translation shortly.
startdate="05/10/2005"
>
<topic>Debugging</topic>
-<p>The new <a href="http://wiki.winehq.org">Wine Wiki</a> saw more
+<p>The new <a href="https://wiki.winehq.org">Wine Wiki</a> saw more
new material added this week. Various developers, including Alexandre,
put up to do lists. Mike Hearn announced a new page:</p>
<quote who="Mike Hearn"><p>
@@ -300,8 +300,8 @@ put up to do lists. Mike Hearn announced a new page:</p>
I've added the first of what will hopefully become many debugging
tutorials to the wiki:
<ul>
- <a href="http://wiki.winehq.com/DebuggingTutorials">
- http://wiki.winehq.com/DebuggingTutorials</a></ul>
+ <a href="https://wiki.winehq.com/DebuggingTutorials">
+ https://wiki.winehq.com/DebuggingTutorials</a></ul>
</p><p>
Sometimes fixing Wine can be a bit hard to get into. Hopefully these short
"show me" guides will give people a taste for what it involves and help
diff --git a/wwn/en/wn20050520_275.xml b/wwn/en/wn20050520_275.xml
index 1d37a9a..4149459 100644
--- a/wwn/en/wn20050520_275.xml
+++ b/wwn/en/wn20050520_275.xml
@@ -152,8 +152,8 @@ he gave a pointer to a document on the wiki he's been updating:</p>
<quote who="Maarten Lankhorst"><p>
Status: Nearly complete, need testers.
<ul>
-<a href="http://wiki.winehq.org/MSN_Messenger_webcam_support">
-http://wiki.winehq.org/MSN_Messenger_webcam_support</a></ul>
+<a href="https://wiki.winehq.org/MSN_Messenger_webcam_support">
+https://wiki.winehq.org/MSN_Messenger_webcam_support</a></ul>
</p><p>
You need the native quartz dll, which gets installed with internet
explorer, as the builtin quartz doesn't work properly when changing
@@ -292,19 +292,19 @@ If someone could spend some time updating those scripts we'd appreciate it.
enddate="05/19/2005"
>
<topic>WineHQ</topic>
-<p>The <a href="http://wiki.winehq.org">Wine Wiki</a> has really
+<p>The <a href="https://wiki.winehq.org">Wine Wiki</a> has really
taken off. Lots of people have added info over the past few weeks.
A bunch of interesting docs appeared, many of which are working
drafts of areas people are looking into. Check out the
-<a href="http://wiki.winehq.org/RecentChanges">RecentChanges</a>
+<a href="https://wiki.winehq.org/RecentChanges">RecentChanges</a>
to see the activity going on. Mike Hearn posted
another debugging doc and asked on wine-devel:</p>
<quote who="Mike Hearn"><p>
This time, it's how to debug PE Explorer hanging when you double click on
a DLL in the file open dialog (fixed in CVS).
<ul>
- <a href="http://wiki.winehq.com/Debugging_the_PE_Explorer_file_open_dialog">
- http://wiki.winehq.com/Debugging_the_PE_Explorer_file_open_dialog</a></ul>
+ <a href="https://wiki.winehq.com/Debugging_the_PE_Explorer_file_open_dialog">
+ https://wiki.winehq.com/Debugging_the_PE_Explorer_file_open_dialog</a></ul>
</p><p>
Newbie developers, I crave your feedback. Are these actually useful or am
I wasting my time?</p></quote>
diff --git a/wwn/en/wn20050527_276.xml b/wwn/en/wn20050527_276.xml
index 62cba9d..0793b5a 100644
--- a/wwn/en/wn20050527_276.xml
+++ b/wwn/en/wn20050527_276.xml
@@ -244,7 +244,7 @@ been doing lately concering some new idea not especially related to
WINE.
</p><p>
To quote myself from
-<a href="http://wiki.winehq.org/UnalignedMmap">http://wiki.winehq.org/UnalignedMmap</a>:
+<a href="https://wiki.winehq.org/UnalignedMmap">https://wiki.winehq.org/UnalignedMmap</a>:
</p><p>
Large majority of PE executables have sections that are page-aligned in
diff --git a/wwn/en/wn20050603_277.xml b/wwn/en/wn20050603_277.xml
index 31068fb..134627b 100644
--- a/wwn/en/wn20050603_277.xml
+++ b/wwn/en/wn20050603_277.xml
@@ -98,7 +98,7 @@ Its main goal is to hate budgeting. It also serves to inform you of what's going
<section
title="News: Summer of Code, Linux Mag article"
subject="News"
- archive="http://wiki.winehq.org/SummerOfCode"
+ archive="https://wiki.winehq.org/SummerOfCode"
posts="2"
startdate="05/28/2005"
enddate="06/03/2005"
@@ -123,7 +123,7 @@ details and eligibility requirements. </p>
<p> For anyone wanting to be involved, we've put together some resources
to help you figure out what to work on. There's no shortage of projects,
so check out the
-<a href="http://wiki.winehq.org/SummerOfCode">SummerOfCode wiki page</a>
+<a href="https://wiki.winehq.org/SummerOfCode">SummerOfCode wiki page</a>
and fill out
<a href="http://code.google.com/soc_application.html">an application</a>.
Submissions are due by June 14th. The Wine team is really looking forward to
@@ -474,6 +474,6 @@ by September 1st.
<p>It touched off a flurry of emails and ideas. Even more was
discussed on IRC. The end result was most of the ideas listed
-on the <a href="http://wiki.winehq.org/SummerOfCode">wiki page</a>.
+on the <a href="https://wiki.winehq.org/SummerOfCode">wiki page</a>.
</p>
</section></kc>
diff --git a/wwn/en/wn20050610_278.xml b/wwn/en/wn20050610_278.xml
index 9954198..e038461 100644
--- a/wwn/en/wn20050610_278.xml
+++ b/wwn/en/wn20050610_278.xml
@@ -145,7 +145,7 @@ them are given.
<p>The AppDB has seen even more improvements in the past few months.
We've had a lot of bug fixes, fuzzy searching support added, category
and application sorting by name, etc. As part of the
-<a href="http://wiki.winehq.org/SummerOfCode">Summer of Code</a>
+<a href="https://wiki.winehq.org/SummerOfCode">Summer of Code</a>
program, Ed Mack asked last week if there was some work that could
be done on the website. Chris Morgan thought it would be really
helpful and replied with some ideas:</p>
@@ -361,7 +361,7 @@ to determine if you got the NT4 structure or the win2k one.</quote>
>
<topic>Project Management</topic>
<p>Alexandre announced a committee had been set up to review submissions
-to Google's <a href="http://wiki.winehq.org/SummerOfCode">Summer of Code</a>:
+to Google's <a href="https://wiki.winehq.org/SummerOfCode">Summer of Code</a>:
</p><quote who="Alexandre Julliard"><p>
Just to let people know, we have now organized an "official" committee
composed of Jeremy, Dimi, Lionel, Dan Kegel and myself. We'll be
diff --git a/wwn/en/wn20050617_279.xml b/wwn/en/wn20050617_279.xml
index baac933..e99390b 100644
--- a/wwn/en/wn20050617_279.xml
+++ b/wwn/en/wn20050617_279.xml
@@ -280,7 +280,7 @@ up anything.
</p><p>
For a complete update on the AppDB to-do list, head over to the
wiki and look at
-<a href="http://wiki.winehq.org/AppdbInfo">http://wiki.winehq.org/AppdbInfo</a>.
+<a href="https://wiki.winehq.org/AppdbInfo">https://wiki.winehq.org/AppdbInfo</a>.
</p>
</section>
<section
diff --git a/wwn/en/wn20050624_280.xml b/wwn/en/wn20050624_280.xml
index 521c20c..f5e335c 100644
--- a/wwn/en/wn20050624_280.xml
+++ b/wwn/en/wn20050624_280.xml
@@ -698,6 +698,6 @@ tablets and using a word processor).
</p><p>
For anybody who is interested in moving their own Wine development to
Subversion and SVK, there is a page on the Wiki describing what to do at
-<a href="http://wiki.winehq.com/SVK">http://wiki.winehq.com/SVK</a>.
+<a href="https://wiki.winehq.com/SVK">https://wiki.winehq.com/SVK</a>.
</p></quote>
</section></kc>
diff --git a/wwn/en/wn20050715_283.xml b/wwn/en/wn20050715_283.xml
index 949f2b5..9ef3a59 100644
--- a/wwn/en/wn20050715_283.xml
+++ b/wwn/en/wn20050715_283.xml
@@ -199,7 +199,7 @@ make it safe to), the only other alternative is a shared locking server
their suggestion.</quote>
</p>
<p>After a little more discussion, Rob updated the
-<a href="http://wiki.winehq.org/FileLocking">FileLocking wiki page</a>
+<a href="https://wiki.winehq.org/FileLocking">FileLocking wiki page</a>
with some of the info. Vitaly Lipatov wanted some input about having
one wineserver synchronize locks:</p>
<quote who="Vitaly Lipatov"><p>
diff --git a/wwn/en/wn20050722_284.xml b/wwn/en/wn20050722_284.xml
index e01b3f5..de4d681 100644
--- a/wwn/en/wn20050722_284.xml
+++ b/wwn/en/wn20050722_284.xml
@@ -253,7 +253,7 @@ project if anyone wants to take a look at it before I start submitting
patches; just reply and I'll send it to you. For more information on
what's left TODO with the project, check out my wiki page:
-<ul><a href="http://wiki.winehq.org/JamesHawkins">
+<ul><a href="https://wiki.winehq.org/JamesHawkins">
wiki.winehq.org/JamesHawkins</a></ul></p></quote>
</section>
<section
diff --git a/wwn/en/wn20050729_285.xml b/wwn/en/wn20050729_285.xml
index 8de114f..f49cf8d 100644
--- a/wwn/en/wn20050729_285.xml
+++ b/wwn/en/wn20050729_285.xml
@@ -124,7 +124,7 @@ us, Jacek Caban has been working for several months on implementing
this DLL. Basically it's the web browser behind Internet Explorer.
Jacek has put together a pretty good description of everything on
the wiki under
-<a href="http://wiki.winehq.org/MozillaIntegration">MozillaIntegration</a>.
+<a href="https://wiki.winehq.org/MozillaIntegration">MozillaIntegration</a>.
Jacek posted a large patch this week that got it closer to being a
reality and explained how it was implemented:</p>
<quote who="Jacek Caban"><p>
@@ -302,8 +302,8 @@ looking at the PID side of things.</quote></p>
I put the Benchmark results that I posted to wine-devel back in April
on the Wiki.
-<a href="http://wiki.winehq.org/BenchMark">
-http://wiki.winehq.org/BenchMark</a></p></quote>
+<a href="https://wiki.winehq.org/BenchMark">
+https://wiki.winehq.org/BenchMark</a></p></quote>
<p>A long discussion then ensued about the format of the results.
What you'll see if you go to the page now is the result of a bunch of
diff --git a/wwn/en/wn20050805_286.xml b/wwn/en/wn20050805_286.xml
index c426702..7a26eae 100644
--- a/wwn/en/wn20050805_286.xml
+++ b/wwn/en/wn20050805_286.xml
@@ -119,7 +119,7 @@ Allow maintainers to process submitted screenshots and application
versions for applications they maintain and supermaintain.</ul>
</p></quote>
-<p>The <a href="http://wiki.winehq.org/AppdbInfo">AppdbInfo</a> page
+<p>The <a href="https://wiki.winehq.org/AppdbInfo">AppdbInfo</a> page
on the wiki was updated this week as well. If you like to hack on
PHP, you might be interested in looking at the to-do list.
</p>
diff --git a/wwn/en/wn20050812_287.xml b/wwn/en/wn20050812_287.xml
index 238300e..a5f446e 100644
--- a/wwn/en/wn20050812_287.xml
+++ b/wwn/en/wn20050812_287.xml
@@ -135,7 +135,7 @@ see some improvements in usability along the way. </p>
<section
title="Summer of Code Projects"
subject="Summer of Code Projects"
- archive="http://wiki.winehq.org/SummerOfCode"
+ archive="https://wiki.winehq.org/SummerOfCode"
posts="0"
startdate="08/12/2005"
>
@@ -155,7 +155,7 @@ it appears one has gone MIA. So that leaves us with five:
Gecko rendering engine. We've covered this quite a bit over the past
few months, including a status update two weeks ago in
<a href="//www.winehq.org/wwn/285#MSHTML%20Update">WWN #285</a>.
-The <a href="http://wiki.winehq.org/MozillaIntegration">MozillaIntegration</a>
+The <a href="https://wiki.winehq.org/MozillaIntegration">MozillaIntegration</a>
page has more info. Mike McCormack is mentoring this project.
</li>
<li>Theming support being tacked by Frank Richter, alluded to in Alexandre's
@@ -173,7 +173,7 @@ Daniel is behind that work and there's even more stuff to come.
Lionel Ulmer is mentoring this project. </li>
<li>Now we get into two projects we haven't really discussed.
-<a href="http://wiki.winehq.org/KaiBlin">Kai Blin</a> is just starting
+<a href="https://wiki.winehq.org/KaiBlin">Kai Blin</a> is just starting
to post patches to get authentication working in Wine. His wiki page,
referenced in that link, contains a good project roadmap. There's a
lot of code to wrap your head around and it sounds like he's getting
diff --git a/wwn/en/wn20051007_293.xml b/wwn/en/wn20051007_293.xml
index a5f7374..cd21af9 100644
--- a/wwn/en/wn20051007_293.xml
+++ b/wwn/en/wn20051007_293.xml
@@ -230,8 +230,8 @@ wrote in to give a status update on what still needs to be tackled:</p>
As Dimi suggested, I'm writing here a summary of my
SoC project. I was working on MSHTML implementation.
More about what is MSHTML is on the wiki:
-<a href="http://wiki.winehq.org/MozillaIntegration">
-http://wiki.winehq.org/MozillaIntegration</a>
+<a href="https://wiki.winehq.org/MozillaIntegration">
+https://wiki.winehq.org/MozillaIntegration</a>
so I won't rewrite it here.</p><p>
MSHTML generally works as HTML is displayed, but
@@ -275,8 +275,8 @@ and in most apps HTML pages should work out of the box.
<p>Dimi Paun asked Jacek to update the wiki page to include a
to do list. Jacek created some new pages for that, including
-<a href="http://wiki.winehq.org/MsHtml">MsHtml</a> and
-<a href="http://wiki.winehq.org/UrlMon">UrlMon</a>. Dimi also
+<a href="https://wiki.winehq.org/MsHtml">MsHtml</a> and
+<a href="https://wiki.winehq.org/UrlMon">UrlMon</a>. Dimi also
wanted to know what the problem was with shdocvw, the
Microsoft shell doc object and control library. Jacek
described what was going on with it:</p>
diff --git a/wwn/en/wn20051025_296.xml b/wwn/en/wn20051025_296.xml
index 0b1002c..140e8b4 100644
--- a/wwn/en/wn20051025_296.xml
+++ b/wwn/en/wn20051025_296.xml
@@ -373,7 +373,7 @@ likely drive
to
<a href="//www.winehq.org/wwn/290#Safedisc%20Begins%20to%20Work">improve</a>
copy protection support. On the tools side of things, the new
-<a href="http://wiki.winehq.org">Wine Wiki</a> has proven to be quite
+<a href="https://wiki.winehq.org">Wine Wiki</a> has proven to be quite
successful. In the more distant future, Mac OS X on Intel presents an
interesting opportunity and could very well lead to very successful port.
And, as always, at any time a major patch could arrive from out of the blue
diff --git a/wwn/en/wn20051202_300.xml b/wwn/en/wn20051202_300.xml
index 3da55a1..80fafa0 100644
--- a/wwn/en/wn20051202_300.xml
+++ b/wwn/en/wn20051202_300.xml
@@ -128,7 +128,7 @@ since I can publish it there directly.
<section
title="wine.git"
subject="Git"
- archive="http://wiki.winehq.org/GitWine"
+ archive="https://wiki.winehq.org/GitWine"
posts="1"
>
<topic>Project Management</topic>
@@ -144,7 +144,7 @@ and the commit messages appearing on
<a href="//www.winehq.org/pipermail/wine-cvs/">wine-cvs</a> have
changed in format to reflect the git commits.</p>
<p>In lieu of having a real thread to cover, I'll refer you to Mike McCormack's
-<a href="http://wiki.winehq.org/GitWine">GitWine</a> page on the wiki.
+<a href="https://wiki.winehq.org/GitWine">GitWine</a> page on the wiki.
He has instructions for getting git up and running. </p>
<p>Interestingly, in a thread this week Alexandre mentioned we
now have an even older history of Wine than what's in CVS,
diff --git a/wwn/en/wn20060122_303.xml b/wwn/en/wn20060122_303.xml
index 755fbcb..f3fc3bb 100644
--- a/wwn/en/wn20060122_303.xml
+++ b/wwn/en/wn20060122_303.xml
@@ -302,8 +302,8 @@ side by side by side XP SP2. Tom's brief announcement read:</p>
<quote who="Tom Wickline"><p>
Please take with a large dose of salt.
-<ul><a href="http://wiki.winehq.org/BenchMark-0.9.5">
-http://wiki.winehq.org/BenchMark-0.9.5</a></ul></p></quote>
+<ul><a href="https://wiki.winehq.org/BenchMark-0.9.5">
+https://wiki.winehq.org/BenchMark-0.9.5</a></ul></p></quote>
<p>Chris Morgan pointed out Wine appeared to be doing better,
<quote who="Chris Morgan">
@@ -568,8 +568,8 @@ interested to know if you can get Office 2000 to install and run with
Wine out of the box or with my cheats. :D So others who read the
howto in the future will know the status of their distro.
-<ul><a href="http://wiki.winehq.org/Office-BSD?action=show">
-http://wiki.winehq.org/Office-BSD?action=show</a>
+<ul><a href="https://wiki.winehq.org/Office-BSD?action=show">
+https://wiki.winehq.org/Office-BSD?action=show</a>
</ul></p></quote>
diff --git a/wwn/en/wn20060210_305.xml b/wwn/en/wn20060210_305.xml
index 2dc2f84..d503920 100644
--- a/wwn/en/wn20060210_305.xml
+++ b/wwn/en/wn20060210_305.xml
@@ -120,7 +120,7 @@ Alexandre noted the following significant changes:</p>
</ul>
</p></quote>
<p>Good stuff. Now go grab Wine from
-<a href="http://wiki.winehq.org/GitWine">the GIT repository</a> and compile it.
+<a href="https://wiki.winehq.org/GitWine">the GIT repository</a> and compile it.
All the cool kids are doing it.</p>
<p>Am I the only one who still wants to call them Lindows? </p>
<p>This week CrossOver Office for Linspire was released. The biggest
diff --git a/wwn/en/wn20060305_307.xml b/wwn/en/wn20060305_307.xml
index ff3802e..586c546 100644
--- a/wwn/en/wn20060305_307.xml
+++ b/wwn/en/wn20060305_307.xml
@@ -94,7 +94,7 @@ changes:</p>
<p>Grab the binary off the
<a href="//www.winehq.org/download">download page</a> or
-<a href="http://wiki.winehq.org/GitWine">git</a> it.
+<a href="https://wiki.winehq.org/GitWine">git</a> it.
</p>
</section>
<section
@@ -109,7 +109,7 @@ It's been known for a long time that using Wine with Valgrind has the
potential to uncover problems. In the past, special patches have been
required with for Wine or Valgrind or both. Eric Pouech has spent some
time working on this recently and created a
-<a href="http://wiki.winehq.org/Wine_and_Valgrind">Wine_and_Valgrind</a>
+<a href="https://wiki.winehq.org/Wine_and_Valgrind">Wine_and_Valgrind</a>
wiki page to document the progress. From that page:</p>
<quote who="Eric Pouech"><p>
diff --git a/wwn/en/wn20060428_312.xml b/wwn/en/wn20060428_312.xml
index eac6783..75c955b 100644
--- a/wwn/en/wn20060428_312.xml
+++ b/wwn/en/wn20060428_312.xml
@@ -376,8 +376,8 @@ May 7th. </p>
strategy for attracting participants:</p>
<quote who="Dan Kegel"><p>
I've updated
-<a href="http://wiki.winehq.org/SummerOfCode">
-http://wiki.winehq.org/SummerOfCode</a>,
+<a href="https://wiki.winehq.org/SummerOfCode">
+https://wiki.winehq.org/SummerOfCode</a>,
but it's a bit short on project ideas.
Somewhat on purpose -- last year, people just copied
and pasted our detailed project ideas. This year, lets
@@ -451,7 +451,7 @@ integrate with the current changes going into ddraw.
<quote who="Troy Rollo"><p>
Yes. See <i>
-<a href="http://wiki.winehq.org/DIBEngine">http://wiki.winehq.org/DIBEngine</a>
+<a href="https://wiki.winehq.org/DIBEngine">https://wiki.winehq.org/DIBEngine</a>
</i> for more information on this.
</p><p>
This is probably feasible as a SOC project *if* you are familiar with all of
@@ -571,8 +571,8 @@ wine server internals.
</p><p>Details:
To implement the SafeDisc Support.
The progress and details can be found here
-<ul><a href="http://wiki.winehq.org/VitaliyMargolen">
-http://wiki.winehq.org/VitaliyMargolen</a></ul>
+<ul><a href="https://wiki.winehq.org/VitaliyMargolen">
+https://wiki.winehq.org/VitaliyMargolen</a></ul>
This basically needs the IRP framework for to be implemented for wine (the
difficult part).
</p></quote>
diff --git a/wwn/en/wn20060515_313.xml b/wwn/en/wn20060515_313.xml
index 1e3ac2a..53bb51c 100644
--- a/wwn/en/wn20060515_313.xml
+++ b/wwn/en/wn20060515_313.xml
@@ -444,8 +444,8 @@ the switch to our implementation bugs 3466 and 3515 will be fixed. In
both cases there are still some problems, but apps can run and view HTML.
</p><p>
If someone wants to test it, I've created a Wiki page about it:
-<a href="http://wiki.winehq.org/ShDocVw">
-http://wiki.winehq.org/ShDocVw</a>.
+<a href="https://wiki.winehq.org/ShDocVw">
+https://wiki.winehq.org/ShDocVw</a>.
</p><p>
Because AFAIK there is much interest in Steam, I plan to do the switch
as follows:
diff --git a/wwn/en/wn20060605_315.xml b/wwn/en/wn20060605_315.xml
index b2468b1..9ff0900 100644
--- a/wwn/en/wn20060605_315.xml
+++ b/wwn/en/wn20060605_315.xml
@@ -134,27 +134,27 @@ are:</a></p>
<quote who="Google"><p>
<ul>
<li>Implementing Wine Oleview application
- (<a href="http://wiki.winehq.org/OleView">more info</a>)
+ (<a href="https://wiki.winehq.org/OleView">more info</a>)
<ul><li>by Piotr Caban, mentored by James Hawkins</li></ul></li>
<li>Improve riched20
- (<a href="http://wiki.winehq.org/MatthewFinnicum">more info</a>)
+ (<a href="https://wiki.winehq.org/MatthewFinnicum">more info</a>)
<ul><li>by Matthew Finnicum, mentored by Mike Hearn</li></ul></li>
<li>Clam AntiVirus integration in Wine
(<a href="http://www.christoph-probst.com/soc2006/wine/proposal.txt">more
info</a>)
<ul><li>by Christoph Probst, mentored by Marcus Meissner</li></ul></li>
<li>Improve mswsock.dll
- (<a href="http://wiki.winehq.org/%c5%81ukaszChr%c3%b3st">more info</a>)
+ (<a href="https://wiki.winehq.org/%c5%81ukaszChr%c3%b3st">more info</a>)
<ul><li>by tukasz Chrost, mentored by Eric Pouech</li></ul></li>
<li>Shell integration (covered below)
<ul><li>by Mikolaj Zalewski, mentored by Ulrich Czekalla</li></ul></li>
<li>NTLM signing/sealing using GENSEC
- (<a href="http://wiki.winehq.org/KaiBlin">more info</a>
+ (<a href="https://wiki.winehq.org/KaiBlin">more info</a>
<ul><li>by Kai Blin, mentored by Juan Lang</li></ul></li>
</ul></p></quote>
<p>So there ya have it. Those info links mostly go to the
-<a href="http://wiki.winehq.org/">Wine Wiki</a> where most of the students
+<a href="https://wiki.winehq.org/">Wine Wiki</a> where most of the students
have posted info about what they're working on.</p>
<p>
@@ -283,7 +283,7 @@ there's been renewed interest in getting that bug fixed, but apparently
no one capable of fixing it has time right now. Discussion of that bug
consumed a lot of the rest of the thread. </p>
-<p>In the end, Dan <a href="http://wiki.winehq.org/DanKegel">provided</a>
+<p>In the end, Dan <a href="https://wiki.winehq.org/DanKegel">provided</a>
a list of things he'd like to see fixed. It included getting Windows
developers to take Wine seriously by getting IDEs and debuggers working well.
He also listed some broken installers that needed to get working.
@@ -294,7 +294,7 @@ tasks were needed for 1.0. Discussion has occurred off and on about a
DIB engine, but it seemed to be generally acknowledged that task wasn't
necessary for 1.0. Lastly, although Alexandre didn't weigh in on the
discussion, he does maintain a
-<a href="http://wiki.winehq.org/AlexandreJulliard">list</a>
+<a href="https://wiki.winehq.org/AlexandreJulliard">list</a>
of things he wants to get working. </p>
diff --git a/wwn/en/wn20060611_316.xml b/wwn/en/wn20060611_316.xml
index 22420bf..fc8973f 100644
--- a/wwn/en/wn20060611_316.xml
+++ b/wwn/en/wn20060611_316.xml
@@ -200,7 +200,7 @@ senstive registry key:
<p>There was some discussion about the patch and Mike Hearn requested
a bit of documentation be added to describe how it all works. Jason
did so and you can find an in-depth description of Wine's
-<a href="http://wiki.winehq.org/DirectX-Shaders">DirectX shaders</a>
+<a href="https://wiki.winehq.org/DirectX-Shaders">DirectX shaders</a>
on the wiki. </p>
@@ -472,7 +472,7 @@ rights so that they can add/change/delete certain fields IE:
administrator.<ul> </ul>
There is a todo list here as well:
-<a href="http://wiki.winehq.org/AppdbInfo">http://wiki.winehq.org/AppdbInfo</a>
+<a href="https://wiki.winehq.org/AppdbInfo">https://wiki.winehq.org/AppdbInfo</a>
<ul> </ul>
If anyone has experience with PHP or wants to gain some, there is a real
need for your help.
diff --git a/wwn/en/wn20060810_319.xml b/wwn/en/wn20060810_319.xml
index 9e98dda..eb59a7f 100644
--- a/wwn/en/wn20060810_319.xml
+++ b/wwn/en/wn20060810_319.xml
@@ -639,7 +639,7 @@ Lotus Notes port to Linux. Well, there's still going to be some missing
features in the near term, such as Designer not being included. There's
also concern that the reliance on Java could easily require more resources
(memory) than Wine and the Windows Notes client. Dan Kegel put together a nice
- <a href="http://wiki.winehq.org/LotusNotes">summary</a> on the wiki about
+ <a href="https://wiki.winehq.org/LotusNotes">summary</a> on the wiki about
all that. There's also been an effort lately by a few developers to get
the Notes 7 client running. A few days ago Dan reported he got it running:</p>
<quote who="Dan Kegel"><p>
@@ -647,7 +647,7 @@ Thanks to a few targeted patches written by
Stefan Siebert and James Hawkins,
and of course decades of effort by the whole Wine team,
Lotus Notes 7 trial version now installs and runs!
-See <a href="http://wiki.winehq.org/LotusNotes">http://wiki.winehq.org/LotusNotes</a> for details.
+See <a href="https://wiki.winehq.org/LotusNotes">https://wiki.winehq.org/LotusNotes</a> for details.
</p><p>
I just spent an hour or so playing with Notes as a plain old
email client. It had a few mysterious crashes, but in general
diff --git a/wwn/en/wn20070216_321.xml b/wwn/en/wn20070216_321.xml
index 924e5c2..024451e 100644
--- a/wwn/en/wn20070216_321.xml
+++ b/wwn/en/wn20070216_321.xml
@@ -536,10 +536,10 @@ feel like doing that?</p></quote>
<quote who="Tom Wickline"><p>
I also put a link in
-<a href="http://wiki.winehq.org/HackingTips">http://wiki.winehq.org/HackingTips</a> under Tips & Tricks.
+<a href="https://wiki.winehq.org/HackingTips">https://wiki.winehq.org/HackingTips</a> under Tips & Tricks.
</p><p>
Here's what I have:
-<a href="http://wiki.winehq.org/Developers-Hints">http://wiki.winehq.org/Developers-Hints</a>
+<a href="https://wiki.winehq.org/Developers-Hints">https://wiki.winehq.org/Developers-Hints</a>
</p></quote>
<p>Alexandre thanked him and removed it from the source tree.</p>
diff --git a/wwn/en/wn20070219_322.xml b/wwn/en/wn20070219_322.xml
index d35e302..e0608c9 100644
--- a/wwn/en/wn20070219_322.xml
+++ b/wwn/en/wn20070219_322.xml
@@ -257,7 +257,7 @@ pretty well in most cases. The motivation to fix the corner cases that
the DIB engine would address doesn't seem to exist. Yet, most people
agree that a DIB engine would bring large performance benefits. We've
covered this topic in depth many times and you can see the wiki page
-for <a href="http://wiki.winehq.org/DIBEngine">a description</a> of
+for <a href="https://wiki.winehq.org/DIBEngine">a description</a> of
exactly what the issue is. The short version: we need to be able to
draw things within Wine that we're currently relying on the X server to
do. Besides just writing the code, there's a huge concern about how to
@@ -371,7 +371,7 @@ the time for us to propose new projects and review the ones we have
already listed on the Wiki for interested applicants? As well as line
up mentors for the accepted applicants?
<ul>
-<li><a href="http://wiki.winehq.org/SummerOfCode">http://wiki.winehq.org/SummerOfCode</a></li>
+<li><a href="https://wiki.winehq.org/SummerOfCode">https://wiki.winehq.org/SummerOfCode</a></li>
<li><a href="http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html">http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html</a></li></ul>
</p></quote>
@@ -391,7 +391,7 @@ There's also about a bazillion other things you could take a stab at.</p>
freedesktop.org specs:</p>
<quote who="David Saez Padros"><p>
I saw your post at
-<a href="http://wiki.winehq.org/GnomeMenusIntegration">http://wiki.winehq.org/GnomeMenusIntegration</a>
+<a href="https://wiki.winehq.org/GnomeMenusIntegration">https://wiki.winehq.org/GnomeMenusIntegration</a>
and i made some freedesktop compliant files which:
<ul>
<li> add a global Wine menu item in the Aplications menu (seen
diff --git a/wwn/en/wn20070319_326.xml b/wwn/en/wn20070319_326.xml
index da78e83..48e7826 100644
--- a/wwn/en/wn20070319_326.xml
+++ b/wwn/en/wn20070319_326.xml
@@ -257,11 +257,11 @@ Tom Wickline wrote in to let everyone know about some updated benchmarks
he ran:</p>
<quote who="Tom Wickline"><p>
I have some benchmarks posted here:
-<ul><a href="http://wiki.winehq.org/BenchMark-0.9.5">
-http://wiki.winehq.org/BenchMark-0.9.5</a></ul>
+<ul><a href="https://wiki.winehq.org/BenchMark-0.9.5">
+https://wiki.winehq.org/BenchMark-0.9.5</a></ul>
as well as here:
-<ul><a href="http://wiki.winehq.org/BenchMark-0.9.6">
-http://wiki.winehq.org/BenchMark-0.9.6</a></ul>
+<ul><a href="https://wiki.winehq.org/BenchMark-0.9.6">
+https://wiki.winehq.org/BenchMark-0.9.6</a></ul>
</p><p>
And I have all the Graphics test in PCMark 04 running, but the app is
crashing between test, but if I run them one at a time they will
diff --git a/wwn/en/wn20070330_327.xml b/wwn/en/wn20070330_327.xml
index dd6b4b8..118c1f5 100644
--- a/wwn/en/wn20070330_327.xml
+++ b/wwn/en/wn20070330_327.xml
@@ -366,16 +366,16 @@ time.
I also updated the CAPS page with 0.9.33 and 1.0.9755.
</p><p>
0.9.33 results:
-<ul><a href="http://wiki.winehq.org/BenchMark-0.9.33">
-http://wiki.winehq.org/BenchMark-0.9.33</a></ul>
+<ul><a href="https://wiki.winehq.org/BenchMark-0.9.33">
+https://wiki.winehq.org/BenchMark-0.9.33</a></ul>
</p><p>
Past results:
-<ul><a href="http://wiki.winehq.org/BenchMarks">
-http://wiki.winehq.org/BenchMarks</a></ul>
+<ul><a href="https://wiki.winehq.org/BenchMarks">
+https://wiki.winehq.org/BenchMarks</a></ul>
</p><p>
CAPS results:
-<ul><a href="http://wiki.winehq.org/DirectX-Caps">
-http://wiki.winehq.org/DirectX-Caps</a></ul>
+<ul><a href="https://wiki.winehq.org/DirectX-Caps">
+https://wiki.winehq.org/DirectX-Caps</a></ul>
</p><p>
Some screen shots of past test results.... You may want to look at
them ASAP if you are interested in them, I plan to ask Dimi to rm -rf the
@@ -383,8 +383,8 @@ page in a couple weeks to save the HD space on the wiki server, this
way I can start a new "In Progress" page and not feel guilty about
uploading all the shots :D
</p><p>
-<ul><a href="http://wiki.winehq.org/BenchMark-0.9.6">
-http://wiki.winehq.org/BenchMark-0.9.6</a></ul>
+<ul><a href="https://wiki.winehq.org/BenchMark-0.9.6">
+https://wiki.winehq.org/BenchMark-0.9.6</a></ul>
</p></quote>
<p>The benchmarks highlight something interesting about Wine's
diff --git a/wwn/en/wn20070410_328.xml b/wwn/en/wn20070410_328.xml
index 6924587..d32bc71 100644
--- a/wwn/en/wn20070410_328.xml
+++ b/wwn/en/wn20070410_328.xml
@@ -341,8 +341,8 @@ I get column headers
but nothing under them. Is this supposed to work?
</p><p>
In the meantime, I'll make do with
-<ul><a href="http://wiki.winehq.org/Debug_trace_toggle_key">
-http://wiki.winehq.org/Debug_trace_toggle_key</a></ul>
+<ul><a href="https://wiki.winehq.org/Debug_trace_toggle_key">
+https://wiki.winehq.org/Debug_trace_toggle_key</a></ul>
which is kind of what I was looking for anyway.
</p></quote>
diff --git a/wwn/en/wn20070416_329.xml b/wwn/en/wn20070416_329.xml
index fa5465d..4e1f574 100644
--- a/wwn/en/wn20070416_329.xml
+++ b/wwn/en/wn20070416_329.xml
@@ -243,7 +243,7 @@ benchmark code or because of compiler differences.
years now. It was broken (some would say 'fixed') when the window management
rewrite occurred. There's been some ideas floated about how to fix it, but
nothing has really come of it. For more background on this issue, see the
-<a href="http://wiki.winehq.org/OpenGL">OpenGL wiki</a> page. Ulrich Czekalla
+<a href="https://wiki.winehq.org/OpenGL">OpenGL wiki</a> page. Ulrich Czekalla
floated a <a href="//www.winehq.org/pipermail/wine-patches/2006-October/031336.html">a patch</a>
last October, but it was never included in Wine. Roderick Colenbrander sent a
patch this week with a different approach and
@@ -633,12 +633,12 @@ work around that by interfacing with winbindd to get the stuff we need.
A quick search through our wiki shows me that Juan put up three pages about
this when we discussed this last time.
<ul>
-<li><a href="http://wiki.winehq.org/NamedPipes">
-http://wiki.winehq.org/NamedPipes</a></li>
-<li><a href="http://wiki.winehq.org/EndPointMapper">
-http://wiki.winehq.org/EndPointMapper</a></li>
-<li><a href="http://wiki.winehq.org/DcomInterfaces">
-http://wiki.winehq.org/DcomInterfaces</a></li>
+<li><a href="https://wiki.winehq.org/NamedPipes">
+https://wiki.winehq.org/NamedPipes</a></li>
+<li><a href="https://wiki.winehq.org/EndPointMapper">
+https://wiki.winehq.org/EndPointMapper</a></li>
+<li><a href="https://wiki.winehq.org/DcomInterfaces">
+https://wiki.winehq.org/DcomInterfaces</a></li>
</ul></p><p>
If we can flesh those out in the next week or two, I'll have some more
substantial things to take with me to SambaXP to discuss this. I think the
diff --git a/wwn/en/wn20071203_333.xml b/wwn/en/wn20071203_333.xml
index 137389b..02f3876 100644
--- a/wwn/en/wn20071203_333.xml
+++ b/wwn/en/wn20071203_333.xml
@@ -492,7 +492,7 @@ we'll defer those for later.
Dan also mentions
<p><quote who="Dan Kegel">
Forgot to mention:
-http://wiki.winehq.org/WineReleaseCriteria
+https://wiki.winehq.org/WineReleaseCriteria
has a handy link to a bugzilla query that shows the list of 1.0 bugs.
</quote></p>
diff --git a/wwn/en/wn20071210_334.xml b/wwn/en/wn20071210_334.xml
index d4e30e6..1919feb 100644
--- a/wwn/en/wn20071210_334.xml
+++ b/wwn/en/wn20071210_334.xml
@@ -140,7 +140,7 @@ browser-based application, such as Google Docs.
posts="0"
>
<topic>WineReview</topic>
-<p><a href="http://wiki.winehq.org/TomWickline">Tom Wickline</a> has begun a
+<p><a href="https://wiki.winehq.org/TomWickline">Tom Wickline</a> has begun a
<a href="http://wine-review.blogspot.com/">"Wine-Review" blog</a>. He writes
about his experiences trying every windows application he can find on as many
different platforms he can find.</p>
@@ -188,7 +188,7 @@ calls into something X can handle, lets X do the legwork and then translates
the results back. This is for the most part an effective solution, however
it's known to be inefficient and not without its problems. Alexandre Julliard has
expressed the opinion that implementing a proper DIB engine will likely be done
-post 1.0. See <a href="http://wiki.winehq.org/DIBEngine">the wiki page</a> on
+post 1.0. See <a href="https://wiki.winehq.org/DIBEngine">the wiki page</a> on
DIB for more information.</p>
<p>
In light of all this, Piotr Maceluch writes in to find out the current status
diff --git a/wwn/en/wn20080114_339.xml b/wwn/en/wn20080114_339.xml
index 754bcab..4ef4823 100644
--- a/wwn/en/wn20080114_339.xml
+++ b/wwn/en/wn20080114_339.xml
@@ -104,7 +104,7 @@ More on RunOnce entries later in this wwn.
</p>
<p>
-In other news, Roderick Colenbrander (aka Thunderbird) has written a <a href="http://wiki.winehq.org/DirectDraw">new wiki page</a> about DirectDraw and the relevant registry keys associated with it. I recommend anybody interested in tinkering with such settings read it over once prior to asking questions in #winehq.
+In other news, Roderick Colenbrander (aka Thunderbird) has written a <a href="https://wiki.winehq.org/DirectDraw">new wiki page</a> about DirectDraw and the relevant registry keys associated with it. I recommend anybody interested in tinkering with such settings read it over once prior to asking questions in #winehq.
</p></section>
<section
title="News: Leopard to have wine built in?"
diff --git a/wwn/en/wn20080121_340.xml b/wwn/en/wn20080121_340.xml
index 9672ad6..5dc176c 100644
--- a/wwn/en/wn20080121_340.xml
+++ b/wwn/en/wn20080121_340.xml
@@ -240,7 +240,7 @@ definitely want to enable them again.
>
<topic>Third Party Applications</topic>
<p>
-Tom Wickline has had a chance to <a href="http://wine-review.blogspot.com/2008/01/playonlinux.html">review</a> one of <a href="http://wiki.winehq.org/ThirdPartyApplications">many third party applications</a> for Wine, <a href="http://www.playonlinux.com/en">PlayOnLinux</a>. From the PlayOnLinux site:
+Tom Wickline has had a chance to <a href="http://wine-review.blogspot.com/2008/01/playonlinux.html">review</a> one of <a href="https://wiki.winehq.org/ThirdPartyApplications">many third party applications</a> for Wine, <a href="http://www.playonlinux.com/en">PlayOnLinux</a>. From the PlayOnLinux site:
</p>
<quote>
<p>
diff --git a/wwn/en/wn20080224_341.xml b/wwn/en/wn20080224_341.xml
index 80b4da1..e30cfc9 100644
--- a/wwn/en/wn20080224_341.xml
+++ b/wwn/en/wn20080224_341.xml
@@ -215,7 +215,7 @@ support for Photoshop ('cause so many people want it) and
for Dragon Naturally Speaking ('cause even Linux users get RSI).
While not yet perfect, those apps are a lot more usable now
as a result. In particular, Photoshop CS and CS2 are quite usable
-indeed. (See http://wiki.winehq.org/AdobePhotoshop for
+indeed. (See https://wiki.winehq.org/AdobePhotoshop for
details.)
</p><p>
I also had the pleasure of hosting eight students as
@@ -366,7 +366,7 @@ log at the end, but it generated the "XP wine-0.9.54-notheme" and "XP
wine-0.9.54" results without any issues.
<br /><br />
I have added my experiences to the wiki
-(http://wiki.winehq.org/ConformanceTests) with a link on the main
+(https://wiki.winehq.org/ConformanceTests) with a link on the main
page.
<br /><br />
Feel free to update it with your own experiences
@@ -573,7 +573,7 @@ Now that Adobe Photoshop CS2 is running kind of
well (there are bugs that need fixing, but I'm trying
to look ahead a bit), what big app(s) are worth focusing on next?
</p><p>
-Using http://wiki.winehq.org/LinuxApplicatonRequestSurvey,
+Using https://wiki.winehq.org/LinuxApplicatonRequestSurvey,
skipping Photoshop (which we should continue to fix up)
and the ones that are either too hard, have native versions,
or are probably something CodeWeavers might already be
@@ -582,13 +582,13 @@ we might want to go for it just for the goodwill from all
those tech writers), I think that leaves about seven big
ticket apps, in rough order of popularity:
</p><p>
-<a href="http://wiki.winehq.org/AdobeDreamweaver">http://wiki.winehq.org/AdobeDreamweaver</a><br />
+<a href="https://wiki.winehq.org/AdobeDreamweaver">https://wiki.winehq.org/AdobeDreamweaver</a><br />
iTunes<br />
-<a href="http://wiki.winehq.org/AdobeIllustrator">http://wiki.winehq.org/AdobeIllustrator</a><br />
-<a href="http://wiki.winehq.org/AdobeFlash">http://wiki.winehq.org/AdobeFlash</a><br />
-<a href="http://wiki.winehq.org/AdobePremiere">http://wiki.winehq.org/AdobePremiere</a><br />
-<a href="http://wiki.winehq.org/AdobeAcrobatPro">http://wiki.winehq.org/AdobeAcrobatPro</a><br />
-<a href="http://wiki.winehq.org/AdobeFramemaker">http://wiki.winehq.org/AdobeFramemaker</a><br />
+<a href="https://wiki.winehq.org/AdobeIllustrator">https://wiki.winehq.org/AdobeIllustrator</a><br />
+<a href="https://wiki.winehq.org/AdobeFlash">https://wiki.winehq.org/AdobeFlash</a><br />
+<a href="https://wiki.winehq.org/AdobePremiere">https://wiki.winehq.org/AdobePremiere</a><br />
+<a href="https://wiki.winehq.org/AdobeAcrobatPro">https://wiki.winehq.org/AdobeAcrobatPro</a><br />
+<a href="https://wiki.winehq.org/AdobeFramemaker">https://wiki.winehq.org/AdobeFramemaker</a><br />
</p><p>
I've created wiki pages with trial download URLs for all but iTunes,
and done a bunch of triage on them.
@@ -645,7 +645,7 @@ Yeah, getting .net working would be great, and we seem to be making
some progress there. And getting the copy protection used by these apps
would be great. Googling around, I see that C-Dilla has sometimes been
called Safecast, which is related to Safedisc, so I took the liberty of updating
-<a href="http://wiki.winehq.org/SafeDisc">http://wiki.winehq.org/SafeDisc</a> with a link to the Autocad 2000 bug,
+<a href="https://wiki.winehq.org/SafeDisc">https://wiki.winehq.org/SafeDisc</a> with a link to the Autocad 2000 bug,
<a href="//bugs.winehq.org/show_bug.cgi?id=8466">http://bugs.winehq.org/show_bug.cgi?id=8466</a>. That one looks like
it's waiting for some action - James pointed out a simple-looking problem,
but nobody's tackled it yet.
diff --git a/wwn/en/wn20080304_342.xml b/wwn/en/wn20080304_342.xml
index d994755..ef2f74e 100644
--- a/wwn/en/wn20080304_342.xml
+++ b/wwn/en/wn20080304_342.xml
@@ -49,7 +49,7 @@ Its main goal is to cover some big milestones that Wine has hit recently. It als
Google recently announced their spec. for Google Summer of Code 2008 and the Wine community did not miss a beat. For official information:
<br /><br />
Wine's Wiki Page:<br />
-*<a href="http://wiki.winehq.org/SummerOfCode">http://wiki.winehq.org/SummerOfCode</a><br />
+*<a href="https://wiki.winehq.org/SummerOfCode">https://wiki.winehq.org/SummerOfCode</a><br />
Google's Page:<br />
*<a href="http://code.google.com/soc/2008">http://code.google.com/soc/2008</a>
<br /><br />
@@ -83,7 +83,7 @@ something else?
Maarten, you wrote a wiki page about your 2007 experience. Could you add it to
the "Helpful Links" section?
<br /><br />
-[1] <a href="http://wiki.winehq.org/SummerOfCode">http://wiki.winehq.org/SummerOfCode</a>
+[1] <a href="https://wiki.winehq.org/SummerOfCode">https://wiki.winehq.org/SummerOfCode</a>
<br /><br />
Cheers,<br />
Kai
@@ -105,7 +105,7 @@ If anyone is interested, please contact me privately.
</p><p>
I'm also looking for project ideas, if anyone has an idea for a
project for the summer of code, please update
-<a href="http://wiki.winehq.org/SummerOfCode">http://wiki.winehq.org/SummerOfCode</a>. I would prefer projects that can
+<a href="https://wiki.winehq.org/SummerOfCode">https://wiki.winehq.org/SummerOfCode</a>. I would prefer projects that can
be done by small changes at a time, like implementing changes to get
an application to work, instead of something dractic like a dib
engine. It should preferably be doable in 2 to 3 months by someone who
diff --git a/wwn/en/wn20080317_343.xml b/wwn/en/wn20080317_343.xml
index c0133e3..ac6476f 100644
--- a/wwn/en/wn20080317_343.xml
+++ b/wwn/en/wn20080317_343.xml
@@ -211,12 +211,12 @@ Dan Kegel, the Wine 1.0 release manager, has begun to put together concrete plan
<quote>
<p>
-I've updated <a href="http://wiki.winehq.org/WineReleaseCriteria">http://wiki.winehq.org/WineReleaseCriteria</a>
+I've updated <a href="https://wiki.winehq.org/WineReleaseCriteria">https://wiki.winehq.org/WineReleaseCriteria</a>
to be a bit more final.<br /><br />
I've also written a draft release plan; see
<br /><br />
-<a href="http://wiki.winehq.org/WineReleasePlan">http://wiki.winehq.org/WineReleasePlan</a>
+<a href="https://wiki.winehq.org/WineReleasePlan">https://wiki.winehq.org/WineReleasePlan</a>
<br /><br />
Comments?
</p>
@@ -348,7 +348,7 @@ Maarten.
</p>
</quote>
<p>
-I think he sounds excited :). As you may know by now Maarten is our head organizer for GSoC this year. Thus far wine has a <a href="http://wiki.winehq.org/SummerOfCode">reasonalby lengthy</a> list of ideas for student projects this summer, including the following:
+I think he sounds excited :). As you may know by now Maarten is our head organizer for GSoC this year. Thus far wine has a <a href="https://wiki.winehq.org/SummerOfCode">reasonalby lengthy</a> list of ideas for student projects this summer, including the following:
</p>
<quote>
<p>
diff --git a/wwn/en/wn20080331_344.xml b/wwn/en/wn20080331_344.xml
index a6872d5..fe9a6d5 100644
--- a/wwn/en/wn20080331_344.xml
+++ b/wwn/en/wn20080331_344.xml
@@ -190,7 +190,7 @@ At CodeWeavers, we believe strongly in truth in advertising. This section is an
>
<topic>Cygwin + Wine</topic>
<p>
-The Wine community has a <a href="http://wiki.winehq.org/CygwinSupport">history</a> of trying to get Cygwin to work within Wine. Cygwin is an emulation layer for POSIX on Win32, and as such is a fairly rigorous test for Wine. Thus getting Cygwin running is a challenge, but to do so would be a great accomplishment. Some news from Dan Kegel:
+The Wine community has a <a href="https://wiki.winehq.org/CygwinSupport">history</a> of trying to get Cygwin to work within Wine. Cygwin is an emulation layer for POSIX on Win32, and as such is a fairly rigorous test for Wine. Thus getting Cygwin running is a challenge, but to do so would be a great accomplishment. Some news from Dan Kegel:
</p>
<quote>
<p>
@@ -207,7 +207,7 @@ Hats off to the Wine team!
</p>
</quote>
<p>
-I myself went ahead and tried the same program (fork) from the <a href="http://wiki.winehq.org/CygwinSupport">'CygwinSupport'</a> wiki page and on Wine 0.9.52 got much further than the wiki page but still had some stack errors, and with wine from source (inbetween .58 and .59) also got similar errors. Well, nobody's perfect, but Wine is certainly making progress!
+I myself went ahead and tried the same program (fork) from the <a href="https://wiki.winehq.org/CygwinSupport">'CygwinSupport'</a> wiki page and on Wine 0.9.52 got much further than the wiki page but still had some stack errors, and with wine from source (inbetween .58 and .59) also got similar errors. Well, nobody's perfect, but Wine is certainly making progress!
</p></section>
<section
title="Detailed reports of Wine 1.0 progress"
diff --git a/wwn/en/wn20080415_345.xml b/wwn/en/wn20080415_345.xml
index 452f14b..63ba2b4 100644
--- a/wwn/en/wn20080415_345.xml
+++ b/wwn/en/wn20080415_345.xml
@@ -365,7 +365,7 @@ let me know if you get a crash when compiling oleaut32. Later when I
have more time I am going to run some benchmarks comparing a directx
game under wine compiled with gcc and icc.
<br />
-<a href="http://wiki.winehq.org/icc">http://wiki.winehq.org/icc</a>br />
+<a href="https://wiki.winehq.org/icc">https://wiki.winehq.org/icc</a>br />
-- <br />
Steven Edwards
</p>
diff --git a/wwn/en/wn20080428_346.xml b/wwn/en/wn20080428_346.xml
index 2ec2636..fd401ce 100644
--- a/wwn/en/wn20080428_346.xml
+++ b/wwn/en/wn20080428_346.xml
@@ -666,7 +666,7 @@ Austin English also presents the idea of linking to the wiki:
</p>
<quote>
<p>
-A link to a wiki page (http://wiki.winehq/MissingDLL ?) with list of
+A link to a wiki page (https://wiki.winehq/MissingDLL ?) with list of
common dlls/where they come from/what they do/how to use winetricks/etc.)
would be a bit easier/quicker to implement.
</p>
diff --git a/wwn/en/wn20080527_347.xml b/wwn/en/wn20080527_347.xml
index f003b89..c88172c 100644
--- a/wwn/en/wn20080527_347.xml
+++ b/wwn/en/wn20080527_347.xml
@@ -153,7 +153,7 @@ Wine is well on its way to hitting 1.0 with two release candidates already being
</p>
</quote>
<p>
-You will also notice that the <a href="//www.winehq.org">main WineHQ.org</a> page has an update on the number of open bugs left until 1.0. The Wine development community continues to encourage users to visit <a href="http://wiki.winehq.org/PlatinumRegressionHunt">one</a> <a href="http://wiki.winehq.org/DogfoodChallenge">of</a> <a href="http://wiki.winehq.org/MakeTestFailures">several</a> different wiki pages about trying to find bugs and regressions in 1.0!
+You will also notice that the <a href="//www.winehq.org">main WineHQ.org</a> page has an update on the number of open bugs left until 1.0. The Wine development community continues to encourage users to visit <a href="https://wiki.winehq.org/PlatinumRegressionHunt">one</a> <a href="https://wiki.winehq.org/DogfoodChallenge">of</a> <a href="https://wiki.winehq.org/MakeTestFailures">several</a> different wiki pages about trying to find bugs and regressions in 1.0!
</p>
<p>
Also, Wine 1.0 <a href="http://linuxrevolution.blogspot.com/2006/09/wine-10-in-early-2007.html">seems</a> <a href="http://www.downloadsquad.com/2008/03/22/wine-1-0-coming-soon-to-a-computer-near-you/">to</a> <a href="http://www.icewalkers.com/Linux/Software/53560/Wine.html">be</a> <a href="http://digg.com/linux_unix/Wine_1_0_rc2_Released">getting</a> <a href="http://linux.slashdot.org/article.pl?sid=08/05/24/1745221&from=rss">tons</a> <a href="http://wine-review.blogspot.com/2008/03/wine-10-release-criteria-updated.html">of</a> <a href="http://www.phoronix.com/scan.php?page=news_item&px=NjM5Ng">press</a> <a href="http://www.desktoplinux.com/news/NS7959950148.html">all</a> <a href="http://www.linux.com/feed/134814">over</a> the internet.
@@ -680,7 +680,7 @@ Dan Kegel:
<p>
I just wrote up an idea related to release management for post-1.0
wine releases. It's online at
-<a href="http://wiki.winehq.org/TimeBasedReleases">http://wiki.winehq.org/TimeBasedReleases</a>
+<a href="https://wiki.winehq.org/TimeBasedReleases">https://wiki.winehq.org/TimeBasedReleases</a>
Essentially, the idea is to release in March and September,
in time for the April and October releases of Ubuntu.
</p><p>
@@ -908,7 +908,7 @@ Jaroslav Tomecek
>
<topic>Test Suite</topic>
<p>
-Wine's <a href="http://wiki.winehq.org/WineReleaseCriteria"> official release criteria</a> includes a number of applications and a specific set of bugs, but theres also a far more important, behind the scenes, goal which all of the dev's are striving for: a working, reliable test suite. Winetest has been around for a long time (2002 ish) and has great coverage of much of the windows api that wine implements. The major issue is that many of the tests not only fail when running with wine, but some pass on wine and fail on windows! There has been a big push to get 100% tests passing on Wine and greatly improving the consistency on windows.
+Wine's <a href="https://wiki.winehq.org/WineReleaseCriteria"> official release criteria</a> includes a number of applications and a specific set of bugs, but theres also a far more important, behind the scenes, goal which all of the dev's are striving for: a working, reliable test suite. Winetest has been around for a long time (2002 ish) and has great coverage of much of the windows api that wine implements. The major issue is that many of the tests not only fail when running with wine, but some pass on wine and fail on windows! There has been a big push to get 100% tests passing on Wine and greatly improving the consistency on windows.
</p>
<p>
<a href="//test.winehq.org/data/">test.winehq.org</a> has been around for a while to compile the results of running a test suite on a specific platform. Recently Alexandre Julliard with the help of several others revamped the test.winehq.org main page. Also, Jeremy Newman put in a fair amount of work to make it easy for users to run the whole test suite and have their results posted to test.winehq.org. These have all been very useful tools to the community! The test suite is nearly perfect on Wine and fixes for the tests for Windows keep coming in.
diff --git a/wwn/en/wn20080714_349.xml b/wwn/en/wn20080714_349.xml
index e36dae0..10f26da 100644
--- a/wwn/en/wn20080714_349.xml
+++ b/wwn/en/wn20080714_349.xml
@@ -189,7 +189,7 @@ Thanks to the volunteer efforts of James Ramey (new guy in our office),
we now have a great venue for Wineconf 2008.
</p><p>
I've put together a page on it here:<br />
- <a href="http://wiki.winehq.org/WineConf2008">http://wiki.winehq.org/WineConf2008</a>
+ <a href="https://wiki.winehq.org/WineConf2008">https://wiki.winehq.org/WineConf2008</a>
</p><p>
The key details are that it will be over the weekend of September 27 and 28,
at a hotel in Bloomington, MN. I promise that it won't be mind numbingly cold,
diff --git a/wwn/en/wn20080922_352.xml b/wwn/en/wn20080922_352.xml
index 77abf58..4e24ad9 100644
--- a/wwn/en/wn20080922_352.xml
+++ b/wwn/en/wn20080922_352.xml
@@ -177,12 +177,12 @@ dissuade other vendors from doing native ports.<br />
<section
title="WineConf 2008 Coming Up"
subject="WineConf"
- archive="http://wiki.winehq.org/WineConf2008"
+ archive="https://wiki.winehq.org/WineConf2008"
posts="1"
>
<topic>WineConf</topic>
<p>
-WineConf 2008 is coming up, in St. Paul Minnesota, this weekend. The big theme of the event is a gigantic celebration of Wine 1.0! The <a href="http://wiki.winehq.org/WineConf2008">wiki page</a> has an outline of arrival times and a rough agenda of what will take place.
+WineConf 2008 is coming up, in St. Paul Minnesota, this weekend. The big theme of the event is a gigantic celebration of Wine 1.0! The <a href="https://wiki.winehq.org/WineConf2008">wiki page</a> has an outline of arrival times and a rough agenda of what will take place.
</p>
<p>
In addition WineConf traditionally has a mini hackathon -- in past years its been on the test suite in general. This year it appears we may be working hard to fix the test suite on windows machines.
diff --git a/wwn/en/wn20090109_355.xml b/wwn/en/wn20090109_355.xml
index 1b7f771..8fc3e97 100644
--- a/wwn/en/wn20090109_355.xml
+++ b/wwn/en/wn20090109_355.xml
@@ -474,11 +474,11 @@ Max
>
<topic>Wine64</topic>
<p>
-Improvements in Wine's ability to compile for 64-bits and run native Win64 applications have made a number of headlines lately. Many of the major roadblocks have been cleared, and some major benchmarks are starting to be met. Maarten has a number of test applications working and Dan Kegel has a new <a href="http://wiki.winehq.org/Wine64">wiki page</a> for compiling Wine64 yourself. There is also a a 64-bit version of <a href="//test.winehq.org/builds/winetest64-latest.exe">winetest</a> available on the <a href="//test.winehq.org/data/">wine test page</a>. Speaking of the test suite, Wine64 does pass a significant number of tests. Dan Kegel:
+Improvements in Wine's ability to compile for 64-bits and run native Win64 applications have made a number of headlines lately. Many of the major roadblocks have been cleared, and some major benchmarks are starting to be met. Maarten has a number of test applications working and Dan Kegel has a new <a href="https://wiki.winehq.org/Wine64">wiki page</a> for compiling Wine64 yourself. There is also a a 64-bit version of <a href="//test.winehq.org/builds/winetest64-latest.exe">winetest</a> available on the <a href="//test.winehq.org/data/">wine test page</a>. Speaking of the test suite, Wine64 does pass a significant number of tests. Dan Kegel:
</p>
<quote>
<p>
-I updated <a href="http://wiki.winehq.org/Wine64">http://wiki.winehq.org/Wine64</a> with easy
+I updated <a href="https://wiki.winehq.org/Wine64">https://wiki.winehq.org/Wine64</a> with easy
instructions (thanks, Maarten!) for how to build
wine's 64 bit support and try 64 bit pacman
(which works!).
diff --git a/wwn/en/wn20090204_356.xml b/wwn/en/wn20090204_356.xml
index d95ef78..87f91a9 100644
--- a/wwn/en/wn20090204_356.xml
+++ b/wwn/en/wn20090204_356.xml
@@ -81,7 +81,7 @@ Its main goal is to announce ANOTHER platform passing the tests! This issue als
>
<topic>Wine</topic>
<p>
-Dan Kegel made a quick <a href="http://wiki.winehq.org/AppsThatSupportWine">wiki list</a> of applications that officially support "Wine" as a platform. This list quickly caught the eye of slashdot editors and it went up on front page of the tech section. Thanks to the publicity the list began to grow! Be sure to add any applications or developer studios that you know of to the list!
+Dan Kegel made a quick <a href="https://wiki.winehq.org/AppsThatSupportWine">wiki list</a> of applications that officially support "Wine" as a platform. This list quickly caught the eye of slashdot editors and it went up on front page of the tech section. Thanks to the publicity the list began to grow! Be sure to add any applications or developer studios that you know of to the list!
</p>
<p>
GeekZone has <a href="http://www.geekzone.co.nz/foobar/6201">published</a> a list of several reasons to switch to Linux. Reason number 9:
@@ -388,7 +388,7 @@ James Mckenzie then writes in asking (among other things) if there will be a tra
<p>
I have made a wiki on winehq with an agenda which will be updated with
the results (and maybe transcript?) of the conversation.
- <a href="http://wiki.winehq.org/AppDBUpgrades">http://wiki.winehq.org/AppDBUpgrades</a>
+ <a href="https://wiki.winehq.org/AppDBUpgrades">https://wiki.winehq.org/AppDBUpgrades</a>
</p>
</quote>
<p>
diff --git a/wwn/en/wn20090603_358.xml b/wwn/en/wn20090603_358.xml
index 9941c1e..6903d2c 100644
--- a/wwn/en/wn20090603_358.xml
+++ b/wwn/en/wn20090603_358.xml
@@ -97,7 +97,7 @@ as possible.
</p><p>
Directions, agenda, etc. will be made available on this page:
</p><p>
- <a href="http://wiki.winehq.org/WineConf">http://wiki.winehq.org/WineConf</a>
+ <a href="https://wiki.winehq.org/WineConf">https://wiki.winehq.org/WineConf</a>
</p><p>
Please e-mail me at wineconf at meelstraat.net if you intend to come, so we
can make a better estimation of the number of attendees.
diff --git a/wwn/en/wn20090913_359.xml b/wwn/en/wn20090913_359.xml
index 499638c..6e4a5c9 100644
--- a/wwn/en/wn20090913_359.xml
+++ b/wwn/en/wn20090913_359.xml
@@ -172,7 +172,7 @@ this Monday. The purpose of triaging bugs is to ultimately get them
fixed, so if you're a developer and would rather work on patches then by
all means do that instead.
</p>
-<p>I've created a wiki page for the event here: <a href="http://wiki.winehq.org/BugDay">http://wiki.winehq.org/BugDay</a>
+<p>I've created a wiki page for the event here: <a href="https://wiki.winehq.org/BugDay">https://wiki.winehq.org/BugDay</a>
When we're done I'll poke BugZilla for some stats and we can see how
much of a success the event was.
</p>
diff --git a/wwn/en/wn20090921_360.xml b/wwn/en/wn20090921_360.xml
index c22071c..8805175 100644
--- a/wwn/en/wn20090921_360.xml
+++ b/wwn/en/wn20090921_360.xml
@@ -52,7 +52,7 @@ Its main goal is to introduce Wineconf 2009! It also serves to inform you of wha
>
<topic>Wineconf</topic>
<p>
-<a href='http://wiki.winehq.org/WineConf2009'>Wineconf 2009</a> has been announced and community members have begun signing up to attend. This year's conference will be held in Enschede Netherlands on November 7th and 8th. Wineconf 2008 is now infamous for establishing the ever-so-tough to break <a href='http://www.winehq.org/wwn/353#News: WineConf 2008'>Julliard Rank</a>. Wineconf 2009 is sure to also be filled with fun and interesting insights into the Wine development community! Jeremy White's announcement:
+<a href='https://wiki.winehq.org/WineConf2009'>Wineconf 2009</a> has been announced and community members have begun signing up to attend. This year's conference will be held in Enschede Netherlands on November 7th and 8th. Wineconf 2008 is now infamous for establishing the ever-so-tough to break <a href='http://www.winehq.org/wwn/353#News: WineConf 2008'>Julliard Rank</a>. Wineconf 2009 is sure to also be filled with fun and interesting insights into the Wine development community! Jeremy White's announcement:
</p>
<quote>
<p>
@@ -62,7 +62,7 @@ It's now close enough to November that you can't blow
this email off <grin>.
</p><p>
We've got all the info here:
- <a href="http://wiki.winehq.org/WineConf2009">http://wiki.winehq.org/WineConf2009</a>
+ <a href="https://wiki.winehq.org/WineConf2009">https://wiki.winehq.org/WineConf2009</a>
</p><p>
Our challenge this year is that we're managing the booking,
so we need a firm head count ahead of time.
@@ -223,7 +223,7 @@ The future of appinstall really depends on if users contribute :-). If
anything, those 35 applications will be tested daily. If users would
like to contribute, by writing a test for their favorite downloadable
application, it would be helpful. There's a guide here:
- <a href="http://wiki.winehq.org/Appinstall_Testing.">http://wiki.winehq.org/Appinstall_Testing.</a> Personally, my time
+ <a href="https://wiki.winehq.org/Appinstall_Testing.">https://wiki.winehq.org/Appinstall_Testing.</a> Personally, my time
recently has been spoken for, so I haven't had as much time to work on
it. If I get more free time, or a sponsor ;-), that may change.
There's tons of room for improvement...there are a lot of small
diff --git a/wwn/en/wn20140214_363.xml b/wwn/en/wn20140214_363.xml
index aa147db..84bc90f 100644
--- a/wwn/en/wn20140214_363.xml
+++ b/wwn/en/wn20140214_363.xml
@@ -29,7 +29,7 @@ Its main goal is to fool you into thinking there's going to be issues written re
>
<topic></topic>
<p>
-Hi, my name is André Hentschel, a Wine developer. I guess I'm mostly known for my <a href="http://wiki.winehq.org/ARM">Wine on ARM work</a>,
+Hi, my name is André Hentschel, a Wine developer. I guess I'm mostly known for my <a href="https://wiki.winehq.org/ARM">Wine on ARM work</a>,
but this time I'll try to revive WWN for you. As I'm not a native speaker, enjoy my typos :)
</p>
<p>
@@ -39,7 +39,7 @@ It has long been driven by Zachary Goldberg, but stalled nearly four years ago.
<p>
I can't present many news this time, mostly because I'm not a journalist and thus need the help from others to gather topics around Wine to report.
At best they already come with some more text than just the headline and are posted to
-<a href="http://wiki.winehq.org/RecentNewsQueue">RecentNewsQueue in our Wiki</a>, which is totally out of date.
+<a href="https://wiki.winehq.org/RecentNewsQueue">RecentNewsQueue in our Wiki</a>, which is totally out of date.
</p>
</section>
diff --git a/wwn/en/wn20140303_364.xml b/wwn/en/wn20140303_364.xml
index 3134161..48852ff 100644
--- a/wwn/en/wn20140303_364.xml
+++ b/wwn/en/wn20140303_364.xml
@@ -29,7 +29,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
>
<p>
A user proposed to run Wine on Chrome OS. Actually I once tried compiling Wine with the NaCl SDK:
-<a href="http://wiki.winehq.org/NaCl">http://wiki.winehq.org/NaCl</a>, but it turned out to be too hard
+<a href="https://wiki.winehq.org/NaCl">https://wiki.winehq.org/NaCl</a>, but it turned out to be too hard
to produce runnable binaries for Chromebooks.
</p>
<p>
@@ -72,7 +72,7 @@ Shortly after the last WWN, Marcus wrote:
</p>
<quote>
<p>The FOSDEM Videos have been uploaded with correct sound again.</p>
-<p><a href="http://wiki.winehq.org/FOSDEM2014">http://wiki.winehq.org/FOSDEM2014</a> has our index.</p>
+<p><a href="https://wiki.winehq.org/FOSDEM2014">https://wiki.winehq.org/FOSDEM2014</a> has our index.</p>
<p>Or more direct links: <a href="http://video.fosdem.org/2014/AW1120/Sunday/">http://video.fosdem.org/2014/AW1120/Sunday/</a></p>
</quote>
</section>
@@ -80,7 +80,7 @@ Shortly after the last WWN, Marcus wrote:
<section
title="Google Summer of Code 2014"
subject=""
- archive="http://wiki.winehq.org/SummerOfCode"
+ archive="https://wiki.winehq.org/SummerOfCode"
posts="0"
>
<topic>Interim Period</topic>
@@ -88,7 +88,7 @@ Shortly after the last WWN, Marcus wrote:
Wine is an accepted organization for GSoC 2014, would-be students should now discuss project ideas with us as in one week the Student application period opens.
</p>
<p>
-See <a href="http://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations and project ideas.
+See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations and project ideas.
</p>
</section>
@@ -114,7 +114,7 @@ For each article you buy, we donate part of our benefit to Wine HQ. This way we
<section
title="Winetricks updates"
subject=""
- archive="http://wiki.winehq.org/winetricks"
+ archive="https://wiki.winehq.org/winetricks"
posts="0"
>
<topic>New release, ton of new verbs and updates</topic>
diff --git a/wwn/en/wn20140314_365.xml b/wwn/en/wn20140314_365.xml
index 7877796..3347e83 100644
--- a/wwn/en/wn20140314_365.xml
+++ b/wwn/en/wn20140314_365.xml
@@ -24,7 +24,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
<section
title="Google Summer of Code 2014"
subject=""
- archive="http://wiki.winehq.org/SummerOfCode"
+ archive="https://wiki.winehq.org/SummerOfCode"
posts="0"
>
<topic>Student application period</topic>
@@ -33,7 +33,7 @@ Wine is an accepted organization for GSoC 2014, would-be students should now sub
See the <a href="//www.google-melange.com/gsoc/events/google/gsoc2014">timeline</a> to learn how much time is left.
</p>
<p>
-See <a href="http://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations and project ideas.
+See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations and project ideas.
</p>
</section>
@@ -73,7 +73,7 @@ Jeremy White finally got annoyed enough by the remaining <a href="//test.winehq.
This also had the fact that other developers were afraid to get shamed and also fix test failures :)
</p>
<p>
-We already made good progress, but there are some strange behaviours of Windows, other hard to analyze failures and problems caused by <a href="http://wiki.winehq.org/WineTestBotVMs">the way</a> the WineTestBot works.
+We already made good progress, but there are some strange behaviours of Windows, other hard to analyze failures and problems caused by <a href="https://wiki.winehq.org/WineTestBotVMs">the way</a> the WineTestBot works.
It seems often enough we trigger corner cases in Qemu and upgraded raises even worth problems, so we need to trace them down and fix them.
</p>
<p>
@@ -90,14 +90,14 @@ In the end the benefits of our test suite are:
<li>Detect and prevent Wine regressions.</li>
</ul>
<p>
-See <a href="http://wiki.winehq.org/ConformanceTests">our Wiki</a> for more information.
+See <a href="https://wiki.winehq.org/ConformanceTests">our Wiki</a> for more information.
</p>
</section>
<section
title="WineTestBot"
subject=""
- archive="http://wiki.winehq.org/WineTestBot"
+ archive="https://wiki.winehq.org/WineTestBot"
posts="0"
>
<topic>First month with the new TestBot</topic>
diff --git a/wwn/en/wn20140328_366.xml b/wwn/en/wn20140328_366.xml
index dada939..05ee392 100644
--- a/wwn/en/wn20140328_366.xml
+++ b/wwn/en/wn20140328_366.xml
@@ -24,7 +24,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
<section
title="Google Summer of Code 2014"
subject=""
- archive="http://wiki.winehq.org/SummerOfCode"
+ archive="https://wiki.winehq.org/SummerOfCode"
posts="0"
>
<topic>We review and rank student proposals</topic>
@@ -32,14 +32,14 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
Wine is an accepted organization for GSoC 2014, our potential Mentors and Admins are now reviewing your proposals. Thanks to everyone who sent one!
</p>
<p>
-See <a href="http://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations.
+See <a href="https://wiki.winehq.org/SummerOfCode">our Wiki</a> for more informations.
</p>
</section>
<section
title="Recent News Queue empty"
subject=""
- archive="http://wiki.winehq.org/RecentNewsQueue"
+ archive="https://wiki.winehq.org/RecentNewsQueue"
posts="0"
>
<p>
@@ -47,7 +47,7 @@ Finally i cleaned out the Recent News Queue page, either by posting the story or
Also i tried hard to find potential news myself, but that is nothing i'm good at and steals my time i could spend coding for Wine.
</p>
<p>
-So please, if you find something interesting and Wine related, post it <a href="http://wiki.winehq.org/RecentNewsQueue">there</a>. At best you also add some text, but meanwhile i'm also happy for simple suggestions.
+So please, if you find something interesting and Wine related, post it <a href="https://wiki.winehq.org/RecentNewsQueue">there</a>. At best you also add some text, but meanwhile i'm also happy for simple suggestions.
</p>
</section>
@@ -58,7 +58,7 @@ So please, if you find something interesting and Wine related, post it <a href="
posts="0"
>
<p>
-<a href="http://wiki.winehq.org/AndreHentschel">I recently</a> pushed a lot of changes for WineCE to <a href="https://github.com/AndreRH/wine/tree/winece">github</a>.
+<a href="https://wiki.winehq.org/AndreHentschel">I recently</a> pushed a lot of changes for WineCE to <a href="https://github.com/AndreRH/wine/tree/winece">github</a>.
At the moment WineCE is based on the stable version 1.6.2 and with the new changes this month it should be able to run at least <a href="http://www.pocketputty.net/">PocketPuTTY</a>.
</p>
</section>
@@ -71,9 +71,9 @@ At the moment WineCE is based on the stable version 1.6.2 and with the new chang
>
<topic>CN102364433</topic>
<p>
-Last week i was told about the chinese Patent CN102364433. It claims that <a href="http://wiki.winehq.org/ARM">Wine on ARM</a> was invented by five chinese people and that they want to protect that procedure.
+Last week i was told about the chinese Patent CN102364433. It claims that <a href="https://wiki.winehq.org/ARM">Wine on ARM</a> was invented by five chinese people and that they want to protect that procedure.
While from my point of view there are no facts in that potential Patent that should be patented, there is also a Problem with the timing.
-As you can see <a href="//source.winehq.org/git/wine.git/search/HEAD?pg=1;s=+ARM;st=commit">here</a>, the main commits <a href="http://wiki.winehq.org/AndreHentschel">from me</a> to support the ARM architecture in Wine
+As you can see <a href="//source.winehq.org/git/wine.git/search/HEAD?pg=1;s=+ARM;st=commit">here</a>, the main commits <a href="https://wiki.winehq.org/AndreHentschel">from me</a> to support the ARM architecture in Wine
were published 2010 <a href="//www.winehq.org/announce/1.3.4">(and ARM was supported with Wine 1.3.4)</a>.
But that potential Patent seems to be from June 2011 and tries to describe the procedure of porting Wine to ARM using Wine 1.3.13 which clearly has ARM support.
</p>
diff --git a/wwn/en/wn20150607_392.xml b/wwn/en/wn20150607_392.xml
index 3741114..3000ee9 100644
--- a/wwn/en/wn20150607_392.xml
+++ b/wwn/en/wn20150607_392.xml
@@ -24,7 +24,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
<section
title="WineConf 2015"
subject="WineConf"
- archive="http://wiki.winehq.org/WineConf2015"
+ archive="https://wiki.winehq.org/WineConf2015"
posts="1"
>
<![CDATA[
diff --git a/wwn/en/wn20150914_398.xml b/wwn/en/wn20150914_398.xml
index ae04b4c..f172e9a 100644
--- a/wwn/en/wn20150914_398.xml
+++ b/wwn/en/wn20150914_398.xml
@@ -41,7 +41,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
<section
title="WineConf 2015"
subject="WineConf"
- archive="http://wiki.winehq.org/WineConf2015"
+ archive="https://wiki.winehq.org/WineConf2015"
posts="1"
>
<p>
@@ -49,7 +49,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
</p>
<p>
See also:
- <a href="http://wiki.winehq.org/WineConf2015">WineConf2015 in our Wiki</a>
+ <a href="https://wiki.winehq.org/WineConf2015">WineConf2015 in our Wiki</a>
</p>
</section>
diff --git a/wwn/en/wn20150924_399.xml b/wwn/en/wn20150924_399.xml
index 77cb901..5e666b9 100644
--- a/wwn/en/wn20150924_399.xml
+++ b/wwn/en/wn20150924_399.xml
@@ -9,7 +9,7 @@
<section
title="WineConf 2015"
subject="WineConf"
- archive="http://wiki.winehq.org/WineConf2015"
+ archive="https://wiki.winehq.org/WineConf2015"
posts="1"
>
<p>
@@ -19,7 +19,7 @@
</p>
<p>
See also:
- <a href="http://wiki.winehq.org/WineConf2015">WineConf2015 in our Wiki</a>
+ <a href="https://wiki.winehq.org/WineConf2015">WineConf2015 in our Wiki</a>
</p>
</section>
diff --git a/wwn/en/wn20151004_400.xml b/wwn/en/wn20151004_400.xml
index abe6496..091e0b0 100644
--- a/wwn/en/wn20151004_400.xml
+++ b/wwn/en/wn20151004_400.xml
@@ -24,7 +24,7 @@ Its main goal is to inform you of what's going on around Wine. Wine is an open s
<section
title="WineConf 2015"
subject="WineConf"
- archive="http://wiki.winehq.org/WineConf2015"
+ archive="https://wiki.winehq.org/WineConf2015"
posts="3"
>
<p>
@@ -41,7 +41,7 @@ Over the last few months there have been a lot of discussions about how
to improve our development process. I've been gathering feedback, and
last week at WineConf I summarized the suggestions in my keynote
presentation; the slides can be viewed at
-http://wiki.winehq.org/WineConf2015?action=AttachFile&do=get&target=wineconf-2015.pdf
+https://wiki.winehq.org/WineConf2015?action=AttachFile&do=get&target=wineconf-2015.pdf
We've then had a lot of constructive discussions about the various
points. The major decisions we've agreed on are:
--
1.9.1
More information about the wine-patches
mailing list