Language-site specific profile pages
ConversazioniRecommend Site Improvements
Iscriviti a LibraryThing per pubblicare un messaggio.
1Cynfelyn
Currently members get a single profile page, copied "as is" across all of LT's language versions. No matter what LT language version you are logged into, what language you write the profile in, or whether you subsequently edit the profile in another language site, the same single profile is posted across LT's family of language sites.
Would it be possible for the data in the boxes in 'Edit profile and account' / 'About you' (and equivalents in other languages) to be treated more akin to CK, so that, if they wanted, members could create and edit their profiles to the appropriate language on the various language sites?
Even if, for example, many non-native English speaking members mainly use LT's English site and have English profiles - it is after all LT's lingua franca - they may nevertheless appreciate also being able to post a profile on their mother tongue site, possibly differently weighted to reflect that part of their library.
I imagine that, as with CK, the original profile in the original language would be used as the default and copied across to language-site profiles that have not been 'localised'. Or treat the English version as the default if it has been localised.
Would it be possible for the data in the boxes in 'Edit profile and account' / 'About you' (and equivalents in other languages) to be treated more akin to CK, so that, if they wanted, members could create and edit their profiles to the appropriate language on the various language sites?
Even if, for example, many non-native English speaking members mainly use LT's English site and have English profiles - it is after all LT's lingua franca - they may nevertheless appreciate also being able to post a profile on their mother tongue site, possibly differently weighted to reflect that part of their library.
I imagine that, as with CK, the original profile in the original language would be used as the default and copied across to language-site profiles that have not been 'localised'. Or treat the English version as the default if it has been localised.
2Cynfelyn
I still think many members would like to be able to 'localise' their profile page across the languages important to them. I certainly would, so ... bump.
3Crypto-Willobie
Good idea.
4birder4106
Very good idea. Bump
5Petroglyph
+1
Monolingual defaults never sit well with me.
Monolingual defaults never sit well with me.
8Crypto-Willobie
Bwmp
9Cynfelyn
Six months after the last bump, I still think many members would like to be able to 'localise' their profile page across the languages important to them. I certainly would.
Bump.
Bump.
10royalhistorian
Oh, I would love that!
11Cynfelyn
I still think many members would like to be able to 'localise' their profile page across the languages important to them. I certainly would, so ... bump.
Or has any possibility of this been squashed by LT v.2 and the roll-out of non-localisable CK fields?
Or has any possibility of this been squashed by LT v.2 and the roll-out of non-localisable CK fields?
12Nicole_VanK
I'm hesitant. Automatic translations are usually atrocious, and there are only so many languages I could provide a translation myself.
Depending on the "how" though, good idea.
Depending on the "how" though, good idea.
13Cynfelyn
>12 Nicole_VanK: Automatic translation shouldn't come into it. Just as localised CK depends on members contributing People/Characters, First words, Quotations etc. from copies of the same work in different languages, localised member profiles would depend on the individual member editing whichever fields they wanted of their own profile in the "Edit profile and account" (www.), "Bewerk profiel en account" (nl.) etc. module. The only difference is the system would keep both the www and nl content, rather than only keeping the most recent, across all languages, as at present.
Just as, for example, the CK for Asterix the Gaul on the www site is a mixture of English, Welsh and German, because some fields with no www content do have cym and de content, and the system is using these to fill what would otherwise be empty fields. I would expect profile pages to do the same: use localised content where available, otherwise use other language content for the same field, otherwise leave blank. No automatic translation.
Just as, for example, the CK for Asterix the Gaul on the www site is a mixture of English, Welsh and German, because some fields with no www content do have cym and de content, and the system is using these to fill what would otherwise be empty fields. I would expect profile pages to do the same: use localised content where available, otherwise use other language content for the same field, otherwise leave blank. No automatic translation.
14Cynfelyn
If LT2 is very close to being rolled out - "because there won't be any LT1 pages left" (conceptDawg, https://www.librarything.com/topic/332123#7983685) - unless language-site specific / localisable profile pages are part of LT2, perhaps now is the time to say:
Bump.
Bump.