2012-03-19 12:55:42 +00:00
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="${LANGUAGE_ISO}">
|
2012-03-19 12:51:31 +00:00
|
|
|
|
|
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Type" content="text/html; charset=${LANGUAGE_CHARSET}" />
|
|
|
|
|
<meta name="description" content="${LANG_METADESC}" />
|
|
|
|
|
<meta name="keywords" content="${LANG_METAKEYW}" />
|
|
|
|
|
<title>'${projname}' - HTTrack Website Copier</title>
|
|
|
|
|
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
<link rel="stylesheet" type="text/css" media="screen" href="style.css">
|
|
|
|
|
<script type="text/javascript" src="ping.js" defer></script>
|
2012-03-19 12:51:31 +00:00
|
|
|
|
|
|
|
|
<script language="javascript">
|
|
|
|
|
<!--
|
|
|
|
|
function do_load() {
|
|
|
|
|
window.status=' ';
|
|
|
|
|
}
|
|
|
|
|
function do_unload() {
|
|
|
|
|
}
|
|
|
|
|
function do_load() {
|
|
|
|
|
window.status=' ';
|
|
|
|
|
form.urls.select();
|
|
|
|
|
}
|
|
|
|
|
function key_event(event) {
|
|
|
|
|
if (event && event.keyCode && event.keyCode == 10) {
|
|
|
|
|
form.nextBtn.click();
|
|
|
|
|
return false;
|
|
|
|
|
}
|
|
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
function info(str) {
|
|
|
|
|
window.status = str;
|
|
|
|
|
}
|
|
|
|
|
function doOpenWindow() {
|
|
|
|
|
childWn=window.open('addurl.html', 'addurl', 'toolbar=no, location=no, directories=no, status=yes, menubar=no, scrollbars=yes, resizable=yes, width=640, height=480');
|
2012-03-19 13:00:51 +00:00
|
|
|
setTimeout("do_check_child()", 100);
|
2012-03-19 12:51:31 +00:00
|
|
|
}
|
|
|
|
|
function do_check_child() {
|
2012-03-19 13:00:51 +00:00
|
|
|
if (childWn && childWn.document) {
|
|
|
|
|
if ((typeof childWn.wparent) == "undefined") {
|
|
|
|
|
childWn.wparent=document;
|
|
|
|
|
setTimeout("do_check_child()", 1000);
|
|
|
|
|
} else {
|
|
|
|
|
childWn.wparent=document;
|
|
|
|
|
}
|
2012-03-19 12:51:31 +00:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
// -->
|
|
|
|
|
</script>
|
|
|
|
|
|
|
|
|
|
</head>
|
|
|
|
|
<body onLoad="do_load();" onUnload="do_unload();" onKeyPress="return key_event(event);">
|
|
|
|
|
|
|
|
|
|
<table width="76%" border="0" align="center" cellspacing="0" cellpadding="0" class="tableWidth">
|
|
|
|
|
<tr>
|
|
|
|
|
<td><img src="images/header_title_4.gif" width="400" height="34" alt="HTTrack Website Copier" title="" border="0" id="title" /></td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
<table width="76%" border="0" align="center" cellspacing="0" cellpadding="3" class="tableWidth">
|
|
|
|
|
<tr>
|
|
|
|
|
<td width="90%" id="subTitle">${LANG_OSFWB}</td>
|
|
|
|
|
<td id="subTitle" align="right">
|
|
|
|
|
<a href="/server/file.html" target="_blank"
|
|
|
|
|
onClick="window.open('/server/file.html', 'help', 'toolbar=no, location=no, directories=no, status=yes, menubar=no, scrollbars=yes, resizable=yes, width=640, height=480'); return false"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_O1}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
style="color:#FFFFFF"
|
|
|
|
|
>
|
|
|
|
|
${LANG_O1}
|
|
|
|
|
</a>
|
|
|
|
|
</td>
|
|
|
|
|
${/* show help only if available */}
|
|
|
|
|
${do:if-file-exists:html/index.html}
|
|
|
|
|
<td id="subTitle">|</td>
|
|
|
|
|
<td id="subTitle" align="right">
|
|
|
|
|
<a href="/index.html" target="_blank"
|
|
|
|
|
onClick="window.open('/server/help.html', 'help', 'toolbar=no, location=no, directories=no, status=yes, menubar=no, scrollbars=yes, resizable=yes, width=640, height=480'); return false"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_TIPHELP}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
style="color:#FFFFFF"
|
|
|
|
|
>
|
|
|
|
|
${LANG_O5}
|
|
|
|
|
</a>
|
|
|
|
|
</td>
|
|
|
|
|
${do:end-if}
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
<table width="76%" border="0" align="center" cellspacing="0" cellpadding="0" class="tableWidth">
|
|
|
|
|
<tr class="blak">
|
|
|
|
|
<td>
|
|
|
|
|
<table width="100%" border="0" align="center" cellspacing="1" cellpadding="0">
|
|
|
|
|
<tr>
|
|
|
|
|
<td colspan="6">
|
|
|
|
|
<table width="100%" border="0" align="center" cellspacing="0" cellpadding="10">
|
|
|
|
|
<tr>
|
|
|
|
|
<td id="pageContent">
|
|
|
|
|
<!-- ==================== End prologue ==================== -->
|
|
|
|
|
|
|
|
|
|
<table border="0" width="100%">
|
|
|
|
|
<tr><td width="90%">
|
|
|
|
|
<h2 align="center"><em>Select URLs</em></h2>
|
|
|
|
|
</td>
|
|
|
|
|
${/* show help only if available */}
|
|
|
|
|
${do:if-file-exists:html/index.html}
|
|
|
|
|
<td>
|
|
|
|
|
<a href="/step2.html" target="_blank"
|
|
|
|
|
onClick="window.open('/step2.html', 'help', 'toolbar=no, location=no, directories=no, status=yes, menubar=no, scrollbars=yes, resizable=yes, width=640, height=480'); return false"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_TIPHELP}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>${LANG_TIPHELP}</a>
|
|
|
|
|
</td>
|
|
|
|
|
${do:end-if}
|
|
|
|
|
</tr></table>
|
|
|
|
|
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<form method="POST" action="step4.html" name="form">
|
|
|
|
|
<input type="hidden" name="sid" value="${sid}">
|
|
|
|
|
<input type="hidden" name="redirect" value="">
|
|
|
|
|
|
|
|
|
|
<table border="0" width="100%">
|
|
|
|
|
<tr><td>
|
|
|
|
|
${LANG_G31}
|
|
|
|
|
<select name="todo"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_G9}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
${listid:todo:LISTDEF_10}
|
|
|
|
|
</select>
|
|
|
|
|
|
|
|
|
|
</td></tr>
|
|
|
|
|
<tr><td>
|
|
|
|
|
<table border="0">
|
|
|
|
|
<tr><td>
|
|
|
|
|
${LANG_G44}
|
|
|
|
|
</td><td>
|
|
|
|
|
<input type="button" value="${LANG_G43}"
|
|
|
|
|
onClick="doOpenWindow()"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_G24b}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
</td></tr></table>
|
|
|
|
|
<br>
|
|
|
|
|
<textarea name="urls" cols="50" rows="8"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_G11}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
${do:output-mode:html}
|
|
|
|
|
${urls}
|
|
|
|
|
${do:output-mode:}
|
|
|
|
|
</textarea>
|
|
|
|
|
|
|
|
|
|
</td></tr>
|
|
|
|
|
<tr><td>
|
|
|
|
|
<table border="0">
|
|
|
|
|
<tr><td>
|
|
|
|
|
${LANG_URLLIST}:
|
|
|
|
|
</td><td>
|
|
|
|
|
<input name="filelist" value="${filelist}" size="40"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_G24c}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
</td></tr></table>
|
|
|
|
|
|
|
|
|
|
</td></tr>
|
|
|
|
|
<tr><td>
|
|
|
|
|
<table border="0">
|
|
|
|
|
<tr><td>
|
|
|
|
|
${LANG_G41}
|
|
|
|
|
</td><td>
|
|
|
|
|
<input type="button" value="${LANG_G40}" onClick="window.open('option1.html', 'option1', 'toolbar=no, location=no, directories=no, status=yes, menubar=no, scrollbars=yes, resizable=yes, width=640, height=480'); return false"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_G24}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
</td></tr></table>
|
|
|
|
|
|
|
|
|
|
</td></tr>
|
|
|
|
|
|
|
|
|
|
<tr><td align="right">
|
|
|
|
|
<table width="100%" border="0"><tr><td align="left">
|
|
|
|
|
<input type="submit" value=" << ${LANG_PREVIOUS} " onClick="form.redirect.value='step2.html'; form.submit()"
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_TIPPREV}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
</td><td align="right">
|
|
|
|
|
<input name="nextBtn" type="submit" value=" ${LANG_NEXT} >> "
|
Fixed webhttrack incompatibility with Chrome
* closes:#53
Also fixed HTML-escaping issues inside webhttrack
Rationale: The webhttrack script made the wrong assumption that once the "browse" command returned, it meant the user killed the navigation window, and it had to kill the server itself. However, modern browsers tend to "attach" to an existing session (creating a new tab, for example, within an existing window), causing the browsing command to return immediately, thus causing the server to be killed immediately by the webhttrack script. I have rewritten the logic behind, and now the server is able to kill himself if the parent script dies, AND if the browsing client did not make any activity for two minutes. The "activity" can be any browser/refreshed page, or the internal "ping" iframe (which pings the server every 30 seconds). With this model, we *should* be compatible with old browsers, and modern ones.
2014-10-15 19:17:29 +00:00
|
|
|
onMouseOver="info('${html:LANG_TIPNEXT}'); return true" onMouseOut="info(' '); return true"
|
2012-03-19 12:51:31 +00:00
|
|
|
>
|
|
|
|
|
</td></tr></table>
|
|
|
|
|
|
|
|
|
|
</td></tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
</form>
|
|
|
|
|
|
|
|
|
|
<!-- ==================== Start epilogue ==================== -->
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
<table width="76%" border="0" align="center" valign="bottom" cellspacing="0" cellpadding="0">
|
|
|
|
|
<tr>
|
2012-03-19 12:59:03 +00:00
|
|
|
<td id="footer"><small><small>© 2007 Xavier Roche & other contributors - Web Design: Leto Kauler.</small></small></td>
|
2012-03-19 12:51:31 +00:00
|
|
|
</tr>
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
</body>
|
|
|
|
|
|
|
|
|
|
</html>
|
|
|
|
|
|
|
|
|
|
|
