Files
rawTherapee/rtdata/languages
Niklas Haas 2101b846c3 Implement file sorting in thumbnail view (#6449)
* Use mtime as fallback timestamp for files without EXIF data

As suggested in #6449, with date-based sorting it can be useful to have
at least *some* sort of time-relevant information for EXIF-less files,
to prevent them from falling back to getting sorted alphabetically all
the time.

This commit simply defaults the file timestamp to the file's mtime as
returned by g_stat. For annoying reasons, it doesn't suffice to merely
forward the timestamp to the FileData structs - we also need to keep
track of it inside FilesData to cover the case of a file with 0 frames
in it.

* Add DateTime to Thumbnail

Putting it here facilitate easier sorting without having to re-construct
the DateTime on every comparison.

To simplify things moving forwards, use the Glib::DateTime struct right
away. This struct also contains timezone information, but we don't
currently care about timezone - so just use the local timezone as the
best approximation. (Nothing currently depends on getting the timezone
right, anyway)

In addition to the above, this commit also changes the logic to allow
generating datetime strings even for files with missing EXIF (which
makes sense as a result of the previous commit allowing the use of mtime
instead).

* Implement file sorting in thumbnail view

For simplicity, I decided to only implement the attributes that I could
verily easily reach from the existing metadata exported by Thumbnail.
Ideally, I would also like to be able to sort by "last modified" but I'm
not sure of the best way to reach this from this place in the code.

It's worth pointing out that, with the current implementation, the list
will not dynamically re-sort itself until you re-select the sorting
method - even if you make changes to the files that would otherwise
affect the sorting (e.g. changing the rank while sorting by rank). One
might even call this a feature, not a bug, since it prevents thumbnails
from moving around while you're trying to re-label them. You can always
re-select "sort by ..." from the context menu to force a re-sort.

Fixes #3317

Co-authored-by: Thanatomanic <6567747+Thanatomanic@users.noreply.github.com>
2023-01-02 21:27:12 +01:00
..
2022-09-30 09:53:40 +02:00
2022-09-29 00:47:59 +02:00
2022-09-29 00:47:59 +02:00

This is the directory where all translations should go.

Translations are loaded for a given term at three levels:

  1) default
  2) <Language>
  3) <Language> <Locale/Variant>

Developers who are adding a new feature should add new strings *only* to 
default.  This file should be comprised of basic English text.  It will be used 
in the event that there are no more specific languages specified.  Once you 
have modified default, you should run ./tools/generateTranslationDiffs (Bash 
script) which will re-generate the localizations with commented out additions 
which you have just added.

Translators should in general implement the <Language> file.  This is the 
generic translation for a given language; for instance, 'French', 'German', 
'Norsk', etc.  If a string exists in this file (and the user has specified this 
language), then RawTherapee will override the value in default with the value 
in <Language>.  Please note that the filename for this file must not contain 
any spaces.

In some situations, translations may differ based on region, locale, etc.  A 
good example of this is the difference in spelling between 'color' (American 
English) and 'colour' (British English). In this case, the vast majority of 
strings are identical between English and English (UK); however, to keep the 
proper spelling in Britain, we have a locale file called 'English (UK)' which
contains the differences between the two.  RawTherapee uses locale files when:
  a) The user has selected a language which has a space in the file name
  b) There is another file which is identical to the locale file up until the 
     space (i.e., 'English' to the locale file 'English (UK)').

If a locale file is used, it is applied in the same manner as <Language> is to 
default.  The locale will override any keys present from the ones in the 
language file (and in turn, the default).

After the generateTranslationDiffs has been run, all untranslated terms for 
a given language/locale will exist at the end of the file, prefixed by a ! 
comment marker.  Translators should go through this section of the file and 
translate all terms which they can. After you have translated a line, just 
remove the ! comment marker.  Comments may be included using the #xx comment 
marker, where xx is a numeric prefix used to make sure automated sorting keeps 
comments in the right order, e.g.:
  #00 Comment line 1...
  #01 Line 2...
  #02 3, etc.

To create a file with only Latin characters from a non-Latin one, you can use 
sed with the "y" command. For example, to create a latin-only "Polish (Latin 
Characters)" file from the non-latin "Polish" one:
  sed 'y/ĄĆĘŁŃÓŚŹŻąćęłńóśźż/ACELNOSZZacelnoszz/' < Polish > "Polish (Latin Characters)"

You can use this Wikipedia "Character sets" category page to help you find all 
the characters in the language file you want to convert into Latin-only:
  http://en.wikipedia.org/wiki/Category:Character_sets

To convert all line terminators in all language files to CRLF (dos/mac/unix)
you can use vim:
  a) cd rtdata/languages
     vim
  b) In vim, type:
     :set ffs=dos
     :args *
     :argdo w
  c) vim will process all language files. Once done, you can close it:
     :q