|
| From: | Brian Wilson |
| Subject: | Re: [be] Copy, Paste, and Zero Width Space |
| Date: | Thu, 18 Apr 2013 14:46:25 +0700 |
Hi Brian,
For final publishing I can do pretty much anything I want as long as the source has some kind of logical pattern to run a regex on. A built-in pre-process module is an integral part of most publishing projects I do. For example, I have one Thai script project where in the editor, there are normal spaces between words and to mark phrase spacing, the translator is adding punctuation (just periods) at the end of phrases (kind of like sentences). When we render it, we'll swap the normal spaces with ZWSP for good line breaks and where there is a period, we'll change it to a TeX space command (I can't remember which one right now). That will give us the format we need for the final publication without having to introduce any complex or confusing characters or markup in the source.
In another project, it was decided that inserting "/" character between words was the best way for the editor to work with the text. In another project the "#" character indicated a certain kind off spacing needed in the rendered output. I guess you can use most anything you want as long as you are consistent and logical.
The biggest problem I've found with using invisible characters in the source is consistency. There's just no way the editor can keep track of them. Then cleaning up the mess when it comes time to render is a lot more work. The only upside I've seen is editors "feel better" when in the editor, the words "look" like they are supposed to. Some times that is hard to get around that.
Hope that helps.
In Him,
Dennis
On 04/18/2013 01:06 PM, Brian Wilson wrote:
Thank you Dennis,
We need regular spaces for the phrasal spacing. It is also helpful to have the ZWSP in order to work with the text in BE. It is much easier on the eyes.
Currently I have a friend (we are still friends at the moment) alternating between pulling his hair out and beating his head against the wall in developing a perl script that will run through the data files in the Project directory and insert the ZWSP between Lao words found in a laowordlist.txt file while removing duplicate ZWSP. The progress is promising.
I am interested in the space characters you use for final publishing.
God bless,
Brian
Brian Wilson, Director
Mekong Information Technology Co., Ltd.Dong Dok, Saythany, Vientiane MunicipalityLao PDR
Tel/Fax: (+85621) 725010Mobile: (+85620) 9646-7085
--------------------------------And so the visitor turned sadly away, thinking for what miserable messes of pottage men and women are willing to sell their glorious birthright as children of God. -- Ellen White.
On Thu, Apr 18, 2013 at 12:17 PM, Dennis Drescher <address@hidden> wrote:
Hi Brian,
I'm not currently using BE but for these types of situations in projects I work with I recommend a couple ways. One way would be to insert a visible character in the text that could represent the ZWSP. IMO, you really don't want invisible characters in your source text, especially when they are only for formated output, not actual data. A second way would be to use just normal spaces in BE and then replace them with ZWSP just before you run it through XeTeX. My publishing system uses XeTeX and this is how I normally handle situations like this. Some projects we have we have to use a combination of "space" character types to get the final look we need in the output so we might have to replace a couple types on-the-fly.
I hope one of these ways work for you. Thanks.
In Him,
Dennis--
On 04/15/2013 02:34 PM, Brian Wilson wrote:
Hi all,
Brining up a different subject from the mac install issues and that is the need to be able to copy/paste without the cumbersome menu method.
I am needing to enter Zero Width Space between Lao words in the translation. (If email cooperates an example is located between the reversed angle brackets ><).
Currently I am translating in libreoffice, inserting the ZWSP manually (it is visible in Libreoffice) and then pasting each verse into bibledit. With this process, Xetex is able to know the word boundaries in Lao and generate a pdf with a justified margin.
Any suggestions?
Brian
(In testing all of this I noticed that bibledit 4.6 crashed each time I try to print the Lao text that did not contain the ZWSP. I do not know if the reason was because xetex didn't know what to do with such long strings or whether it had something to do with trying to print only 1 chapter.)
Dennis Drescher
Publishing Systems Developer
SIL International - MSEAG
Ph: (66) 8-318-6988 (cell)
Ph: (66) 5 313-1022 (home)
email: address@hidden
This message was not sent from a smart phone or an iAnything, please don't think any less of it.
-- Dennis Drescher Publishing Systems Developer SIL International - MSEAG Ph: (66) 8-318-6988 (cell) Ph: (66) 5 313-1022 (home) email: address@hidden This message was not sent from a smart phone or an iAnything, please don't think any less of it.
| [Prev in Thread] | Current Thread | [Next in Thread] |