Closed (fixed)
Project:
User Guide
Version:
8.x-5.x-dev
Component:
HU translation
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
26 Sep 2018 at 19:58 UTC
Updated:
19 Nov 2018 at 22:04 UTC
Jump to comment: Most recent
This is a placeholder umbrella issue to track the progress of proofreading the final version in Hungarian.
General observations
Probably would be better to fix them by search & replace and commit them in bulk:
In template „melyek szerzői joga 2000-2017 között” replace the „–” character to „-” (many occurrences)– see #3002928: [HU] Proofreading general fix #1 – hyphen instead dashWord „Látogató” should not be capitalized (4 occurrences)– see #3002931: [HU] Proofreading general fix #2 – lowercase word „Látogató”Subsentence separator comma is needed before the „vagy írjuk be a címsorba” text (3 occurrences)– see #3002934: [HU] Proofreading general fix #3 – missing sub-sentence separator commaIn the text „Ha nem látjuk azonnal az eredményét a változtatásainknak, akkor szükség lehet a gyorsítótár ürítésére” the prefix „ki” is needed before „ürítésére.” (6 occurrences)– see #3002938: [HU] Proofreading general fix #4 – prefix „ki” neededUnify these two variant: A) „vagy írjuk be a címsorba” és B) „vagy a címsorban adjuk meg az ...” Which one is the preferred?– not needed to change, as we agreed, variety is better.Replace everywhere the incorrect „webhelyinformációk” word with the correct „webhely-információk” format (reference)– see #3002989: [HU] Proofreading general fix #5 – hyphen needed in „webhelyinformációk”.
Other todos
Add proofreaders' name to the attributions list.– Done in commit 2616b45Make sure that definite articles („a” and „az”) are propely aligned to chapter numbers in links pointing to topics in 1. and 5. chapters.– Done in commit 18bcb53Ensure that all summaries length are under 120 char limit.– Done in commit 3451fdf
Comments
Comment #2
baluertl(Unintentionally duplicated comment, sorry)
Comment #3
baluertlComment #4
baluertlComment #5
baluertlComment #6
baluertlComment #7
jhodgdonWould you like me to wait until this issue is finished (and sub-issues) before I build ebooks and make a release, or go ahead now?
Comment #8
jhodgdonI know these issues are in the HU Translation component, but it would help me scan email from drupal.org (I am subscribed to all User Guide issues) if they also had the [HU] prefix in the issue titles, for new issues you create. Thanks!
Comment #9
baluertlSorry, you're absolutely right. (To be honest, I had some strange feeling when I looked on these issue titles, but didn't realize what I'm missing. The [LC] from their beginning! :) I'll keep prefix them from now on.
Comment #10
baluertlComment #11
baluertlComment #12
baluertlComment #13
baluertlComment #34
baluertlComment #35
baluertlComment #44
baluertlComment #87
baluertlComment #101
baluertlComment #118
baluertlComment #119
baluertlComment #132
baluertlComment #133
jhodgdonWoot!!!! I'm just updating the HU screenshots for 8.6 now; should be done later today.
Comment #134
drummI did get 2 more length errors importing:
I think we might want to just raise the character limit, since I’m guessing this is really counting bytes (this is basic core textfield validation), and non-latin characters do take up more bytes.
Comment #135
jhodgdon140 characters isn't much. It is hard to stay within that sometimes.
Comment #136
baluertl@drumm thanks for notifying. If you decide to keep the current 120 char limit, then I'll be available to commit a fix only at my evening (13-14 hours from now)
Comment #137
drummNevermind about changing the field’s max length: “There is data for this field in the database. The field settings can no longer be changed.”
Comment #139
baluertlNow checked, and indeed, in
[[blocks-chapter]]and in[[prevent-chapter]]the summaries were beyond 140 chars. To be honest I have to admit that I forgot to check the summary lines directly in this guide.txt file, only checked the individual files.