Translating the Gramps User manual/he

From Gramps
Revision as of 20:32, 29 July 2023 by Avma (talk | contribs) (translation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This article's content is incomplete or a placeholder stub.
Please update or expand this section.

מדריך למשתמש

זמין גם מתוך תוכנת גרמפס באמצעות מקש F1 (שפותח מדריך זה בחלון דפדפן), או מתפריט העזרה.

הקישור להסבר כיצד ניתן לתרגם את Gramps User manual.

תחילת העבודה

Getting started

Translating Gramps' documentation into a new language is a worthwhile process and the Gramps team thanks you.

Since Gramps version 3.0 the documentation was moved completely to this wiki. So for translation you don't need to use or even install any fancy applications to help us. You can use your browser and start immediately. Just go to the User manual page, select the current manual and then click on your language. You should could keep the English manual open to check if there is a help page missing.

The general wiki help page will help you editing wiki pages. This wiki uses the MediaWiki software, which is the same that is used by Wikipedia, so it could feel familiar.



Recommended that when updating any of the user manuals:

Where to begin...?

כלים ותצורה

  • Use Gramps localized in that language as a reference and do not simply guess the words. Verify your translated text actually matches what the user will see in the standard localized Gramps installation. You can search the Weblate translations. (i.e., searching for the phrase source:"Relationship Information" AND language:fr finds French translation: "Information sur la relation". Clicking that translation says that that phrase was found that phrase in the editfamily code and lists the other nearby translated text. This includes Tips as well as labels.)
  • If the localized interface has a typo or incorrect translation, document the EXISTING interface. Do not mislead the user into expecting something else. They might waste time searching for an non-existent update.
  • Do not have any third party addons loaded. Use a vanilla version of Gramps unless documenting that particular addon.
  • Also, preferably use a fresh copy of the Example.gramps family tree for any screenshots in your preferred language.

טיפול בשגיאות תרגום

Translation errors, typos and revisions are inevitable.

It is important that documentation describe software as it currently exists... not as it should be in a perfect world.

That acknowledgment of a localization problem in the wiki doesn't mean that the problem cannot or will not be fixed. Rather than patch the problem in documentation, file a translation bug report, see How to report bugs. A good bug report will also include a link to the wiki page that will need to be revised. The wiki page link gives the developer a second viewpoint of the nature of the problem. This helps if the bug report accidentally omits key information.

There is no requirement to pretend a problem doesn't exist while waiting for a fix. It is reasonable to annotate that the translation has the problem in the wiki without misleading the user into expecting something else.

You can make this annotation easier to eliminate after the bug fix. An English version Warning box like below can be inserted with the wiki code snippet that follows it. You might notice that the snippet has a chunk commented out:

<!--is in the process of being-->

By moving the comment markers, you can re-cycle this same warning and easily update to inform that a Bug has been filed and when a correction was released. When the manual is rolled over for the corrected release, you can update the main text and any affected screenshots before removing the warning entirely.


An unfortunate translation in the Gramps 4.1.0 interface is documented above. A "localization" Gramps bug report 7854 has been filed... so any corrections (version 4.1.1) might make this warning obsolete.

The Gramps Wiki documentation is a community project. If you notice that documentation is: outdated, incomplete, entirely missing, or not yet translated into your native language; request a WikiContributor account and help us improve! Or join our volunteers translating the interface.

{{man warn|1=[ My hovercraft is full of eels]|2=An unfortunate translation in the Gramps 4.1.0 interface is documented above. A "localization" Gramps bug report <!--is in the process of being-->{{bug|7854}} has been filed... so any corrections ''<small>(version 4.1.1)</small>'' might make this warning obsolete. 

{{WikiContributorRecruiting}} Or join [[Portal:Translators|our volunteers]] translating the interface.

צילומי מסך

Localized screenshots (aka: figures ) are useful for the localized manual.

  • If you can provide screenshots that would be great. Upload them to this wiki with the following naming convention/scheme (locale is your two letter language code):
    • filename-{gramps version number}-{locale}.png eg: Mainwin-52-fr.png
    • filename_{gramps version number}_{locale}.png eg: Mainwin_52_fr.png
    • If the screenshot/figure is language independent (such as an unlabeled icon) then just call it figure_name-52.png.
  • The Linux tool called imagemagick has proven very effective for taking Gramps screenshots for this wiki. (imagemagick should be installed with every linux distribution. If not with your installation, get it!) Invoke the preferred command options by using :
    import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png 
    This creates a fully compressed (-quality 100), timed screenshot after 2 seconds (-delay 200) of size 500 pixels wide (-resize 500), with resolution 100 (-density 100x100), with the window frame attached (-frame) in RGB mode (-channel RGB) and bbp 24 (-depth 8). This creates images of 5 inches wide, which fit nicely on a book page, as well as on a HTML page.
  • If it is too much trouble for you, just let us know and perhaps somebody else will help you. Fortunately, one does not have to speak the language to make screenshots :-)

Screenshots - gallery of available references for screenshots in different languages and past versions.

קישורים למדריך הוויקי

מדריך למשתמש גרמפס זמין באופן מקוון מתוך תוכנת גרמפס עצמה. כברירת מחדל הפניה תהיה למדריך־המשתמש בשפה האנגלית, אך ניתן להפוך את המדריך האחרון שתורגם, לזמין גם כן מתוך גרמפס. כאשר עמודי הוויקי מופיעים בשפת המקום ולא באנגלית (מהקשה על לחצן עזרה בתיבות דו־שיח, או הקשה על מקש F1,) המשמעות היא שהמדריך בשפת המקום נחשב מוּפעָל או מופשר.

כדי לאפשר או להפעיל את המדריך בשפה הרצויה, נדרשת עריכת הקובץ הבא: gramps/gui/ על מנת שקוד השפה המבוקשת תיכלל. לחלופין, אפשר ליצור קשר עם מפתחי מייזם גרמפס על ידי פתיחת בקשת תכונה עבור השפה החדשה ב-Bug tracker.

שם ניתן לראות מספר שורות קוד שנראות בערך כך:

    'nl' : '/nl',
    'fr' : '/fr',
    'sq' : '/sq',
    'mk' : '/mk',
    'de' : '/de',
    'fi' : '/fi',
    'ru' : '/ru',
    'sk' : '/sk',

פיסת הקוד הזו למעשה ממפה את קוד השפה להרחבה (סיומת עמוד ב־'/nl' לדוגמה) בכתובת עמוד הוויקי. לכן, על מנת לקשר את עמוד המדריך־הלמשתמש בעברית לגישה מתוך גרמפס נדרש פשוט להוסיף את המחרוזת הבאה 'he' : '/he' לסוף מקטע הקוד

    'fi' : '/fi',
    'ru' : '/ru',
    'sk' : '/sk',
    'he' : '/he',   <===== שורה חדשה
  • Every 'manual|...' entry in the gramp.pot file refers to a section in the manual, so make sure to use good section headings so this does not change too much over time.

Note that reports/tools link to a section in the page with the same name as the report name in Gramps.

  • You should be able to edit directly on wiki or using tools like txt2po and Weblate.

Also previous gettext file for the manual and Translation Memory may help you to upgrade deprecated/old gettext files.

שיפורים אפשריים

מייזם גנוקאש provides a complete web site environment by using gettext files, see README file and current environment.