Mobilizon/app-facebook-event-scraper
1
0
Fork 0
mirror of https://github.com/akaessens/NoFbEventScraper synced 2025-06-05 23:29:13 +02:00
Code Issues Releases Wiki Activity

move html to res/raw to enable localization

Browse Source
This commit is contained in:
akaessens
2020-08-30 19:09:44 +02:00
parent 7a44e467f0
commit 9540b252a5
5 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
app/src/main/java/com/akdev/nofbeventscraper/AboutActivity.java
View File

@@ -24,7 +24,7 @@ public class AboutActivity extends AppCompatActivity {
WebView webview_about = findViewById(R.id.webview_about);
webview_about.loadUrl("file:////android_asset/about.html");
webview_about.loadUrl("file:///android_res/raw/about.html");
}

2
app/src/main/java/com/akdev/nofbeventscraper/HelpActivity.java
View File

@@ -19,7 +19,7 @@ public class HelpActivity extends AppCompatActivity {
WebView webview_help = findViewById(R.id.webview_help);
webview_help.loadUrl("file:////android_asset/help.html");
webview_help.loadUrl("file:////android_res/raw/help.html");
}
}

0
app/src/main/assets/about.html → app/src/main/res/raw/about.html
View File

0
app/src/main/assets/help.html → app/src/main/res/raw/help.html
View File

2
app/src/main/res/values/strings.xml
View File

@@ -13,7 +13,7 @@
<string name="url_setting">Which URL to scrape</string>
<string name="url_setting_summary">
Using m.facebook.com is more stable and faster. Using www.facebook.com works better with multiple instance events but will eventually break when facebook disables the classic design.
Using m.facebook.com is more stable and faster. Using www.facebook.com works better with multiple instance events and will display a high resolution preview but will eventually break when facebook disables the classic design.
</string>
</resources>