Comments (9)
This can be used as a sample asciidoc text:
= Test of a sentence per line para
== Para not styled as 'sentence per line'
Not sentence per line para. This para is written such as all it's sentences are placed on one line only. After po4a processing, there is just single space between the senteces of the para.
== Para styled as 'sentence per line'
Sentence per line para.
This para is written such as all it's sentences are placed each one on its own line.
After po4a processing, there are double spaces between the sentences of the para.
from po4a.
What I found is that, this is mostly due to the fact that the carriage return is replaced with a space, and you can have a dangling space at the end of the line.
I can make po4a
tidy the input string when it is not "wrap", but that logic will upset a lot of existing translations.
from po4a.
I can make po4a tidy the input string when it is not "wrap", but that logic will upset a lot of existing translations.
Thank you for looking into this. I consider that not worth to make others upset.
from po4a.
Maybe I can add an option, so that the default behavior is retained but you can still get a cleaned up po file. Let's try this.
from po4a.
Then thank you very much indeed. I did not think about this 'configuration' possibility.
from po4a.
@jnavila I think that an option for that would complicate the use of the software for little gain, unless we find a simplification opportunity such as "legacy mode" where we never do such fixes, and "modern mode" where we do all of them (ie, this one and the future comparable ones). But a specific option for this specific bug that we cannot fix without upsetting users seems like a bad idea.
Maybe, legacy needs to be a scalar related to the date instead of a boolean, so that people can chose the level of legacy they want in the future, to not force anyone to either embrace bugs older than their project by jumping in the legacy more or get rid of the bugs they are used to.
Still somewhat unsure here
from po4a.
Still somewhat unsure here
Ok, this is not urgent IMHO, take your time to think it all through.
I was puzzled by the double spaces mainly because they are, let's say, highlighted in weblate editor I use for translating documentation. Not experienced translators may tend towards transferring the double spaces also to their translation(s), which is actually not necessary.
from po4a.
I was puzzled by the double spaces mainly because they are, let's say, highlighted in weblate editor I use for translating documentation.
This also bogged me, and I feel that something needs to be done. Doing the translation of git manpages, I spotted some places where the authors use two spaces after a final dot. This is totally useless with asciidoc, because the processor deduplicates them anyway. And Weblate, which is unaware of asciidoc, tends to be very picky on maintaining double-spaces in translations. So this is obviously something I'd like to tackle.
Maybe, legacy needs to be a scalar related to the date instead of a boolean, so that people can chose the level of legacy they want in the future, to not force anyone to either embrace bugs older than their project by jumping in the legacy more or get rid of the bugs they are used to.
Of course, I don't want to upset already existing po-files; the default will be to keep all spaces. Each time I "fix" something in the management of po-files for asciidoc, unfortunately this comes with fuzzied entries in existing stuff if you apply them. The scalar optional stuff would be a good idea, but then, you have an indirection between an command line option and the actual stuff being fixed. I don't think that this is a good idea because this changes are not additive. For instance, 'tablecells' can make sense for some files but you may want to not enable it on others.
I don't think there's going to be a lot more options to develop (I hope!) .
from po4a.
IIUC, this is fixed by #481
Please do not hesitate to reopen if some issue remains.
from po4a.
Related Issues (20)
- Mb -> MB in the po4a-gettextize docs
- Weblate: Set a repository browser URL for po4a-doc HOT 5
- How to generate Markdown without line wrap? HOT 2
- seems update to po4a to 0.70 breaks builds of apt HOT 14
- UTF-8 "\xF3" does not map to Unicode at /usr/share/perl5/vendor_perl/Locale/Po4a/TransTractor.pm line 583 HOT 5
- seems update to po4a to 0.70 the alternate language man pages are no longer installed. HOT 5
- Accept-Languages + Accept on website returns incorrect languages HOT 3
- docbook: Multiline entities not translated HOT 3
- Failed to run 'po4a-gettextize' for 'sgml' format (Error while running onsgmls -p) HOT 2
- Feature Request: Keep maintaining 'po4a-xxx' utilities HOT 4
- Malformed encoding while writing to file <output> with charset utf-8: Unknown failure HOT 3
- Error while build v0.71 on openSUSE HOT 12
- Markdown tables not parsed properly
- Lots of warnings and errors when building texinfo-docs with po4a-traslated texinfo.texi HOT 1
- Is it possible to use translated (but outdated version) of changed paragraph in translated file? HOT 2
- second argument to Locale::Po4a::TransTractor::read now mandatory HOT 2
- Problem after PerlIO overhaul in v0.70 HOT 9
- Fails to build with perl 5.40 HOT 2
- Add custom placeholders for po4a componentes in Weblate HOT 5
- Generate POT template from POD file error
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from po4a.