Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polish language support. #107

Closed
georgthegreat opened this issue Apr 11, 2013 · 14 comments
Closed

Polish language support. #107

georgthegreat opened this issue Apr 11, 2013 · 14 comments
Assignees
Labels
enhancement localisation concerns lbx files or localisation in general

Comments

@georgthegreat
Copy link

Hi.

Some time ago I posted an issue devoted to polish language support on sourceforge tracker.
Translator have finished his work today.

Here is the answers to the 9 questions:

  1. What kind of dash do you use in number ranges like "35-50"
    n-dash: 35–50
  2. What kind of dash do you use in date ranges like "1st January-3rd February 2009"?
    n-dash with spaces: 1 sycznia 2013 roku – 23 września 2015 roku
  3. In lists and enumerations, do you add a comma in addition to connectors like "and":
    Comma must NOT be present before "i" (literally "and"), but must BE present before "oraz" (the same meaning)
  4. How do you format short ordinals? Are ordinals gender/number sensitive?
    As I understood, modern practice is to write just numbers: 1 2 3 (without any additions)
    This format is gender insensitive
  5. What's the gender of the word "edition":
    Neuter gender. The word is "wydanie"
  6. What's the gender of the word "series" (of a journal)?
    Feminine gender. The word is "serja"
  7. What's the long date format?
    This matches the russian date format: 31 sycznia 2013 roku (January 31th 2013) or styczeń 2013 (January 2013).
  8. What's the short date format?
    This matches the russian date format: 31.01.2013
  9. After which punctuation marks do you capitalize a word?
    ". ! ?" (English = package default)

I don't understand how to attach custom file to the issue.

@georgthegreat
Copy link
Author

Here is the link to the utf-8 with BOM bibliography strings file:
https://www.dropbox.com/s/qr6005g9mn6huoz/polish.lbx

aboruvka pushed a commit that referenced this issue Apr 12, 2013
@aboruvka
Copy link
Collaborator

@georgthegreat Thanks. You can find the revised module in the referenced commit. The short strings for and editorsco and byeditortrco contained Cyrillic characters. I've changed these to Latin, so they likely need some checking over. I also converted the file to Ascii and incorporated biblatex punctuation commands. If the result is now too tedious for the translator to read, you could compile example number 03 from the documentation for him to review.

For answer 3, the module only contains the string "i". It is possible to create a "smart and" that uses different strings, but we would need to know conditions for use of "i" versus the alternative "oraz".

We acknowledge all contributors in the biblatex manual, so I'll add yours. Is there a name we can use to credit the translator as well?

@ghost ghost assigned aboruvka Apr 12, 2013
@georgthegreat
Copy link
Author

I've rechecked them.
I'm waiting for the confirmation from translator, but it seems that everything is fine.

Will this file be added to biblatex repo? When I can pull to get it?

@aboruvka
Copy link
Collaborator

The file is on the dev branch here. @plk Could you update the dev files at SF?

@plk
Copy link
Owner

plk commented Apr 12, 2013

Done - the 2.6 dev version now has the latest changes. Note that if you are using biber, you'll need the 1.6 dev version.

@georgthegreat
Copy link
Author

Hi!
I've pulled the latest dev version from github (from dev branch).
Here is the error I've got:

Package biblatex Warning: Language 'polish' not supported.
(biblatex) Using fallback language 'russian' on input line 15.

! LaTeX Error: Command \k unavailable in encoding OT1.

I'm using T2A everywhere in my project. Seems that biblatex traits font encoding incorrectly (I'm not sure who is switching it actually).

Also, I have to remove unicode byte order park from polish.lbx since latex doesn't support it.

@aboruvka
Copy link
Collaborator

@georgthegreat Can you post an example? Oh, and you should use the dev version available at SF - to use the files from github you need to run the build script.

@georgthegreat
Copy link
Author

Can you pull dev version from here:
https://github.com/georgthegreat/dancebooks-bibtex
Just clone it and run make from the repo root.

Or here is the link to the final file
https://github.com/georgthegreat/dancebooks-bibtex/blob/dev/bib/polish.bib

@aboruvka
Copy link
Collaborator

@georgthegreat I meant a full example here in the comments. The first error seems to imply that the files you pulled didn't build properly. The second error is likely associated with the entry aksin from biblatex-examples.bib, which uses \k. To handle that just add \usepackage[T1,T2A]{fontenc} to your preamble.

@georgthegreat
Copy link
Author

Thanks! This helped.

@aboruvka
Copy link
Collaborator

@georgthegreat I still need to update the manual. Is there a name we can use to credit your translator?

@georgthegreat
Copy link
Author

I've asked the translator for permission. I'le answer as soon as she answers me.

@georgthegreat
Copy link
Author

Yes, you can use her name: Anastasia Kandulina

@aboruvka
Copy link
Collaborator

Great. Thanks to you and Anastasia.

aboruvka pushed a commit that referenced this issue May 20, 2013
aboruvka pushed a commit that referenced this issue May 20, 2013
@moewew moewew added the localisation concerns lbx files or localisation in general label Jun 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement localisation concerns lbx files or localisation in general
Projects
None yet
Development

No branches or pull requests

4 participants